{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/crypto-exchanges.scoped-access/",
    "json": "https://www.anchorterminal.com/niches/crypto-exchanges.scoped-access/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/crypto-exchanges.scoped-access/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/crypto-exchanges.scoped-access/index.min.md"
  },
  "markdown": "Four or more companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 8 | 11 | 20 | 12 | 10 |\n\n## What counts as done\n\nA 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.\n\nHow 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\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **dYdX (dYdX Trading Inc.)**: Permissioned keys compose a signature authenticator with a message filter limited to MsgPlaceOrder on one subaccount.\n- **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.\n- **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.\n- **MEXC API (MEXC (Comoros) Ltd)**: Endpoints are labelled with permissions such as SPOT_ACCOUNT_R and SPOT_DEAL_WRITE; IP whitelist errors 700006.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **HTX trading API (HTX)**: Keys carry Read, Trade and Withdraw permissions with IP binding; sub-user keys exist; no key-permissions endpoint was seen.\n- **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).\n- **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.\n- **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.\n- **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.\n\n- not this job: Uniswap Trading API (Uniswap Labs): A single x-api-key with no scopes; the agent trades from its own wallet.\n\n## What stops agents finishing\n\n- keys issued only after national identity verification on the PC web site (Upbit, Bithumb)\n- hosted MCP admits only allowlisted clients; others need the CLI and a key (Coinbase)\n- OAuth refresh fails after an hour on a generic client\n- signature accepted by one TLS stack and refused by another\n\n## Around it\n\nBefore: chat.user-instruction, wallets.create-wallet. After: crypto-exchanges.rehearse-no-money, crypto-exchanges.mcp-from-assistant.\n\n## Where this comes from\n\nWeight 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)\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Connect the agent to an account with the least permission",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": null,
    "h1": "Connect the agent to an account with the least permission",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/crypto-exchanges.scoped-access/",
    "published": "",
    "section": "agents",
    "title": "Connect the agent to an account with the least permission | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/crypto-exchanges.scoped-access/"
  },
  "tokens": {
    "markdown": 1600,
    "slim": 380
  },
  "version": 1
}
