New: pay in USDC at checkout, next to cards — prices and invoices stay in EUR.New: pay in USDC

How it works
Low-Latency Trading Solutions
Cart
Realtime access

Real-time crypto market data — the WebSocket feed of Binance, Coinbase, Kalshi, Polymarket, OKX and Bybit, bought by the UTC day

The feeds of Binance, Coinbase, Kalshi, Polymarket, OKX and Bybit — the Level-2 order book and every trade of every instrument and, on Binance USDT-M, OKX and Bybit, the derivatives topics, nothing sampled — over a plain WebSocket in JSON or SBE, captured at each venue and delivered at our London, Frankfurt, Ashburn, Ohio or Tokyo endpoints over dedicated lines (Binance, OKX and Bybit from Tokyo at London, Frankfurt, Ashburn or Ohio; Coinbase from Ashburn at Ohio or Tokyo; Kalshi from Ohio at Tokyo; Polymarket from London at Tokyo), and at source where the venue is captured (Binance, OKX and Bybit at Tokyo; Coinbase at Ashburn; Kalshi at Ohio; Polymarket at London). You buy whole UTC calendar days per venue and endpoint, self-serve, and connect with one API key.

Venues
6
Markets
7
Endpoints
5
Feed topics
7
Per instrument-day
€49
Latency comparison

Every line, every endpoint — one-way latency

Every line of the product on one table: the venue, where it is captured, the endpoint you connect at and the one-way latency of the line between them. Pick the endpoint nearest your system; a market listens on the same port at every endpoint that serves it, and access is bought per endpoint and market.

VenueCaptured inEndpointSiteLatencyBuy
BinanceTokyoLondonLD4 / AWS London, dedicated fiber~69.3 ms one-wayBinance USDT-M →Binance Spot →
OKXTokyoLondonLD4 / AWS London, dedicated fiber~69.3 ms one-wayOKX →
BybitTokyoLondonLD4 / AWS London, dedicated fiber~69.3 ms one-wayBybit →
BinanceTokyoFrankfurtAWS eu-central-1, dedicated fiber~68.2 ms one-wayBinance USDT-M →Binance Spot →
OKXTokyoFrankfurtAWS eu-central-1, dedicated fiber~68.2 ms one-wayOKX →
BybitTokyoFrankfurtAWS eu-central-1, dedicated fiber~68.2 ms one-wayBybit →
BinanceTokyoAshburnAWS us-east-1, dedicated fiber~67.7 ms one-wayBinance USDT-M →Binance Spot →
OKXTokyoAshburnAWS us-east-1, dedicated fiber~67.7 ms one-wayOKX →
BybitTokyoAshburnAWS us-east-1, dedicated fiber~67.7 ms one-wayBybit →
BinanceTokyoOhioAWS us-east-2, dedicated fiber~64.1 ms one-wayBinance USDT-M →Binance Spot →
CoinbaseAshburnOhioAWS us-east-2, dedicated fiber~4.6 ms one-wayCoinbase Spot →
OKXTokyoOhioAWS us-east-2, dedicated fiber~64.1 ms one-wayOKX →
BybitTokyoOhioAWS us-east-2, dedicated fiber~64.1 ms one-wayBybit →
CoinbaseAshburnTokyoAWS ap-northeast-1, dedicated fiber~67.7 ms one-wayCoinbase Spot →
KalshiOhioTokyoAWS ap-northeast-1, dedicated fiber~64.1 ms one-wayKalshi →
PolymarketLondonTokyoAWS ap-northeast-1, dedicated fiber~69.3 ms one-wayPolymarket →
PolymarketLondonLondonLD4 / AWS London, same site · no lineAt sourcePolymarket →
CoinbaseAshburnAshburnAWS us-east-1, same site · no lineAt sourceCoinbase Spot →
KalshiOhioOhioAWS us-east-2, same site · no lineAt sourceKalshi →
BinanceTokyoTokyoAWS ap-northeast-1, same site · no lineAt sourceBinance USDT-M →Binance Spot →
OKXTokyoTokyoAWS ap-northeast-1, same site · no lineAt sourceOKX →
BybitTokyoTokyoAWS ap-northeast-1, same site · no lineAt sourceBybit →

