Getting started

Get a key

In the console, open Settings → API Keys and create one. It is shown once.

export CHORDIAN_API_KEY="ck_live_..."

Call the API

curl https://api.chordian.ai/api/v1/workspaces \
  -H "x-api-key: $CHORDIAN_API_KEY"

{
  "workspaces": [
    {
      "workspace_id": "wsp_a1b2c3d4",
      "name": "Acme Production",
      "slug": "acme-production",
      "is_default": true,
      "primary_memory_id": "csmbx-wsp_a1b2c3d4"
    }
  ],
  "active_workspace_id": "wsp_a1b2c3d4",
  "default_workspace_id": "wsp_a1b2c3d4"
}

active_workspace_id determines which memory is used when a request does not name one. Most integrations never need to change it — but if answers come back from an unexpected memory, this is the first thing to check.

Base URL and versioning

https://api.chordian.ai/api/v1/

Every public route is versioned. There are no unversioned public routes, and internal service routes are not registered on the gateway at all — they return 404 from the public internet rather than 403.

Common first-request failures

Symptom	Cause
`401`	Missing or mistyped key; check the header is `x-api-key`, not `Authorization`
`403`	Key valid but not allowed for this route (permission or KeyScope)
`404` on a resource you can see in the console	The resource belongs to a different tenant, or a different workspace than you assume
`404` on `/api/v1/api-keys` with a `ck_` key	Key management is console/session only — not on the public gateway
`429`	Per-key rate limit; back off and retry
`402`	Plan limit or credit balance — they are different

Client setup

export CHORDIAN_API_KEY="ck_live_..."

curl https://api.chordian.ai/api/v1/workspaces \
  -H "x-api-key: $CHORDIAN_API_KEY"