New realtime endpoint: Ohio (AWS us-east-2, next to Kalshi) — Binance from Tokyo at ~64.1 ms one-way line latencyNew endpoint: Ohio · ~64.1 ms one-way line

Configure
Low-Latency Trading Solutions
CART
Polymarket · Climate · daily

Polymarket Daily High Temperature — Jakarta D

Every Polymarket “Daily High Temperature — Jakarta” contract of the day — every trade print and the complete Level-2 book, captured co-located with nanosecond venue and receive timestamps. 49 trading days as day bundles, €1 per day, bought as a guest with instant download.

Trading days
49
Coverage
April 2026 – May 2026
Archive size
5.00 GB
Price per day
€1
Activity & identifier

Daily High Temperature — Jakarta on Polymarket — activity

Per-day trade and turnover statistics exist from July 2026 onward — a limit of the statistics, not of the capture: older days are archived in full (every contract, every message) without a statistics row.

Slug prefix
highest-temperature-in-jakarta-
Files on latest day
11
Typical files / day
36
What's in a bundle

One purchase, the whole series for a day

A series-day bundle contains every Daily High Temperature — Jakarta contract that was listed on Polymarket on that UTC day — traded or not — 11 contract files on the latest covered day. Each file carries the full raw feed: every trade print with price, size and side, plus Level-2 order-book updates, in the same zstd-compressed schema as our crypto venues. Event contracts quote 0..1; turnover is USD-normalized.

Coverage runs April 2026 – May 2026 — 49 trading days, 5.00 GB compressed in total. A day typically holds 36 contract files (up to 66 on the busiest day, 204 MB). Pick individual days in the shop calendar for €1 each; delivery is an instant per-file download or one archive for the whole day.

Daily statistics

Daily High Temperature — Jakarta — last 30 days in the archive

Files, size, contracts traded, trades, USD turnover, buy share, quoted spread, top-of-book depth and order-book updates per UTC day, from the recorded tick data.

UTC dayFilesSizeNotes
2026-05-21111.24 MBBuy day →
2026-05-202221.1 MBBuy day →
2026-05-19223.49 MBBuy day →
2026-05-183313.8 MBBuy day →
2026-05-1737173 MBBuy day →
2026-05-1633123 MBBuy day →
2026-05-1533112 MBBuy day →
2026-05-1433109 MBBuy day →
2026-05-1333188 MBBuy day →
2026-05-1227196 MBBuy day →
2026-05-113195.4 MBBuy day →
2026-05-1033149 MBBuy day →
2026-05-0933119 MBBuy day →
2026-05-0833109 MBBuy day →
2026-05-073373.4 MBBuy day →
2026-05-0633125 MBBuy day →
2026-05-0533150 MBBuy day →
2026-05-0433122 MBBuy day →
2026-05-0339133 MBBuy day →
2026-05-0233141 MBBuy day →
2026-05-0133139 MBBuy day →
2026-04-3032135 MBBuy day →
2026-04-293396.5 MBBuy day →
2026-04-283373.8 MBBuy day →
2026-04-2733134 MBBuy day →
2026-04-2633127 MBBuy day →
2026-04-253380.7 MBBuy day →
2026-04-2433148 MBBuy day →
2026-04-2333204 MBBuy day →
2026-04-2233152 MBBuy day →

Trades and turnover per day appear here once our daily statistics have captured this series — normally the morning UTC after a day closes.

Why CryptoStruct

Why buy Polymarket Daily High Temperature — Jakarta data here

Four things every page on this site is built on — and the reason the numbers above exist at all.

We record everything

The complete public feed of each venue as it was published: every Level-2 snapshot and update at the venue's full book depth, every trade with its aggressor side, every quote, funding, mark-price and liquidation event — for every instrument the venue lists, every UTC day since we added the venue. Nothing sampled, no top-N cut, no on-demand capture.

Institutional grade

Captured co-located at the venue with the exchange timestamp and our receive timestamp in integer nanoseconds, an event-id chain that makes any gap visible, and one normalized schema across 35+ venues — the same capture our own high-frequency trading engine and enterprise feeds run on.

€1 per instrument-day

Any instrument-day is €1, series-day bundles start at €1 — no subscription, no minimum order, no tiers to unlock. Credit packs lower the effective price and never expire, and every venue has free full-day samples to test against first.

Self-service for everyone

Pick the days in the Data Shop, pay by card as a guest and download immediately — no sales call, no enterprise contract, no KYC. Coding agents buy the same files through the MCP server, and the free Agent Skill teaches them the format.

Agents: /llms.txt · MCP server /mcp · every page as markdown via Accept: text/markdown

FAQ

Polymarket Daily High Temperature — Jakarta data — FAQ

What Polymarket Daily High Temperature — Jakarta data can I download?

Tick-by-tick trades and Level-2 order-book depth for every contract of the Daily High Temperature — Jakarta series on Polymarket (11 contract files on the latest day). One bundle = one UTC day of the whole series.

How far back does the Daily High Temperature — Jakarta data go?

Coverage runs April 2026 – May 2026 — 49 trading days in total.

What format are the Polymarket files in?

One zstd-compressed text file per contract per UTC day, in the same normalized schema as our crypto venues — see the market-data specification; free samples on the downloads page.

Can I get Polymarket Daily High Temperature — Jakarta data as CSV or Parquet?

Yes — trades export as gzipped CSV or Parquet at no extra cost, with integer microsecond UTC timestamps that load straight into pandas, polars or DuckDB. Polymarket records full order-book depth without a separate BBO stream, so book data ships in the native tick file — the free reader script converts it locally. See the formats overview.

How much does Polymarket Daily High Temperature — Jakarta historical data cost?

€1 per series-day bundle — every contract of the series for that day — no subscription, no minimum order; buy as a guest in the Data Shop and download immediately. Credit packs lower the effective price and never expire.

Do I need an account or a sales call?

No. Pick the Daily High Temperature — Jakarta series-days in the Data Shop, pay by card as a guest and download immediately — no subscription, no minimum order, no KYC, no enterprise contract, no sales call. Coding agents buy the same bundles through the MCP server.

How is the Polymarket Daily High Temperature — Jakarta data captured?

Co-located at the venue, message by message: every Level-2 update and every trade print carries the exchange timestamp and our receive timestamp in integer nanoseconds, an event-id chain makes any gap visible, and one normalized schema across 35+ venues means a parser written for Binance reads these files unchanged. It is the same capture our own high-frequency trading engine runs on — nothing sampled, no top-N cut.

Topics

Topic hubs featuring this series