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

# API Keys and Connected Apps

> Manage REST API keys, MCP OAuth apps, and Telegram bot setup from the Centaur app.

Centaur separates API keys, MCP connected apps, and Telegram bot setup.

## API keys

Use API keys for REST integrations and custom clients.

API keys are managed from the Centaur app:

```text theme={null}
/settings/api-keys
```

API keys authenticate REST requests with:

```text theme={null}
x-api-key: <api-key>
```

Default API keys are scoped to the read families enabled for the account. A key can be valid for one endpoint family and still return `403` for another if it lacks that scope.

## Connected Apps

Connected Apps are MCP OAuth clients connected to your Centaur account.

They are managed from:

```text theme={null}
/settings/apps
```

Use Connected Apps to review which MCP clients have been authorized. Removing a connected app revokes that app's access, but it does not delete REST API keys.

## Telegram bot

Telegram bot setup is a product notification workflow. It is managed separately from REST and MCP credentials.

Following a trader or asset can prompt Telegram bot setup when the bot is not connected, but bot setup does not grant API or MCP access.

## Which credential should I use?

| Need                                           | Use                     |
| ---------------------------------------------- | ----------------------- |
| Backend integration or script                  | REST API key            |
| Claude, ChatGPT, Cursor, Codex, or Claude Code | MCP OAuth               |
| Telegram alerts                                | Telegram bot connection |

Use OAuth for MCP clients. Use API keys for REST integrations.