Test checks
Read whether your test acceptances need a passkey
GET /api/v1/tests/acceptance-policy
Reports whether your test acceptances need a passkey. Sign-ins, agents and check keys read only their own responsible person's effective rule. CI uses its protected check credential. Runner and job credentials cannot substitute their owner for the person whose check is being verified.
Example request
curl --request GET 'https://commitscale.com/api/v1/tests/acceptance-policy' \
--header "Authorization: Bearer $CSCALE_CHECK_KEY"Example values illustrate the format. Use your own credentials and identifiers.
Responses
200 The effective acceptance rule.
application/json
{
"passkey_required": false,
"person": "user:alex"
}Effective rule for the person behind this sign-in or check credential. This read grants no account-management powers.
passkey_requiredrequired · booleanWhether this person requires passkey-backed acceptance of findings.
personrequired · stringHandle of the person responsible for this credential.
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.