Stream fills, order updates and prices over WebSocket
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
Subscribed streams deliver each event once, resume after a reconnect without the agent re-subscribing by hand, and private streams carry fills for the account the agent trades.
How agents ask for it: tell me the moment this fills
, keep a live order book
, subscribe to my order updates
, watch the price and wake me at 65,000
Does the job, with a limit 15
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 | User data stream sends executionReport order and fill events; connections are cut at 24 hours and the docs give no resubscribe mechanism, so the agent reconnects and resubscribes itself. source |
| Bitfinex API C iFinex Inc. | Authenticated WebSocket sends on, ou and oc order events and trade events; resubscription after a drop is not documented and the official Node client has unanswered issues back to 2020 (acc-37). source |
| Bitget C BTG Technology Holdings Limited | Public and private WebSocket hosts, with demo equivalents, are documented; resubscription after a disconnect is not described in the pages read. source |
| Bithumb Open API D Bithumb Co., Ltd. | Private v2 myOrder and myAsset streams carry order and fill events; reconnect and resubscribe behaviour is not described on the page read. source |
| Bybit C Bybit Virtual Asset Platform Operator L.L.C. S.P.C | Private order and position streams exist and demo has a private stream host; the connect page says reconnect as soon as possible and says nothing about resubscribing. source |
| Coinbase Advanced Trade API B Coinbase, Inc. | The user channel carries orders, fills, positions and portfolio updates; the channels page does not say how to resume after a reconnect. source |
| Crypto.com Exchange API D Foris DAX Limited | A stream group covers ticker, book, orders, positions and user trades; reconnect and resubscribe behaviour is not described. source |
| Deribit C Deribit FZE | Subscription channels for user orders and trades are documented in the AsyncAPI spec; resubscription after a drop is left to the client. source |
| dYdX BB dYdX Trading Inc. | The subaccounts channel carries position, order and fill updates; the compression requirement and resubscription are not on the page read. source |
| Gemini Exchange API BB Gemini Trust Company, LLC | Order events WebSocket and market streams documented; resubscription behaviour not read. source |
| HTX trading API E HTX | orders#, trade.clearing# and accounts.update# private topics; resubscription after a drop is not documented. source |
| Hyperliquid D Hyperliquid Labs | userFills, orderUpdates and userEvents subscriptions exist; the official Python SDK drops post-connect subscriptions on reconnect (acc-08) and an API wallet cannot receive user events (acc-09). source |
| MEXC API C MEXC (Comoros) Ltd | spot@private.orders.v3.api and spot@private.deals.v3.api with a listenKey; resubscription is not documented. source |
| OKX API B Aux Cayes FinTech Co. Ltd. | Order and fills WebSocket channels are documented; resubscription after a drop is not described in the sections read. source |
| Upbit Open API C Dunamu Inc. | myOrder WebSocket sends order and fill events; resubscription after a drop is not described. source |
Couldn't check 4
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Bitstamp API D Bitstamp Ltd. | The WebSocket v2 documentation page returned 212 bytes to a plain fetch, so private channels and reconnect behaviour were not read. |
| Gate C Gate | WebSocket docs are on gate.com, which answered 403; neither MCP README lists streaming tools. |
| Kraken API BB Payward, Inc. | WebSocket v2 private channels were not read in this pass and kraken-mcp lists no streaming service. |
| KuCoin C KuCoin | WebSocket pages render by script and were not read. |
Doesn't do this job 2
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Coinbase MCP server (Coinbase for Agents) C Coinbase, Inc. | No streaming or subscription tools. source |
| Uniswap Trading API B Uniswap Labs | No WebSocket. source |
What stops agents finishing
- official SDK drops post-connect subscriptions on reconnect and duplicates the rest
- delegated API wallet cannot subscribe to the master's fills or order updates
- compression required on the indexer WebSocket or the connection is refused (dYdX)
Around it
Before: crypto-exchanges.place-order. After: crypto-exchanges.protective-orders, notifications.telegram-alert.
Where this comes from
Weight 5 of 100 in Crypto exchanges: 4 of 40 accounts; the SDK bug in acc-08 (streams go dead after one disconnect) is the sharpest failure in the category
The same as data: /api/v1/use-cases/crypto-exchanges.stream-updates.json, or the MCP tool get_use_case with id crypto-exchanges.stream-updates. 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.