Accounts & authentication

Name one of your check-only keys

PUT /api/v1/check-keys/{id}

Changes a check-only key's display name. People only, their own keys. Updates only the display name, never the agent's identity or powers.

Parameters

idpath · required · integer (int64): The key ID from your list.

Example request

curl --request PUT 'https://commitscale.com/api/v1/check-keys/1' \
  --header "Authorization: Bearer $CSCALE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{
  "name": "My coding agent"
}'

Example values illustrate the format. Use your own credentials and identifiers.

Request body

application/json

namerequired · string: Label for the key, between 1 and 60 plain characters.

Responses

200 The renamed key.

application/json

{
  "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"
}

agentrequired · string: Handle 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 · string: The 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_scope403

A 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_off403

The 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.

unauthenticated401

The request carried no credentials.

Use this operation's sign-in method. Bearer credentials use Authorization: Bearer <token>; browser credentials use the session cookie.

invalid_token401

The 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.

forbidden403

The 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.

not_found404

It does not exist, or the caller cannot read it: a repository the caller cannot read is reported as not found.

Check the name or ID, and that the token has the repository.

invalid_request400 / 413 / 415 / 422

The request is malformed or breaks a rule, such as a title that is too long, or a body that is not the expected JSON.

Fix the request as detail says. The same request fails the same way.

quota_exceeded429

With 429, the caller used its requests for the minute. With 422, a count limit was reached.

With 429, wait Retry-After seconds and retry. With 422, remove one first.

internal500

The server failed, and logged why.

Retry after Retry-After seconds. A write is safe to retry with the same idempotency key.