Before you begin
- You need a role with Managed Agents access to see API keys in the console. See Organizations and roles.
- Keys are created and revoked only in the console, while you’re signed in. An API key can’t create or revoke keys.
How keys work
- A key acts as you. Requests run with the role you hold in the target organization, checked on every request.
- The secret is shown once. A key starts with
rma_. After you close the drawer, only a hint such asrma_…a1b2is shown, and the full key can’t be retrieved. - Every key expires. Choose a lifetime of up to 365 days. There’s no “never expires”.
- Keys are yours alone. The list shows only the keys you created, and you’re the only one who can revoke them.
Choose a scope
Your tenant has one organization, Default, so both scopes reach the same resources. Prefer organization scope: it needs no extra header.
Create a key
- Console
- Open the Recursion console. In the sidebar, click API keys, then Create key.
- Enter a Name that says where the key is used, such as
nightly-report-prod. - Choose a lifetime in Expires: 3 hours, 1 day, 7 days, 30 days, 90 days, or Custom date up to one year out. The default is 30 days.
- Linked account shows you. Requests with this key act as you.
- Choose the Scope: Tenant, or one organization, such as Default. It starts on Tenant.
- Click Create key.
- On Save your API key, copy the key and store it in a secret manager. This is the only time it’s shown.
Use a key
Send the key as a bearer token. An organization-scoped key needs nothing else. A tenant-scoped key also sendsx-organization-id.
- TypeScript
- cURL
recursion-organization-id and recursion-tenant-id headers, so you can confirm which organization it ran in.
Key statuses
Filter the list by Status and Scope to find a key.
Revoke a key
- Console
- In API keys, open the actions menu on the key’s row.
- Click Revoke, then Revoke key.
Rotate a key
Rotate before a key expires, or right away if it might have leaked.- Create a new key with the same scope.
- Deploy it to the service that uses the old key.
- Confirm the service works with the new key.
- Revoke the old key.
Keep keys safe
- Store keys in a secret manager or your platform’s secret store. Load them into an environment variable such as
RECURSION_API_KEYat run time. - Never commit a key, put it in a system prompt or session message, or paste it into a chat with an AI assistant.
- Use one key per service or coding agent, so you can revoke one without breaking the others.
- Choose the shortest expiry that works. Short-lived keys limit the damage of a leak.
- Never give a key to an agent running inside Recursion. To give an agent credentials, use a vault.
What a key can’t do
A key only calls Managed Agents operations. It can’t create, list, or revoke API keys.What can go wrong
Limits
See Limits for every other limit.
Next steps
API conventions
Set up a client and learn the request rules.
Organizations and roles
See what each role can do with a key.
Connect a coding agent
Give a coding agent a key safely.
Security
See how credentials and data are protected.