Connect the agent to an account with the least permission
Four or more companies' docs show a full fit.
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 8
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Bitfinex API C 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. source |
| Bybit C 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. source |
| Coinbase Advanced Trade API B 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. source |
| Deribit C Deribit FZE | Scopes per area (trade:read_write, wallet:none, account:read) with IP limits and expiry; edit_api_key reads and changes them. source |
| dYdX BB dYdX Trading Inc. | Permissioned keys compose a signature authenticator with a message filter limited to MsgPlaceOrder on one subaccount. source |
| Gemini Exchange API BB Gemini Trust Company, LLC | API key roles: order endpoints require the Trader role and OAuth scopes such as orders:read; Fund Manager is separate. source |
| Kraken API BB 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. source |
| MEXC API C MEXC (Comoros) Ltd | Endpoints are labelled with permissions such as SPOT_ACCOUNT_R and SPOT_DEAL_WRITE; IP whitelist errors 700006. source |
Does the job, with a limit 12
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.
| Listing | Why |
|---|---|
| Binance API B 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. source |
| Bitget C 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. source |
| Bithumb Open API D 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. source |
| Bitstamp API D 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. source |
| Coinbase MCP server (Coinbase for Agents) C 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. source |
| Crypto.com Exchange API D 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. source |
| Gate C 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. source |
| HTX trading API E HTX | Keys carry Read, Trade and Withdraw permissions with IP binding; sub-user keys exist; no key-permissions endpoint was seen. source |
| Hyperliquid D 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). source |
| KuCoin C 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. source |
| OKX API B 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. source |
| Upbit Open API C Dunamu Inc. | Keys carry per-function permissions and a registered IPv4, but are issued only on the PC web site after Korean identity verification. source |
Doesn't do this job 1
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Uniswap Trading API B Uniswap Labs | A single x-api-key with no scopes; the agent trades from its own wallet. source |
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)
The same as data: /api/v1/use-cases/crypto-exchanges.scoped-access.json, or the MCP tool get_use_case with id crypto-exchanges.scoped-access. Other jobs in this category: /api/v1/niches?category=crypto-exchanges.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.