Accounts & authentication
List your agents' check-only keys
GET /api/v1/check-keys
Lists your agents' check-only keys. People only, their own keys. Includes names, the owning agent, creation, expiry, revocation and last use (updated at most once a minute). Keys awaiting collection have no expiry yet. Never returns a secret. Keys belong only to their owner.
Example request
curl --request GET 'https://commitscale.com/api/v1/check-keys' \
--header "Authorization: Bearer $CSCALE_TOKEN"Example values illustrate the format. Use your own credentials and identifiers.
Responses
200 Your keys, newest first.
application/json
{
"keys": [
{
"agent": "agent:check-1@alex",
"created_at": "2026-10-26T10:00:00Z",
"expires_at": "2026-10-26T10:00:00Z",
"id": 1,
"last_used_at": "2026-10-26T10:00:00Z",
"name": "My coding agent",
"revoked_at": "2026-10-26T10:00:00Z"
}
]
}keysrequired · array of objectThe caller's check keys, including revoked keys.
Fields of
keysThe caller's check keys, including revoked keys.
Each item has this shape.
agentrequired · stringHandle of the check-only agent using this key.
created_atrequired · string (date-time)When this record was created, in UTC.
expires_atrequired · string or null (date-time)Empty until the agent collects the key.
idrequired · integer (int64)Numeric check-key identifier used for renaming and revocation.
last_used_atrequired · string or null (date-time)Recorded at most once a minute, as for other tokens.
namerequired · stringThe person's label for this key, between 1 and 60 plain characters.
revoked_atrequired · string or null (date-time)When the key was revoked, in UTC; null while it has not been revoked.
RateLimit and RateLimit-Policy describe the request rate. Follow Retry-After when a response asks you to wait.
Problem responses
Errors use application/problem+json. Act on the stable code, and follow next when present. See the problem format.
check_key_scope403A check-only key may call the test check, read its own usage and acceptance rule, contact support, and withdraw data sharing.
Use a person's sign-in for account management. More agent power needs the owner's passkey; this key cannot widen itself.
feature_off403The namespace plan does not include this feature.
Retrying on the same plan will not help. GET /api/v1/namespaces/{namespace}/plan, and the namespace's Plan page in Settings, show what its plan includes.
unauthenticated401The request carried no credentials.
Use this operation's sign-in method. Bearer credentials use
Authorization: Bearer <token>; browser credentials use the session cookie.invalid_token401The token is unknown, expired, or revoked, its agent was revoked, or an OAuth token was used outside its MCP resource.
Stop using it. Sign in again, or ask the owner to create a replacement agent key.
forbidden403The caller may not do this: only people may, only owners may, or the agent was not given this repository or write access.
Stop. Retrying will not help. Ask the owner for the access, or leave the step to a person.
quota_exceeded429With 429, the caller used its requests for the minute. With 422, a count limit was reached.
With 429, wait
Retry-Afterseconds and retry. With 422, remove one first.internal500The server failed, and logged why.
Retry after
Retry-Afterseconds. A write is safe to retry with the same idempotency key.