API keys

Create, use, and revoke organization API keys for the LLM Gateway from the Console.

Organization API keys authenticate requests to the LLM Gateway. Every key belongs to an organization, and usage is billed to that organization.

Keys look like this:

ccp_live_ak_<key-id>.<secret>

Only a hash of the secret is stored. The full key is shown once, at creation.

Create a key in the Console

  1. Open the Console and select your organization.
  2. Go to API keys in the sidebar and click Create API key.
  3. Enter a Name that describes where the key will live — for example Production inference.
  4. Optionally open Advanced settings to set an expiration date. Keys without an expiration stay valid until you revoke them.
  5. Click Create key.

The dialog then shows the full key one time. Copy it and store it in your secret manager before you close the dialog — you cannot retrieve it again. The key list only ever shows the key ID and the last characters of the secret.

Use the key

Send the key as a bearer token on every request:

curl https://llm.clusterbase.dev/v1/models \
  -H "Authorization: Bearer $CLUSTER_API_KEY"

Every key carries the two scopes the gateway requires:

ScopeGrants
models:readGET /v1/models
chat:statelessPOST /v1/chat/completions and POST /v1/chat

Revoke a key

Open the key's row menu in the Console and choose Revoke key. Revocation is immediate and permanent: requests using the key are rejected from that moment, and the key cannot be restored. Requests with a revoked, expired, or unknown key receive 401 authentication_error.

Errors

StatusMeaning
401Missing, invalid, expired, or revoked key
402The organization has no active plan or credits
403The key lacks the required scope
503The credential authority is temporarily unavailable — retry

On this page