Keys and Access
The three key types on TRUE, how to create them on the MCP & API page, what each can and cannot do, and how to revoke one.
Three credentials exist. They are issued on the same page in the app (side menu, MCP & API) and they authorise different things.
| Bot key | Sequencer API key | MCP key | |
|---|---|---|---|
| Looks like | tbk_<16 hex> id plus a tbs_… secret | 64 hex characters, sent as apikey_<hex> | true_sk_… |
| Where | MCP & API, tab Bots (/bots), web and mobile | MCP & API, tab API Management (web) or Settings, API Keys (mobile) | MCP & API, tab MCP |
| Authorises | HMAC-signed JSON calls on app.truefinance.ai/api/bot/v1 for ONE account: markets, orders, positions, fills, candles, stream | orders, account reads and the transfers ledger on dex-prod.truefinance.ai | tool calls on app.truefinance.ai/api/v1/mcp |
| Signs | you sign each call with the secret (HMAC-SHA256); TRUE places the venue order for that account | you sign every write with your own Ed25519 key; the API key only identifies the account | nothing; each write tool still needs an in app approval |
| Controls | scope read or read and trade, IP allowlist, per-order and open-position caps in USD, pause and resume | revoke | scope read or trade:execute, revoke |
| Can withdraw | no | no, withdrawals are signed by the account owner wallet | no |
| Lifetime | 90 days by default, 365 max, 10 per user | until revoked | 90 days by default, 365 max, 5 per user |
Bot key
The lane for Hummingbot, ccxt, Freqtrade and any code that speaks the common exchange API vocabulary. Everything about it, headers, endpoints, limits and the connectors, is on Bot API.
Sequencer API key
Pick a delegated signer for a bot rather than your owner key: it can trade the account without being the key that owns it. The raw key is shown once and only its hash is stored, so save it when it appears.
What you are shown is 64 hex characters. What you send is apikey_ followed by those characters. The sequencer routes Authorization: Bearer … by prefix: apikey_ is API key auth, anything else is parsed as a JWT and fails with 401 invalid token format.
Revoke from the same screen, or revoke the delegation at the venue with DELETE /v1/accounts/delegated_keys/{public_key}.
MCP key
Scopes: read (portfolio, prices, news, watchlist, points) and trade:execute (orders, agents, copy trading; each order still needs an in app approval, and leveraged orders never auto approve). The Connected Apps tab shows which assistant holds which grant and lets you cut it.
What a leaked key can do
A leaked sequencer key can place, modify and cancel orders on your account until you revoke it. It cannot withdraw and cannot change the owner. A leaked MCP key with trade:execute can propose trades, each of which still needs your approval in the app; with read it can see balances and positions. Revoke first, then rotate.
What landed, what is planned
The IP allowlist per key (requests from other addresses are refused with 403 ip_not_allowed, not rate limited), per-key rate limit headers and API key authentication on the market data WebSocket (POST /api/bot/v1/ws-token) shipped with the Bot API. Still planned: the same controls on the sequencer API key itself, and self-service tiers. See Limits and Security.