Buy Pro for yourself

Parameters

Idempotency-Keyheader · required · string

A durable billing request key, scoped to the person or organization. Retry uncertain results with the same key and input. Use a fresh key for new work after a final refusal. Plan deliveries scope keys to service, workspace kind and ID. Records do not expire.

Minimum length: 1 · Maximum length: 128

Example request

curl --request POST 'https://commitscale.com/api/v1/billing/checkout' \
  --header "Authorization: Bearer $CSCALE_TOKEN" \
  --header 'Idempotency-Key: 019a1f40-7c00-7000-8000-000000000003' \
  --header 'Content-Type: application/json' \
  --data '{
  "seats": 1
}'

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

Request body

application/json

seatsrequired · integer (int32)

Exactly one seat for a personal subscription.

Responses

200 Checkout link.

application/json

{
  "url": "https://billing.commitscale.com/checkout"
}

urlrequired · string

Absolute URL to open for the next step.

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.

billing_not_configured503

Billing is not configured on this server or its billing service.

Billing is unavailable on this server. Try again later or contact support.

billing_unavailable503

Billing could not confirm the request.

Retry the same input with the same idempotency key. Never start another purchase to recover a lost reply.

billing_refused400 / 403 / 404 / 405 / 409 / 410 / 415 / 422 / 429

Billing refused the operation. billing_code names its reason; pending_key identifies a purchase needing resolution.

Review Billing and retry uncertain operations with the original key. Resolve an unfinished personal purchase through billing/requests/resolve. New work after a final refusal needs a fresh key.

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.

idempotency_key_reused409 / 422

The idempotency key was already used for a different request.

Use a new key for each new request, and the same key only for a retry of the same request.

idempotency_key_in_use409

The first request with this key is still running, including a queued model question, or it succeeded with a secret, such as a new token, which is never replayed.

When Retry-After is set, retry then with the same key. Otherwise the first request succeeded: do not repeat it.

internal500

The server failed, and logged why.

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

unavailable503

With 502, a service the server needs did not answer, such as a sign-in provider. With 503, the server is busy, such as when a workspace is locked or host lookups are full, or a write with an idempotency key runs long: that write goes on, and its answer is kept for the key.

With 502, retry later, or sign in another way. With 503, retry after Retry-After seconds, using the same idempotency key for a write; a long-running write can then replay its answer.