Binance lines: ~69.3 ms Tokyo → London, ~68.2 ms Tokyo → Frankfurt, ~67.7 ms Tokyo → Ashburn and ~64.1 ms Tokyo → Ohio.

OKX lines: ~69.3 ms Tokyo → London, ~68.2 ms Tokyo → Frankfurt, ~67.7 ms Tokyo → Ashburn and ~64.1 ms Tokyo → Ohio.

Bybit lines: ~69.3 ms Tokyo → London, ~68.2 ms Tokyo → Frankfurt, ~67.7 ms Tokyo → Ashburn and ~64.1 ms Tokyo → Ohio.

Coinbase lines: ~4.6 ms Ashburn → Ohio and ~67.7 ms Ashburn → Tokyo.

Kalshi lines: ~64.1 ms Ohio → Tokyo.

Polymarket lines: ~69.3 ms London → Tokyo.

Latency is one-way line latency from the site where the venue is captured to our endpoint — the venue's own latency and the on-ramp to your client come on top.

At source means the normalized feed is handed over at the site where the venue is captured — no dedicated line, so there is no line latency to quote.

Feed contents

What the feed carries, per market

Every topic below is the same stream our own systems consume — the historical files in the shop are recordings of it, so a backtest maps 1:1 onto production.

The feed is a WebSocket API: one endpoint per market (the port selects the market — Binance USDT-M (port 14004), Binance Spot (port 14003), Coinbase Spot (port 14006), Kalshi (port 14005), Polymarket (port 14007), OKX (port 14008) and Bybit (port 14009)), one API key per account, a documented login and subscribe flow, JSON or SBE on the wire. Trades and quotes come as separate topics: the order book as a snapshot followed by every changed level, trades one by one with side and size, and on Binance USDT-M, OKX and Bybit mark price, index price, funding and liquidations.

Timestamps are the venue's own clock and our receive clock, both in integer nanoseconds, and every order-book update carries an event id and the id it follows, so a gap is visible the moment it happens. The same schema is written to the historical day files, which is what makes a strategy portable from the archive to the live feed.

TopicWhat you receiveBinance USDT-M
port 14004 · London, Frankfurt, Ashburn, Ohio, Tokyo
Binance Spot
port 14003 · London, Frankfurt, Ashburn, Ohio, Tokyo
Coinbase Spot
port 14006 · Ohio, Tokyo, Ashburn
Kalshi
port 14005 · Tokyo, Ohio
Polymarket
port 14007 · Tokyo, London
OKX
port 14008 · London, Frankfurt, Ashburn, Ohio, Tokyo
Bybit
port 14009 · London, Frankfurt, Ashburn, Ohio, Tokyo
Order bookBook snapshot on subscribe, then changed levels only; every event chained by prevEventId → eventId.✓✓✓✓✓✓✓
Top of bookBest bid and ask as its own stream; optional coalescing for slow consumers.✓✓———✓✓
TradesEvery public trade: aggressor side, price, quantity, trade id, exchange timestamp.✓✓✓✓✓✓✓
Mark priceThe venue's mark price as it is republished.✓————✓✓
Index priceThe underlying index price.✓————✓✓
Funding rateCurrent rate, next settlement time and the venue's predicted next rate.✓————✓✓
Liquidations · opt-inLiquidation orders as the venue publishes them: side, price, quantity, exchange timestamp — off by default, opt in per subscribe.✓————✓✓

Mark price, Index price, Funding rate, Liquidations: not part of the Binance Spot feed — these topics never emit there.

Top of book, Mark price, Index price, Funding rate, Liquidations: not part of the Coinbase Spot feed — these topics never emit there.

