> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getunbound.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Find Your Unbound API Key

> Step-by-step guide to finding, creating, and managing your Unbound API key for Claude Code, Roo Code, Cursor, and other tools

## Finding Your API Key

Your Unbound API key is already generated for you — there is no "create key" step. The setup command on Configure already carries it. Roo Code, Cline, Kilo Code and Custom Access are the tools where you paste the key in by hand.

## From the dashboard

<Steps>
  <Step title="Open Configure">
    Log in at [gateway.getunbound.ai](https://gateway.getunbound.ai), or your organization's custom domain, and click **Configure** in the top-right of the header.
  </Step>

  <Step title="Copy the install command in step 3">
    Your key is inside it — masked on screen, complete when you copy.
  </Step>
</Steps>

## From the command line

`unbound tools connect <TOOL_TYPE>` prints the key for a tool, including the four you paste in by hand:

```bash theme={null}
unbound tools connect ROO_CODE
unbound tools connect CLINE
unbound tools connect KILO_CODE
unbound tools connect CUSTOM_ACCESS
```

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`.

<Note>
  The **Configure** button appears for **Admin** and **Analytics Viewer**. Analytics Viewers see a CLI quickstart with the `unbound login --api-key ...` command instead of the three install steps; copy the key from that command. Other roles have no console, so use the command line — run `unbound login` first, which stores your key in `~/.unbound/config.json`.
</Note>

<Warning>
  Your API key is sensitive. Never share it publicly, commit it to a git repository, or expose it in client-side code.
</Warning>

## 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](mailto: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](mailto:support@unboundsecurity.ai) if it repeats.

## Where the Key Goes, Tool by Tool

| Tool | How the key reaches it |
| - | - |
| **Cursor · Claude Code · Codex · Copilot** | The setup command on the tool's page already carries your key. Copy it and run it — there is nothing to paste by hand |
| **Cowork** | The tool's page gives you a connection endpoint and an `Authorization: Bearer` header with the key already in it |
| **Roo Code** | Roo Code settings → select **unbound** as the API provider → paste the key into **Unbound API Key** |
| **Kilo Code** | Kilo Code in your IDE, or the `kilocode` CLI → select **Unbound** as the provider → paste the key into **Unbound API Key** |
| **Cline** | Cline settings → **OpenAI Compatible** provider → paste the base URL and the key, both shown on the Cline page |
| **Custom Access** | The cURL and Python examples on the page already contain the key |

<Tip>
  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.
</Tip>

## Getting a new key

Key rotation is an admin action. Ask an organization admin to rotate yours from **Configure → Actions → Rotate API Keys**.

<Warning>
  Rotating a key **immediately invalidates the old one**. Any tool still holding it stops working until you copy the new key in.
</Warning>

### 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.

<Warning>
  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.
</Warning>

There is no self-service way to rotate your own key — ask an admin to do it for you.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.