Manage API keys
Create, name, rotate, and revoke the keys that connect Claude to your workspace.
API keys are managed from Intégrations › Clés d’API (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 only. See Get an API key for the full flow.
Give a key an end date
When you create it, choose how long the key stays valid: 30 days, 90 days, a year, or until revoked. After that date the key no longer answers, like a revoked one. A key left on a forgotten machine switches itself off.
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.
Revoking cannot be undone. If you revoke a key still in use, reconnect that
client with a new key via npx -y @stratta/mcp login or by updating its
config.
The owner and the admins of the space see every key of the space, with its owner, its last use and its end date, at the bottom of the Organization page. They can revoke one without going through its owner; the gesture is written to the space's journal.
Limits
| Limit | Value |
|---|---|
| Active API keys per user | 50 |
| New keys per 24 hours | 20 |
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_KEYenvironment variable (highest precedence), or ~/.stratta/config.json(owner-only, mode0600), written by the first-use prompt ornpx -y @stratta/mcp login.
Details in MCP Reference → Overview.