Top of book, Mark price, Index price, Funding rate, Liquidations: not part of the Kalshi feed — these topics never emit there.

Top of book, Mark price, Index price, Funding rate, Liquidations: not part of the Polymarket feed — these topics never emit there.

  • Market-data streams only — a dedicated route, not general-purpose bandwidth
  • Every instrument of the market: the Level-2 order book and every trade
  • Binance USDT-M, Binance Spot, OKX and Bybit add a separate realtime top-of-book stream
  • Binance USDT-M, OKX and Bybit add mark price, index price, funding rate and liquidations
  • On OKX the topics follow the instrument type: spot carries the order book, top of book and trades; derivatives add mark price, index price and liquidations, perpetual swaps also the funding rate
  • On Bybit the topics follow the instrument type: spot carries the order book, top of book and trades; derivatives add mark price, index price and liquidations, perpetual swaps also the funding rate
  • WebSocket, JSON or SBE — the port selects the market, one API key per account
How it works

How access works

Bought by the UTC calendar day

One day or thirty — paid days start at the next 00:00 UTC and the rest of the purchase day is included free, so access begins the moment the order clears. Longer runs cost less per day. Extend any time from your account, invoice on checkout.

Whole market or single instruments

A market day unlocks every instrument of that market; an instrument day unlocks exactly the instruments you pick. €49 per instrument-day or €99 per market-day; longer runs cost less per day: €90 per market-day from 14 days, €80 from 30, €70 from 180, €60 from 365. Kalshi and Polymarket are sold as whole markets only — contracts list and settle around the clock, so a market day covers every contract. Single OKX instruments: spot and perpetual swaps — dated futures and options come with the whole market. Single Bybit instruments: spot and perpetual swaps — dated futures come with the whole market.

One API key per account

The key is created with your first purchase and shown in your account together with the endpoints. It authenticates the feed and the master-data export, and you can rotate it whenever you want. 3 parallel connections per key and endpoint included (one connection can subscribe to every instrument); +5 more for €10 per day, up to 28, added from your account.

The port selects the market

WebSocket in JSON or SBE, the same protocol and subscribe flow as our documented market-data API: Binance USDT-M (port 14004), Binance Spot (port 14003), Coinbase Spot (port 14006), Kalshi (port 14005), Polymarket (port 14007), OKX (port 14008) and Bybit (port 14009). Instrument master data is a free export from the shop.

Enterprise grade, self-service

The lines a trading firm runs on, bought by the day

Nothing here is a retail tier. The self-serve endpoints hang on the same dedicated lines our own high-frequency trading engine and enterprise feeds use, and they carry the same stream: every message of the feed, nothing sampled, with the venue timestamp and our receive timestamp in nanoseconds and an event-id chain that makes any gap visible.

What changes is how you buy it. Market makers, arbitrage desks and HFT teams take the same product on enterprise terms; here it is €49 per instrument-day or €99 per market-day, longer runs cost less per day: €90 per market-day from 14 days, €80 from 30, €70 from 180, €60 from 365 — by card or in USDC, no sales call, no minimum term, nothing renews. Enterprise subscriptions already cover further locations and venues, together with order entry and T+1 history — see the enterprise tiers.

Price

€49 / instrument · day · €99 / market · day

At source: €35 / instrument · day · €69 / market · day

Captured at each venue and delivered at our London, Frankfurt, Ashburn, Ohio or Tokyo endpoints over dedicated lines (Binance, OKX and Bybit from Tokyo at London, Frankfurt, Ashburn or Ohio; Coinbase from Ashburn at Ohio or Tokyo; Kalshi from Ohio at Tokyo; Polymarket from London at Tokyo), and at source where the venue is captured (Binance, OKX and Bybit at Tokyo; Coinbase at Ashburn; Kalshi at Ohio; Polymarket at London) — over a dedicated line, that line is what the per-day price pays for; at source, the normalized feed at the venue's site. London, Frankfurt, Ashburn, Ohio and Tokyo are the self-serve locations today; more will follow, and enterprise subscriptions already cover further locations and venues. See the enterprise tiers for order entry, T+1 history and monthly API swaps.

