Skip to main content
Every Locus Pro key goes through the same life: you create it, store it, use it, rotate it, and eventually revoke it. This page is for workspace owners and admins who manage keys.

How it works

Locus shows a key’s value once, when you create or rotate it, and stores only a hash. Rotation swaps the value but keeps the key’s settings. Revocation ends the key for good.

Create and store a key

1

Verify your identity

Sign in as a workspace owner or admin and complete MFA or passkey verification when prompted.
2

Create the key

Open Connect → API keys and select Create key. Choose what the key is for, then the scopes or tool set it needs.
3

Store and test

Save the value in your server’s secret manager; Locus shows it only once. Test the integration before you retire any old credential.
Never put a secret key in browser code, a mobile app, a prompt, or a source repository. For customer-facing browser features, issue a short-lived end-user token on your server.
A key can’t create other secret keys. Review key changes under Audit log on Connect → API keys.

Lifetime, rotation, and revocation

Use the rotation overlap to deploy the new value before the old one stops working. Revoking is immediate and permanent for every kind of key, so create a new key if you need access again. Revoke end-user tokens one at a time, or all of a customer’s tokens by retiring the customer. Revoke connected apps under Connected apps.

Automate agent keys

A server key with both credentials:manage and credits:move can create or rotate agent keys, or move one to another tool set, without human verification. Revoking needs only credentials:manage. In the dashboard, the same actions need an owner or admin with recent verification. See Agent keys for what each agent key controls.

Next steps

API keys

Pick the right kind of key.

Authentication and scopes

Limit what each credential can do.