{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/crypto-exchanges.read-back-state/",
    "json": "https://www.anchorterminal.com/niches/crypto-exchanges.read-back-state/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/crypto-exchanges.read-back-state/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/crypto-exchanges.read-back-state/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| 16 | 3 | 20 | 11 | 9 |\n\n## What counts as done\n\nBalances, positions and the named order's status and fills returned, consistent with each other, with the exchange treated as the source of truth for position size.\n\nMeasured, for our own tests: they are returned within 2 seconds.\n\nHow agents ask for it: what is my balance; did that order fill; show my open positions and their stops; reconcile what the bot thinks it holds against the exchange\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Binance API (Binance)**: GET /api/v3/order by origClientOrderId, account balances and myTrades; the docs say a 5xx or -1007 TIMEOUT means status UNKNOWN, not failed, so look the order up before retrying.\n- **Bitfinex API (iFinex Inc.)**: Retrieve orders by id or cid plus cid_date, order history, wallets and positions over authenticated REST; WebSocket snapshots on connect.\n- **Bitget (BTG Technology Holdings Limited)**: Account, position and order detail endpoints; the docs say to query by clientOid after 40010, 40725 or 45001 to learn the final result.\n- **Bithumb Open API (Bithumb Co., Ltd.)**: Single order by uuid or client_order_id, order lists by state, assets via account tools, and the myOrder WebSocket for fill events.\n- **Bitstamp API (Bitstamp Ltd.)**: Balances, open orders and order status by id or orig_client_order_id (400.072); 500.016 says a timed-out order should be checked by its order_id.\n- **Bybit (Bybit Virtual Asset Platform Operator L.L.C. S.P.C)**: Wallet balance, position list and open or recent orders by orderLinkId; orders are confirmed over WebSocket because create-order returns before matching.\n- **Coinbase MCP server (Coinbase for Agents) (Coinbase, Inc.)**: portfolios_list and portfolios_get return balances, positions, allocation and unrealised PnL; orders list and get tools exist.\n- **Crypto.com Exchange API (Foris DAX Limited)**: account summary, open orders, order detail by order_id or client_oid, positions and user trades in the account and trade groups.\n- **Deribit (Deribit FZE)**: get_order_state, get_open_orders_by_label, account summary and positions; acc-02 reports order status is dependable here.\n- **Gemini Exchange API (Gemini Trust Company, LLC)**: order status with trades, active orders, balances; the spec recommends the order events WebSocket over polling.\n- **HTX trading API (HTX)**: Orders by id or client order id, match results, open orders and account balances over REST, with orders# and trade.clearing# WebSocket topics.\n- **Kraken API (Payward, Inc.)**: The account service exposes balances, orders, trade history, ledgers and positions; orders are queried by cl_ord_id.\n- **KuCoin (KuCoin)**: Get order by orderId or clientOid, open orders, trade history and account balances are in the reference.\n- **MEXC API (MEXC (Comoros) Ltd)**: Order by origClientOrderId, open orders, account and myTrades; private deals and orders WebSocket channels.\n- **OKX API (Aux Cayes FinTech Co. Ltd.)**: Balance, positions, orders by clOrdId, fills and bills carrying clOrdId.\n- **Upbit Open API (Dunamu Inc.)**: Single order by uuid or identifier, open and closed order lists, balances, and the myOrder WebSocket.\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- **Coinbase Advanced Trade API (Coinbase, Inc.)**: Accounts, order by id, fills and portfolio breakdown exist, but a perps portfolio read answered 403 with view and trade permissions (acc-21) and 401s were intermittent (acc-20).\n- **dYdX (dYdX Trading Inc.)**: Subaccount, orders and fills from the indexer; lookup is by indexer order id rather than clientId, and order type can be misreported (acc-19).\n- **Gate (Gate)**: Account, order and my-trades tools exist, but the hosted trading endpoint answered 404 for two weeks with no support reply (acc-12).\n- **Hyperliquid (Hyperliquid Labs)**: clearinghouseState, orderStatus by oid or cloid and userFills; queries must use the master address, not the API wallet, or the result is empty (acc-10).\n\n- not this job: Uniswap Trading API (Uniswap Labs): No account; balances and fills live on chain and the API does not read them.\n\n## What stops agents finishing\n\n- valid key answers 403 on a portfolio read with no reason the agent can act on\n- intermittent 401 on correctly signed requests depending on the HTTP client\n- order status unavailable for minutes, or fills arriving after a rejection\n\n## Around it\n\nBefore: crypto-exchanges.place-order, crypto-exchanges.protective-orders. After: databases.store-trades, notifications.telegram-alert, crypto-exchanges.place-order.\n\n## Where this comes from\n\nWeight 11 of 100 in Crypto exchanges: 9 of 40 accounts; two (acc-02, acc-19) say order status or order type cannot be trusted and two (acc-21, acc-20) could not read at all with a valid key\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/crypto-exchanges.read-back-state.json, or the MCP tool get_use_case with id crypto-exchanges.read-back-state. 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": "Read balances, positions, fills and order status back from the exchange",
        "url": ""
      }
    ],
    "description": "Read balances, positions, fills and order status back from the exchange: 16 companies fully do it, 3 with a limit, 20 carry the tag. Every listing in Crypto exchanges with the reason and a source.",
    "facts": null,
    "h1": "Read balances, positions, fills and order status back from the exchange",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/crypto-exchanges.read-back-state/",
    "published": "",
    "section": "agents",
    "title": "Read balances, positions, fills and order status back from the…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/crypto-exchanges.read-back-state/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 380
  },
  "version": 1
}
