Send the key on every request:
Authorization: Bearer dbk_live_...Do not use a Clerk JWT. Keys are created under MCP & API in the app and shown once.
| Scope | Access |
|---|---|
read:account | Current user, statistics, positions, position legs, and your emitters |
read:automations | Followers, bots, emitters, portfolios, and summaries |
read:orders | Automation orders and terminal orders, positions, and exchange balances |
read:signals | Emitter signals |
read:backtests | Backtest jobs, signals, and quota |
read:markets | Tickers, markets, exchanges, marketplace search, candles, order book, trades, funding |
| Scope | Access | Extra gate |
|---|---|---|
write:lifecycle |
Start/stop followers, bots, emitters, and portfolios | feat:api:write (institutional) |
write:automation |
Create a follower; patch owned automations | feat:api:write (institutional) |
write:backtest |
Create or cancel a backtest (REST and MCP) | feat:api:write (institutional) |
write:terminal |
Place or cancel a terminal order (REST and MCP) | feat:terminal (Pro or Institutional) |
Pro keys default to all read:* scopes. Write scopes are opt-in at key creation when your plan allows them.
Send Idempotency-Key on every mutating request so retries stay safe.
Automation start/stop is REST-only; MCP cannot start or stop automations.