Manage API keys

Documentation Index

Fetch the complete documentation index at: https://docs.stratta.ch/llms.txt

Use this file to discover all available pages before exploring further.

API keys are managed from stratta.ch/api-keys. Each key is personal to you and grants read/write access to your workspace, so treat them like passwords.

​

The keys table

The API keys page lists your keys with:

• Name — the label you chose, to recognise where the key is used.
• Prefix — the first characters (e.g. sk_strt_abc123…); the rest stays hidden.
• Last used — when the key last made a request.
• Created — when you created it.
• Status — active, or revoked.

​

Create a key

Click Create API key, name it after where you’ll use it (e.g. “Office laptop”), and copy the full key — it’s shown once. See Get an API key for the full flow.

​

Rotate a key

To rotate, create a new key, update your Claude client to use it, then revoke the old one. There’s no in-place “regenerate” — create-then-revoke keeps things explicit and auditable.

​

Revoke a key

Revoking is immediate and permanent: any Claude client still using that key stops working right away. Use it when a key is no longer needed, may have leaked, or belonged to a device you no longer use.

​

Limits

If you reach a limit, revoke unused keys. These limits protect the service from abuse and are per user, not per organization.

​

Where the key lives on your machine

Depending on how you set up, your key is stored in one of:

• The STRATTA_API_KEY environment variable (highest precedence), or
• ~/.stratta/config.json (owner-only, mode 0600), written by the first-use prompt or npx -y @stratta/mcp login.

Details in MCP Reference → Overview.

​

Next steps