Getting started

How to buy real-time market data

  1. Pick the venue — Low-latency Binance market data, Coinbase real-time market data, Kalshi real-time market data, Polymarket real-time market data, OKX real-time market data, Bybit real-time market data — each page lists its endpoints, line latency, feed contents and price.
  2. Choose the endpoint nearest your system and the market; the port selects the market (Binance USDT-M (port 14004), Binance Spot (port 14003), Coinbase Spot (port 14006), Kalshi (port 14005), Polymarket (port 14007), OKX (port 14008) and Bybit (port 14009)).
  3. Pick the scope — a single instrument or the whole market (Kalshi and Polymarket are sold as whole markets only) — and the number of UTC days in the configurator; longer runs cost less per day: €90 per market-day from 14 days, €80 from 30, €70 from 180, €60 from 365.
  4. Pay by card or in USDC: paid days start at the next 00:00 UTC and the rest of the purchase day is included free, and your API key appears in your account with the endpoint URLs.
  5. Connect with the connection guide, or hand the machine-readable spec to a coding agent.
FAQ

Questions about real-time crypto market data

Is real-time crypto market data a subscription?

No — access is bought by the UTC calendar day and nothing renews. €49 per instrument-day or €99 per market-day. At source — the normalized feed at the venue's site, no dedicated line — €35 per instrument-day or €69 per market-day. A market day covers every instrument of that market, an instrument day only the ones you select. Kalshi and Polymarket are sold as whole markets only — contracts list and settle around the clock, so a market day covers every contract. Longer runs cost less per day: over a dedicated line €90 per market-day from 14 days, €80 from 30, €70 from 180, €60 from 365; at source €63, €56, €49 and €42. 3 parallel connections per key and endpoint included (one connection can subscribe to every instrument); +5 more for €10 per day, up to 28, added from your account. Realtime access is paid by card or in USDC — credits apply to historical data only. Paid days start at the next 00:00 UTC and the rest of the purchase day is included free.

Which venues stream in real time?

Binance, Coinbase, Kalshi, Polymarket, OKX and Bybit — Low-latency Binance market data, Coinbase real-time market data, Kalshi real-time market data, Polymarket real-time market data, OKX real-time market data, Bybit real-time market data. Captured at each venue and delivered at our London, Frankfurt, Ashburn, Ohio or Tokyo endpoints over dedicated lines (Binance, OKX and Bybit from Tokyo at London, Frankfurt, Ashburn or Ohio; Coinbase from Ashburn at Ohio or Tokyo; Kalshi from Ohio at Tokyo; Polymarket from London at Tokyo), and at source where the venue is captured (Binance, OKX and Bybit at Tokyo; Coinbase at Ashburn; Kalshi at Ohio; Polymarket at London). Kalshi and Polymarket are sold as whole markets only. London, Frankfurt, Ashburn, Ohio and Tokyo are the self-serve locations today; more will follow, and enterprise subscriptions already cover further locations and venues.

Is the real-time feed an API?

Yes — a WebSocket API with a documented login and subscribe flow, JSON or SBE encoding and one API key per account; the port selects the market (Binance USDT-M (port 14004), Binance Spot (port 14003), Coinbase Spot (port 14006), Kalshi (port 14005), Polymarket (port 14007), OKX (port 14008) and Bybit (port 14009)). The connection guide walks through it with runnable examples, the machine-readable spec is the same document for coding agents, and the instrument directory ships the master data of every market you hold as JSON or CSV. The field-level protocol reference is the market-data specification; the HTTP side — search, coverage, quote, checkout and download of the historical files — is the crypto market data API.

