# Connect the agent to an account with the least permission

> Connect the agent to an account with the least permission: 8 companies fully do it, 11 with a limit, 20 carry the tag. Every listing in Crypto exchanges with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/crypto-exchanges.scoped-access/
- Markdown: https://www.anchorterminal.com/niches/crypto-exchanges.scoped-access/index.md (~1,600 tokens)
- Slim: https://www.anchorterminal.com/niches/crypto-exchanges.scoped-access/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/crypto-exchanges.scoped-access/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 8 | 11 | 20 | 12 | 10 |

## What counts as done

A credential that can do the task's reads and trades and nothing else, with withdrawal off, that the agent can verify by calling a key-permissions or balance endpoint, held outside prompts and logs.

How agents ask for it: give the bot a key that can trade but not withdraw; approve an API wallet for the agent; connect my exchange account to Claude; restrict the key to my IP and one portfolio

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Bitfinex API (iFinex Inc.)**: Keys carry read and write bits per scope (account, orders, positions, wallets, withdraw and so on) and the key-permissions endpoint returns them so the agent can verify withdraw is off.
- **Bybit (Bybit Virtual Asset Platform Operator L.L.C. S.P.C)**: Keys carry permission groups, a readOnly flag, an IP list and an expiry; the apikey-info endpoint returns them so the agent can verify Withdraw is absent.
- **Coinbase Advanced Trade API (Coinbase, Inc.)**: Keys take view, trade and transfer permissions, a portfolio restriction and an IP allowlist; the key permissions endpoint lets the agent read them back.
- **Deribit (Deribit FZE)**: Scopes per area (trade:read_write, wallet:none, account:read) with IP limits and expiry; edit_api_key reads and changes them.
- **dYdX (dYdX Trading Inc.)**: Permissioned keys compose a signature authenticator with a message filter limited to MsgPlaceOrder on one subaccount.
- **Gemini Exchange API (Gemini Trust Company, LLC)**: API key roles: order endpoints require the Trader role and OAuth scopes such as orders:read; Fund Manager is separate.
- **Kraken API (Payward, Inc.)**: kraken auth login mints a restricted key that cannot withdraw, with --read-only and --valid-for options; acc-35 proposes a read-only skill on top.
- **MEXC API (MEXC (Comoros) Ltd)**: Endpoints are labelled with permissions such as SPOT_ACCOUNT_R and SPOT_DEAL_WRITE; IP whitelist errors 700006.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Binance API (Binance)**: The MCP route grants scopes at connect time with no withdrawal scope and an isolated sub-account; REST key permissions and IP restriction live in the account UI and FAQ, not opened here.
- **Bitget (BTG Technology Holdings Limited)**: Keys are read or read-and-write with no separate withdrawal permission in the guide, and IP binding is recommended rather than required.
- **Bithumb Open API (Bithumb Co., Ltd.)**: Keys carry per-function permissions and an IP registration, and the CLI has a read_only profile; keys are issued only on the web site after Korean identity verification.
- **Bitstamp API (Bitstamp Ltd.)**: Keys have per-endpoint permissions and IP allow-lists (API0002, API0003 errors); the key management pages load by script so the permission list was not read.
- **Coinbase MCP server (Coinbase for Agents) (Coinbase, Inc.)**: The person picks portfolios on the OAuth approval screen; agent portfolios are spot-only and no withdrawal exists; but only allowlisted clients can connect and others need a CDP key.
- **Crypto.com Exchange API (Foris DAX Limited)**: Keys go in CDCX_API_KEY and CDCX_API_SECRET or a 0600 config; no key-permissions read is documented and the API docs host is unreadable.
- **Gate (Gate)**: OAuth scopes base, spot_trade, futures_trade and so on; base is not read-only; key permission groups are on gate.com, unreadable here.
- **HTX trading API (HTX)**: Keys carry Read, Trade and Withdraw permissions with IP binding; sub-user keys exist; no key-permissions endpoint was seen.
- **Hyperliquid (Hyperliquid Labs)**: approveAgent registers an API wallet with a name and expiry that can only sign; it cannot withdraw, but it also cannot subscribe to the master's fills (acc-09).
- **KuCoin (KuCoin)**: Keys take General, Spot or Futures permissions with an IP whitelist required for trading rights; trading keys without activity are disabled after 30 days.
- **OKX API (Aux Cayes FinTech Co. Ltd.)**: Keys with Read and Trade and IP binding; the kit registers no order tools when the key lacks trading permission; EEA and US accounts must use regional hosts.
- **Upbit Open API (Dunamu Inc.)**: Keys carry per-function permissions and a registered IPv4, but are issued only on the PC web site after Korean identity verification.

- not this job: Uniswap Trading API (Uniswap Labs): A single x-api-key with no scopes; the agent trades from its own wallet.

## What stops agents finishing

- keys issued only after national identity verification on the PC web site (Upbit, Bithumb)
- hosted MCP admits only allowlisted clients; others need the CLI and a key (Coinbase)
- OAuth refresh fails after an hour on a generic client
- signature accepted by one TLS stack and refused by another

## Around it

Before: chat.user-instruction, wallets.create-wallet. After: crypto-exchanges.rehearse-no-money, crypto-exchanges.mcp-from-assistant.

## Where this comes from

Weight 12 of 100 in Crypto exchanges: 10 of 40 accounts describe key or wallet set-up; one builder enabled withdrawals by accident (acc-33) and one found the delegated wallet cannot see fills (acc-09)

As data: https://www.anchorterminal.com/api/v1/use-cases/crypto-exchanges.scoped-access.json, or the MCP tool get_use_case with id crypto-exchanges.scoped-access. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
