# CryptoStruct Data Shop — historical crypto & prediction-market data > Canonical HTML: https://cryptostruct.com/shop (needs JavaScript) · This document: https://cryptostruct.com/shop.md · Day bundles: https://cryptostruct.com/shop/bundles.md · Realtime: https://cryptostruct.com/shop/realtime.md · Agents: https://cryptostruct.com/llms.txt ## What is sold - **Tick-data day files** — one file = one instrument × one UTC day, every message the venue published for it (L2 order-book snapshots + updates, top of book, trades, funding/mark/index, liquidations, option greeks where the venue sends them). 800K+ instruments across 35+ venues, archive since 2021-02-08, newest day = yesterday (UTC). **€1 per instrument-day**, tax-inclusive, no account, subscription or minimum. - **Day bundles** (`kind: series_day`) — every contract file of one prediction-market series (Kalshi, Polymarket), one Deribit option chain or one dated-futures curve on one UTC day; priced per series, mostly €1 per bundle day. List: https://cryptostruct.com/shop/bundles.md. - **Realtime access** — live Binance WebSocket data by the UTC day, sold on the website only: https://cryptostruct.com/shop/realtime.md. File format: `.txt.zst` (zstd-compressed JSON lines; line 1 = instrument master data; decimal strings for prices/quantities; integer nanosecond UTC timestamps). Reference + parser: https://cryptostruct.com/skills/cryptostruct-market-data/SKILL.md. Free full-day samples in the same format: https://cryptostruct.com/download.md. ## How to find the instrument `GET https://cryptostruct.com/api/search?q=&venue=&class=` — e.g. `q=BTCUSDT&venue=binance&class=perp` → Binance USDT-M perpetual, instrument_id 67824. Venue and class words inside `q` are understood ("binance btcusdt perp"). Coverage: `GET https://cryptostruct.com/api/instrument/{id}/coverage`, days: `GET https://cryptostruct.com/api/instrument/{id}/days`. Instrument ids are stable and identical across MCP, shop and analytics pages. ## How to buy 1. **Hand the user a link** — Buy link (no API call needed): https://cryptostruct.com/shop?i=&d=.. opens the shop with those UTC days of the instrument in the cart; d also takes a comma list or a mix (d=2026-09-01..2026-09-07,2026-09-15). Bundles: https://cryptostruct.com/shop/bundles?bundle=&d=…. Only archived days are added (gaps and days still being merged are skipped), at most 366 days of span and 1000 lines per cart; the user pays on the site. Example: https://cryptostruct.com/shop?i=67824&d=2026-09-29..2026-10-05 = seven days of Binance BTCUSDT perpetual ticks. 2. **MCP** (https://cryptostruct.com/mcp, docs https://cryptostruct.com/docs/mcp.md): search_instruments → get_coverage → get_price_quote → create_checkout → get_checkout_status → get_order_files. Signed-in agents can pay with the account's credits — only with the user's consent. 3. **Plain HTTP** (https://cryptostruct.com/docs/api.md, OpenAPI https://cryptostruct.com/openapi.json): `POST https://cryptostruct.com/api/quote` → guest `POST https://cryptostruct.com/v1/checkout/session` (Stripe page for the user) → poll → download with the `download_token`. Card payment always happens on a Stripe page the USER opens; an agent never collects card details. Guest download links stay valid for 30 days; orders made with a signed-in account never expire. Credits apply to historical data — single tick-day files and Day Bundles. Realtime access is paid by card. ## Delivery Per file: `GET https://cryptostruct.com/api/download/order/{order_id}/{instrument_id}/{date}?t=` (resumable; `&status=1` readiness, `&restore=1` for days older than ~1 month in deep archive, `&format=trades.csv.gz|bbo.csv.gz|liquidations.csv.gz|trades.parquet|liquidations.parquet` for flat exports). Bundles: one ZIP per day (`&kind=series_day&zip=1`) or one resumable tar per date range. Full contract: https://cryptostruct.com/llms.txt. Terms: https://cryptostruct.com/terms.md · Data license: https://cryptostruct.com/license · Pricing overview (credit packs, Premium): https://cryptostruct.com/pricing