Browse documentation
← API reference

Organizations & usage

The namespace's plan and feature flags

GET /api/v1/namespaces/{ns}/plan

Returns the namespace's effective plan and public feature flags. Members may read them; a check-only key cannot call this operation. Missing or unknown flags are off. Manage your subscription from Billing.

Parameters

nspath · required · string

A person, such as john, or an organization, such as acme.

Example request

curl --request GET 'https://commitscale.com/api/v1/namespaces/alex/plan' \
  --header "Authorization: Bearer $CSCALE_TOKEN"

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

Responses

200 The plan and its visible feature flags.

application/json

{
  "billing_available": false,
  "can_test_plan": false,
  "flags": {
    "account_pages": true,
    "accounts": true,
    "billing_pages": true,
    "model_api": true,
    "plan_pages": true,
    "remote_mcp": true,
    "usage": true,
    "usage_pages": true
  },
  "frozen": false,
  "namespace": "alex",
  "people": 1,
  "plan": "free"
}

billing_availablerequired · boolean

Whether this server has a billing service configured.

can_test_planrequired · boolean

Reserved account capability; false for customer organizations.

flagsrequired · object

Unknown or absent flags must be treated as off by clients.

frozenrequired · boolean

Whether a Free organization with several people is frozen.

namespacerequired · string

The personal or organization namespace name.

peoplerequired · integer (int64)

Number of people in this workspace; agents do not count.

planrequired · string

The account's plan: free or pro.

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

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.