COBACK for developers

COBACK monitors regulation for your company, screens every change against a digital twin of the company, and turns real hits into assigned tasks. Everything the dashboard shows is also reachable programmatically: the company brain, the laws we ingested, the screening results, the task board, and product compliance findings.

Four ways in, one credential:

  • REST API: workspace-scoped endpoints under /api/v1. See the API reference.
  • MCP: point Claude or any MCP client at your workspace. See MCP.
  • CLI: npx coback from a terminal or a script. See CLI.
  • Claude skill: teach Claude when and how to use all of the above. See Skill.

Get a key

Every surface authenticates with a workspace API key. In the dashboard, open Settings, then API keys, name the key, and pick its access: read only, or read and write. The key is shown once at creation. Read keys can query everything; write keys can additionally record match feedback, create and update tasks, add comments, and upload documents.

First call

curl -s -H "Authorization: Bearer $COBACK_API_KEY" https://api.coback.ai/api/v1/me

That returns the workspace and company behind the key. From there:

curl -s -H "Authorization: Bearer $COBACK_API_KEY" "https://api.coback.ai/api/v1/laws?limit=10"
curl -s -H "Authorization: Bearer $COBACK_API_KEY" https://api.coback.ai/api/v1/matches

Errors are always { "error": "..." } with a 4xx status. The rate limit is 120 requests per minute per key; a 429 carries a Retry-After header. The machine-readable contract lives at /api/v1/openapi.json.