Skip to content

Managing access keys

Access keys let programs and AI agents work with an account’s clusters. They live in the account under Settings → Access Keys. Only the account’s owners and admins can see and manage them; everyone else sees a short note instead.

How keys behave — permissions, cluster limits, expiry — is described in Access keys.

The list shows the account’s active keys:

Column Shows
Name What you called the key.
Type REST for the API, MCP for AI agents.
Key The last four characters, to tell keys apart. The rest is never shown again.
Permissions Read only, Full access, or the resources it can change.
Clusters All, or how many clusters it is limited to.
Last Used When the key last made a request.
Expires When it stops working, or Never.

Create Key opens a short guide, one question per step:

  1. Type — REST API for scripts, CI pipelines and integrations, or MCP for AI agents such as Claude. A key works on its own endpoint only.
  2. Name — shown in the key list and in the activity log for everything the key does. Name it after what uses it: CI pipeline, Claude agent.
  3. Permissions — a grid of resources against read, write and delete. A new key starts as read only; Read only, Full access and Clear set the whole grid at once. Ticking write or delete also ticks read.
  4. Clusters — every cluster in the account, including ones created later, or only the clusters you tick.
  5. Expiry — 30 days, 90 days (recommended), a year, or never.

Create Key then shows the key:

  • the full key, with a copy button — shown only this once. Store it in a secret manager before closing the dialog.
  • how to use it: for a REST key the API’s address and a curl example, for an MCP key the server’s address with the claude mcp add command and a configuration for other clients, all with your key filled in.

Keys are not edited. To change what a key may do, create a new key with the permissions you want, switch the program or agent over to it, and revoke the old one.

Open the menu at the end of the key’s row and choose Revoke, then confirm. The key is refused from its next request on, and the revocation is recorded in the account’s activity.

A key also stops working on its own when it expires, or when the person who created it is no longer an owner or admin of the account. An expired key is removed from the list within the hour.

An account can hold 10 active keys; the Access keys row in the quota panel under Settings → General shows how many are in use, and Request Limit Increase asks for more. Creating a key notifies the account’s other owners and admins.

Everything a key does shows in the account’s Activity under the key’s name, and creating or revoking a key is recorded too. Filter by Credentials & keys to see the keys’ lifecycle, or by who acted with Access keys to see what keys did.