# Stream fills, order updates and prices over WebSocket

> Stream fills, order updates and prices over WebSocket: 0 companies fully do it, 15 with a limit, 20 carry the tag. Every listing in Crypto exchanges with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/crypto-exchanges.stream-updates/
- Markdown: https://www.anchorterminal.com/niches/crypto-exchanges.stream-updates/index.md (~1,450 tokens)
- Slim: https://www.anchorterminal.com/niches/crypto-exchanges.stream-updates/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/crypto-exchanges.stream-updates/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 15 | 20 | 5 | 4 |

## 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

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.

- **Binance API (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.
- **Bitfinex API (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).
- **Bitget (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.
- **Bithumb Open API (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.
- **Bybit (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.
- **Coinbase Advanced Trade API (Coinbase, Inc.)**: The user channel carries orders, fills, positions and portfolio updates; the channels page does not say how to resume after a reconnect.
- **Crypto.com Exchange API (Foris DAX Limited)**: A stream group covers ticker, book, orders, positions and user trades; reconnect and resubscribe behaviour is not described.
- **Deribit (Deribit FZE)**: Subscription channels for user orders and trades are documented in the AsyncAPI spec; resubscription after a drop is left to the client.
- **dYdX (dYdX Trading Inc.)**: The subaccounts channel carries position, order and fill updates; the compression requirement and resubscription are not on the page read.
- **Gemini Exchange API (Gemini Trust Company, LLC)**: Order events WebSocket and market streams documented; resubscription behaviour not read.
- **HTX trading API (HTX)**: orders#, trade.clearing# and accounts.update# private topics; resubscription after a drop is not documented.
- **Hyperliquid (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).
- **MEXC API (MEXC (Comoros) Ltd)**: spot@private.orders.v3.api and spot@private.deals.v3.api with a listenKey; resubscription is not documented.
- **OKX API (Aux Cayes FinTech Co. Ltd.)**: Order and fills WebSocket channels are documented; resubscription after a drop is not described in the sections read.
- **Upbit Open API (Dunamu Inc.)**: myOrder WebSocket sends order and fill events; resubscription after a drop is not described.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Bitstamp API (Bitstamp Ltd.)**: The WebSocket v2 documentation page returned 212 bytes to a plain fetch, so private channels and reconnect behaviour were not read.
- **Gate (Gate)**: WebSocket docs are on gate.com, which answered 403; neither MCP README lists streaming tools.
- **Kraken API (Payward, Inc.)**: WebSocket v2 private channels were not read in this pass and kraken-mcp lists no streaming service.
- **KuCoin (KuCoin)**: WebSocket pages render by script and were not read.

- not this job: Coinbase MCP server (Coinbase for Agents) (Coinbase, Inc.): No streaming or subscription tools.
- not this job: Uniswap Trading API (Uniswap Labs): No WebSocket.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/crypto-exchanges.stream-updates.json, or the MCP tool get_use_case with id crypto-exchanges.stream-updates. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
