Skip to main content

​
Finding Your API Key

Your Unbound API key is already generated for you — there is no “create key” step. One key covers every tool Unbound sets up from the command line. Roo Code, Cline, Kilo Code and Custom Access are the exception: each holds its own key.

​
From the dashboard

1

Open Configure

Log in at gateway.getunbound.ai, or your organization’s custom domain, and click Configure in the top-right of the header.
2

Copy the install command in step 3

Your key is inside it — masked on screen, complete when you copy.

​
From the command line

unbound tools connect <TOOL_TYPE> prints the key for any tool, including the four that hold their own:
It returns Tool Type, Status, API Key, Application ID and Application Name. Running it again returns the same key rather than issuing a new one, so it is safe to repeat. The types it accepts are CLAUDE_CODE, CURSOR, COPILOT, AUGMENT_CODE, ROO_CODE, CLINE, GEMINI_CLI, CODEX, KILO_CODE and CUSTOM_ACCESS. --help also lists UNBOUND_CODEX, which is rejected — see the CLI reference.
The Configure button appears for Admin and Analytics Viewer. Other roles can open /configure directly, or use the command line — run unbound login first, which stores your key in ~/.unbound/config.json.
Your API key is sensitive. Never share it publicly, commit it to a git repository, or expose it in client-side code.

​
Don’t See an API Key?

If you reach the page but no key is shown:
  • “Your API key is being generated. This usually takes a few moments.” — a new account’s key is still being created. Wait a moment and refresh. The page adds “If this message persists, please contact our support team for assistance” — that route is support@unboundsecurity.ai.
  • Make sure you’re logged into the correct organization
  • Verify you have the necessary permissions — contact your organization administrator if you’re a new user
  • Some enterprise configurations require admins to enable tools before API keys become available
If the page itself won’t load and you see “Unable to load configuration data. Please try again later.”, that is a loading failure rather than a permissions problem — refresh, and contact support@unboundsecurity.ai if it repeats.

​
Where the Key Goes, Tool by Tool

For Roo Code, Cline, Kilo Code and Custom Access, one Unbound key covers every model your organization has enabled — you don’t need a separate key per provider.

​
How Tools Display API Keys

Tools fall into two groups. Their own key — Roo Code, Cline, Kilo Code, Custom Access. Each holds a separate key, and regenerating one leaves the others alone. unbound tools connect <TOOL_TYPE> prints the one you need. The shared key — Cursor, Claude Code, Codex, Gemini CLI, Copilot, Cowork. These use one key between them, already inside the command Configure builds, so copying the whole command is enough.

​
Getting a new key

Key rotation is an admin action. Ask an organization admin to rotate yours from Configure → Actions → Rotate API Keys.
Rotating a key immediately invalidates the old one. Any tool still holding it stops working until you copy the new key in.

​
Rotating keys for other people

Admins can rotate other members’ keys in bulk from Configure → Actions → Rotate API Keys. Select up to five members at a time, type ROTATE to confirm, and the rotation runs in the background — you’ll be notified when it finishes.
This invalidates the selected members’ keys immediately. Any tool or device still holding an old key stops working until that person copies the new one.
There is no self-service way to rotate your own key — ask an admin to do it for you.