# Realtime access — live Binance, Coinbase, Kalshi, Polymarket and OKX market data by the UTC day

> Canonical HTML: https://cryptostruct.com/shop/realtime · This document: https://cryptostruct.com/shop/realtime.md · Product page: https://cryptostruct.com/realtime · Connection spec for coding agents: https://cryptostruct.com/docs/realtime.md

Live WebSocket market data for Binance USDT-M, Binance Spot, Coinbase Spot, Kalshi, Polymarket and OKX, captured at each venue and delivered at our London, Frankfurt, Ashburn, Ohio or Tokyo endpoints over dedicated lines (Binance and OKX 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) (London, Frankfurt, Ashburn, Ohio and Tokyo are the self-serve locations today; more will follow). Sold per UTC calendar day — €39.20 per instrument-day or €79.20 per market-day (public-beta price, 20 % off the list price of €49 / €99 for every day bought during the beta) (Kalshi and Polymarket are sold as whole markets only); paid days start at the next 00:00 UTC and the rest of the purchase day is included free; longer runs cost less per day: −10 % from 14 days, −25 % from 30, −50 % off the list price from 365 (€49.50 per market-day on a 365-day run). No subscription, nothing renews.

## Endpoints

| Location | Market | Endpoint | Latency |
| --- | --- | --- | --- |
| London (`lon1`) | Binance USDT-M | `ws://lon1.cryptostruct.com:14004` | 69.8 ms |
| London (`lon1`) | Binance Spot | `ws://lon1.cryptostruct.com:14003` | 69.8 ms |
| London (`lon1`) | OKX | `ws://lon1.cryptostruct.com:14008` | 69.8 ms |
| Frankfurt (`fra1`) | Binance USDT-M | `ws://fra1.cryptostruct.com:14004` | 68.2 ms |
| Frankfurt (`fra1`) | Binance Spot | `ws://fra1.cryptostruct.com:14003` | 68.2 ms |
| Frankfurt (`fra1`) | OKX | `ws://fra1.cryptostruct.com:14008` | 68.2 ms |
| Ashburn (`ash1`) | Binance USDT-M | `ws://ash1.cryptostruct.com:14004` | 67.7 ms |
| Ashburn (`ash1`) | Binance Spot | `ws://ash1.cryptostruct.com:14003` | 67.7 ms |
| Ashburn (`ash1`) | OKX | `ws://ash1.cryptostruct.com:14008` | 67.7 ms |
| Ohio (`ohio1`) | Binance USDT-M | `ws://ohio1.cryptostruct.com:14004` | 64.1 ms |
| Ohio (`ohio1`) | Binance Spot | `ws://ohio1.cryptostruct.com:14003` | 64.1 ms |
| Ohio (`ohio1`) | Coinbase Spot | `ws://ohio1.cryptostruct.com:14006` | 4.6 ms |
| Ohio (`ohio1`) | OKX | `ws://ohio1.cryptostruct.com:14008` | 64.1 ms |
| Tokyo (`tyo1`) | Coinbase Spot | `ws://tyo1.cryptostruct.com:14006` | 67.7 ms |
| Tokyo (`tyo1`) | Kalshi | `ws://tyo1.cryptostruct.com:14005` | 64.1 ms |
| Tokyo (`tyo1`) | Polymarket | `ws://tyo1.cryptostruct.com:14007` | 69.8 ms |

Latency basis: 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.

Entitlement is per (location, market, UTC day): a London day does not stream from Frankfurt. One API key per account (`?apiKey=` on the WebSocket URL), JSON or SBE encoding. Take all your instruments on one connection. Racing several connections to the same host against each other (feed arbitrage) gains nothing: they are served by the same host from the same feed, so no copy arrives earlier, and the duplicate traffic tends to slow your connection down rather than speed it up. That optimization is already done for you: we run feed arbitrage internally, before the data reaches your endpoint, so every connection delivers the fastest copy we have. Use further connections for independent processes only. 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.

## How to buy

1. Open https://cryptostruct.com/shop/realtime — pick endpoint → market → scope (whole market or single instruments) → number of days; the receipt shows list price, beta and duration pricing, total.
2. Pay by card (Stripe) or, when signed in, with account credits where applicable; the API key and the endpoint URLs appear at https://cryptostruct.com/account/realtime right after payment.
3. Connect: https://cryptostruct.com/docs/realtime (HTML) or https://cryptostruct.com/docs/realtime.md (one markdown spec: login, subscribe, every message type, reconnect rules, a ready prompt for Claude Code / Cursor). The key is read from the environment — never paste it into prompts.

Realtime days are NOT purchasable through the MCP server or the HTTP checkout API — those sell the historical archive. Agents: hand the user the shop link above.

Terms: https://cryptostruct.com/terms.md · Pricing overview: https://cryptostruct.com/pricing