Browse documentation
← API reference

Accounts & authentication

Read this check-only key's own usage

GET /api/v1/check-keys/current/usage

Returns a check-only key's daily API usage. Authenticates only a check-only key. The key ID is taken from its credential, never a path or caller-supplied ID. Returns daily API request counts including this read, newest first. These are not model usage or billing units; metering and billing add those separately.

Parameters

daysquery · optional · integer (int32)

How many days back, up to 366; 30 when not given.

Example request

curl --request GET 'https://commitscale.com/api/v1/check-keys/current/usage' \
  --header "Authorization: Bearer $CSCALE_CHECK_KEY"

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

Responses

200 This key's usage.

application/json

{
  "days": [
    {
      "api_requests": 1,
      "day": "2026-10-26"
    }
  ],
  "key_id": 1
}

daysrequired · array of object

Daily usage, newest UTC date first. Dates without use have no entry.

Fields of days

Daily usage, newest UTC date first. Dates without use have no entry.

Each item has this shape.

api_requestsrequired · integer (int64)

Requests admitted to the key's allowlist, including failed requests. These are not model tokens, successful checks, or billing units.

dayrequired · string (date)

UTC calendar date in YYYY-MM-DD form.

key_idrequired · integer (int64)

Identifier of the check key supplied in Authorization.

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.

invalid_request400

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.