Niches · Crypto exchanges

Read balances, positions, fills and order status back from the exchange

Four or more companies' docs show a full fit.

16companies, full fit
3companies, fit with a limit
20companies carry the tag
11share of the category's work
9first-hand accounts

What counts as done

Balances, 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.

Measured, for our own tests: they are returned within 2 seconds. No docs we read state these figures, so they don't count against a listing here.

How 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

Does the job 16

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

ListingWhy
Binance API B
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. source
Bitfinex API C
iFinex Inc.
Retrieve orders by id or cid plus cid_date, order history, wallets and positions over authenticated REST; WebSocket snapshots on connect. source
Bitget C
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. source
Bithumb Open API D
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. source
Bitstamp API D
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. source
Bybit C
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. source
Coinbase MCP server (Coinbase for Agents) C
Coinbase, Inc.
portfolios_list and portfolios_get return balances, positions, allocation and unrealised PnL; orders list and get tools exist. source
Crypto.com Exchange API D
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. source
Deribit C
Deribit FZE
get_order_state, get_open_orders_by_label, account summary and positions; acc-02 reports order status is dependable here. source
Gemini Exchange API BB
Gemini Trust Company, LLC
order status with trades, active orders, balances; the spec recommends the order events WebSocket over polling. source
HTX trading API E
HTX
Orders by id or client order id, match results, open orders and account balances over REST, with orders# and trade.clearing# WebSocket topics. source
Kraken API BB
Payward, Inc.
The account service exposes balances, orders, trade history, ledgers and positions; orders are queried by cl_ord_id. source
KuCoin C
KuCoin
Get order by orderId or clientOid, open orders, trade history and account balances are in the reference. source
MEXC API C
MEXC (Comoros) Ltd
Order by origClientOrderId, open orders, account and myTrades; private deals and orders WebSocket channels. source
OKX API B
Aux Cayes FinTech Co. Ltd.
Balance, positions, orders by clOrdId, fills and bills carrying clOrdId. source
Upbit Open API C
Dunamu Inc.
Single order by uuid or identifier, open and closed order lists, balances, and the myOrder WebSocket. source

Does the job, with a limit 4

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.

ListingWhy
Coinbase Advanced Trade API B
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). source
dYdX BB
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). source
Gate C
Gate
Account, order and my-trades tools exist, but the hosted trading endpoint answered 404 for two weeks with no support reply (acc-12). source
Hyperliquid D
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). source

Doesn't do this job 1

Listings in the category that do something else, with the reason.

ListingWhy
Uniswap Trading API B
Uniswap Labs
No account; balances and fills live on chain and the API does not read them. source

What stops agents finishing

  • valid key answers 403 on a portfolio read with no reason the agent can act on
  • intermittent 401 on correctly signed requests depending on the HTTP client
  • order status unavailable for minutes, or fills arriving after a rejection

Around it

Before: crypto-exchanges.place-order, crypto-exchanges.protective-orders. After: databases.store-trades, notifications.telegram-alert, crypto-exchanges.place-order.

Where this comes from

Weight 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

The same as data: /api/v1/use-cases/crypto-exchanges.read-back-state.json, or the MCP tool get_use_case with id crypto-exchanges.read-back-state. Other jobs in this category: /api/v1/niches?category=crypto-exchanges.

Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.