{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/crypto-exchanges.stream-updates/",
    "json": "https://www.anchorterminal.com/niches/crypto-exchanges.stream-updates/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/crypto-exchanges.stream-updates/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/crypto-exchanges.stream-updates/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 15 | 20 | 5 | 4 |\n\n## What counts as done\n\nSubscribed 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.\n\nHow 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\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)**: 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.\n- **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).\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **dYdX (dYdX Trading Inc.)**: The subaccounts channel carries position, order and fill updates; the compression requirement and resubscription are not on the page read.\n- **Gemini Exchange API (Gemini Trust Company, LLC)**: Order events WebSocket and market streams documented; resubscription behaviour not read.\n- **HTX trading API (HTX)**: orders#, trade.clearing# and accounts.update# private topics; resubscription after a drop is not documented.\n- **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).\n- **MEXC API (MEXC (Comoros) Ltd)**: spot@private.orders.v3.api and spot@private.deals.v3.api with a listenKey; resubscription is not documented.\n- **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.\n- **Upbit Open API (Dunamu Inc.)**: myOrder WebSocket sends order and fill events; resubscription after a drop is not described.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **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.\n- **Gate (Gate)**: WebSocket docs are on gate.com, which answered 403; neither MCP README lists streaming tools.\n- **Kraken API (Payward, Inc.)**: WebSocket v2 private channels were not read in this pass and kraken-mcp lists no streaming service.\n- **KuCoin (KuCoin)**: WebSocket pages render by script and were not read.\n\n- not this job: Coinbase MCP server (Coinbase for Agents) (Coinbase, Inc.): No streaming or subscription tools.\n- not this job: Uniswap Trading API (Uniswap Labs): No WebSocket.\n\n## What stops agents finishing\n\n- official SDK drops post-connect subscriptions on reconnect and duplicates the rest\n- delegated API wallet cannot subscribe to the master's fills or order updates\n- compression required on the indexer WebSocket or the connection is refused (dYdX)\n\n## Around it\n\nBefore: crypto-exchanges.place-order. After: crypto-exchanges.protective-orders, notifications.telegram-alert.\n\n## Where this comes from\n\nWeight 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\n\nAs 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.\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": "Stream fills, order updates and prices over WebSocket",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": null,
    "h1": "Stream fills, order updates and prices over WebSocket",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/crypto-exchanges.stream-updates/",
    "published": "",
    "section": "agents",
    "title": "Stream fills, order updates and prices over WebSocket | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/crypto-exchanges.stream-updates/"
  },
  "tokens": {
    "markdown": 1450,
    "slim": 380
  },
  "version": 1
}
