Context Repository API

This reference is generated from Context Repository's own GET /v1/product-openapi.json, so it cannot drift from what the service serves. The raw document is served at /openapi/context-repository.json.

Context Repository is the part of Coelevate that holds a project's context — skills, knowledge, memories and tools — as versioned assets, and the kits that select which of them an agent is served. This is its customer API: read and search that context, inspect releases and their tags, stage changes for review, settle a change request by approving or rejecting its ops and merging or closing it, and write kits and gaps directly. A key that can only stage a change can propose it and cannot land it: deciding, merging and closing need the review scope, kit writes need the kits scope and gap writes need the gaps scope.

Calling the API

The examples on each page use these shell variables:

export API_URL="<the Context Repository address your key panel shows>"   # no trailing slash
export PROJECT_ID="<your project id>"
export TOKEN="<a bearer token, below>"

Authentication

A short-lived access token, obtained by exchanging an API key with the OAuth 2.0 client-credentials grant. Send it as Authorization: Bearer <token>. Each operation lists the scope the token must carry; there are five, and none implies another: context:read reads context; context:assets stages a change for review and never decides, merges or closes one; context:review approves or rejects staged ops and merges or closes the change request; context:kits writes kits directly and context:gaps records and closes gaps directly, each of which takes effect at once and bypasses the changeset.

Exchange your API key for a token at the token address your key panel shows, with the OAuth 2.0 client-credentials grant, asking for the scopes you need (context:read, context:assets, context:review, context:kits and context:gaps, separated by a space when you ask for several): read reads context, write stages changes for review, review decides, merges and closes a change request, kits writes kits directly, and gaps records and closes gaps directly. A token issued for another Coelevate API, such as the A2A one, is not accepted here. Staging a change needs both scopes in practice, because you read the open changeset (read) before you write to it (write).

A request that fails authentication returns 401; one whose token lacks the operation's scope returns 403; an unknown project, or a token for a different project, returns 404.

Operations