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

# Authentication

> Create an API key in the dashboard and send it as a bearer token to the REST API and the MCP server. Claude can sign in with OAuth instead.

Every request to the REST API and the MCP server carries an API key in the `Authorization` header:

```http theme={null}
Authorization: Bearer otb_live_…
```

* **Create keys in the dashboard.** Sign in at `app.otbstudio.ai` with a confirmed email address, name the key, and copy it. It is shown once and stored only as a hash: a lost key cannot be recovered, so create another.
* **A key belongs to your organisation.** Every call it makes reads and spends within that organisation. No parameter can point it at another.
* **Unlimited keys.** Give production, staging and each customer integration its own key, so each has its own usage line in the dashboard. A key costs nothing to hold; calls spend credits.
* **Revoking is immediate.** A revoked key fails on its next call.
* **No login flow.** An unattended job or agent needs no browser, only the key. In Claude, the [connector](/mcp.md) signs in with OAuth instead, and reaches the same data with the same organisation's credits.
* **Server-side only.** Never put a key in a browser or a mobile app, where anyone can read it. Call the API from your server.

The base URL is `https://api.otbstudio.ai`.


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