API
One API key model, bearer authentication and one set of conventions: how Ciresk's APIs work, and where each product's reference is.
Every Ciresk API that takes keys is used with the same credential: an API key created on platform.ciresk.com under API tokens, sent as Authorization: Bearer <key>. A key carries its organization's region in its prefix (csk_live_eu_...); Ciresk runs in the EU only today. Ciresk CI and the Platform API follow the same conventions: an Idempotency-Key that makes a retry of a request that creates something safe, cursor pagination with data, has_more and next_cursor, application/problem+json errors with a stable code, and an X-Request-Id on every response. Those are documented once, on this tab: API keys, Scopes, Regions, Idempotency, Pagination, Errors and Request IDs.
Products
| Product | Base URL | Reference |
|---|---|---|
| Ciresk CI | https://ci.eu.ciresk.com/v1/ci (EU cell) | Ciresk CI API: the overview, the quickstart and every endpoint, generated from the OpenAPI document |
| Ciresk Platform | https://api.ciresk.com/v1/platform | Platform API: keys, organizations, team and sessions; bearer csk_ key or a signed-in person's token |
| Ciresk Kepler | Kepler API: reference coming | |
| Ciresk Scribe | Scribe API: reference coming | |
| Ciresk Trace | Trace API: reference not published yet | |
| Ciresk Context | Context API: reference coming | |
| Ciresk Agent | Agent API: no public API today |
Good to know
GET /healthandGET /readyon a product's origin need no credential.- Ciresk CI's CLI is its reference client:
ciresk ci <command> --jsonshows exactly what the API answers, in the same envelope. - Agents reach Ciresk CI's API through its MCP endpoint with the same credential,
https://ci.eu.ciresk.com/v1/ci/mcp; see How it works.