What does "at source" mean?

At source means the normalized feed is handed over at the site where the venue is captured — no dedicated line, so there is no line latency to quote. Each venue is also sold at the endpoint where it is captured — Polymarket at London, Coinbase at Ashburn, Kalshi at Ohio, Binance at Tokyo, OKX at Tokyo, Bybit at Tokyo — the same feed, protocol and port as over a line. Day prices at source: €35 per instrument-day or €69 per market-day.

How is the latency of each endpoint measured?

Binance lines: ~69.3 ms Tokyo → London, ~68.2 ms Tokyo → Frankfurt, ~67.7 ms Tokyo → Ashburn and ~64.1 ms Tokyo → Ohio — one-way line latency from the site where the venue is captured to our endpoint — the venue's own latency and the on-ramp to your client come on top. OKX lines: ~69.3 ms Tokyo → London, ~68.2 ms Tokyo → Frankfurt, ~67.7 ms Tokyo → Ashburn and ~64.1 ms Tokyo → Ohio — one-way line latency from the site where the venue is captured to our endpoint — the venue's own latency and the on-ramp to your client come on top. Bybit lines: ~69.3 ms Tokyo → London, ~68.2 ms Tokyo → Frankfurt, ~67.7 ms Tokyo → Ashburn and ~64.1 ms Tokyo → Ohio — one-way line latency from the site where the venue is captured to our endpoint — the venue's own latency and the on-ramp to your client come on top. Coinbase lines: ~4.6 ms Ashburn → Ohio and ~67.7 ms Ashburn → Tokyo — one-way line latency from the site where the venue is captured to our endpoint — the venue's own latency and the on-ramp to your client come on top. Kalshi lines: ~64.1 ms Ohio → Tokyo — one-way line latency from the site where the venue is captured to our endpoint — the venue's own latency and the on-ramp to your client come on top. Polymarket lines: ~69.3 ms London → Tokyo — one-way line latency from the site where the venue is captured to our endpoint — the venue's own latency and the on-ramp to your client come on top. Each line is a dedicated route from the capture site to the endpoint; the venue's own delay and the hop from the endpoint to your system come on top. Enterprise subscriptions already cover further locations and venues — see the enterprise tiers.

Does the feed carry both trades and quotes?

Binance USDT-M, OKX and Bybit serve order book, top of book, trades, mark price, index price, funding rate and liquidations; Binance Spot serves order book, top of book and trades; Coinbase Spot, Kalshi and Polymarket serve order book and trades. A topic a market does not carry never emits there. The order book arrives as a snapshot on subscribe, then every changed level; trades arrive one by one with side, size and the venue's trade id. Where a venue offers more than one order-book feed, we take the one with the lowest latency, at the depth that feed carries. On Bybit that feed carries the top 50 levels per side, on OKX the top 400 levels per side.

Do historical and real-time data share the same schema?

Yes. The day files in the shop are recordings of this stream — same topics, same normalized schema, same two clocks — so a parser and a strategy written against the historical archive read the live feed unchanged. The schema is documented field by field in the market-data specification.

Is this the same feed as your enterprise and HFT lines?

Yes. The self-serve endpoints hang on the same dedicated lines our own high-frequency trading engine and enterprise feeds use, and they carry the same stream — every message, nothing sampled. The difference is commercial: self-serve access is bought by the UTC day with one API key and covers Binance, Coinbase, Kalshi, Polymarket, OKX and Bybit at London, Frankfurt, Ashburn, Ohio and Tokyo are the self-serve locations today; more will follow; enterprise subscriptions already cover further locations and venues, plus order entry and T+1 history — see the enterprise tiers.

Can a coding agent implement the WebSocket connection for me?

Yes — hand it the machine-readable spec: login, subscribe, message types and reconnect rules in one markdown document. Give the agent the key through the CRYPTOSTRUCT_REALTIME_API_KEY environment variable, never inside the prompt.