Polymarket cricket data: match pricing at 250ms

Cricket sits in the sports long tail alongside motorsport, MMA, and basketball — families Polymarket lists continuously but reports as long tail rather than a counted split.

The record is identical to the counted families: each cricket market PolyOrderbooks lists captures as a full L2 book four times per second, while the official API serves only the live ladder with no history.

Cricket match and series questions resolve to the shared record — full bid/ask ladders with sizes, a captured_at timestamp, and the winning outcome — and trade as binaries like everything else.

No cricket-specific count is quoted: the measured coverage stops at the 700k+ total, and this page does not fabricate a split. The honest indicative sizes live on the sports data page.

• Live ladder — official /book, free and keyless, current moment only (what the API serves).
• Historical depth — full L2 books at 250ms over REST, free Starter with 3 days, paid windows to 120 days.
• Discovery — /v1/series for cricket events; /v1/markets for questions and slugs.
• Coverage — measured counts per sport on the sports data page.

A T20 fixture is the fastest clock on the calendar: the powerplay opens the book, the death overs reprice the totals inside two deliveries, and the chase settles the winner at the last ball. The official API serves those moments live; the archive holds the death-over frame for replay long after the drinks break souvenir.

Cricket sits in the sports long tail alongside motorsport, MMA, and basketball: series listed continuously, counted as part of the 700k+ combined pool rather than a split of its own. Match and series questions trade within that pool, so the unit of study is the fixture clock — overs, not days.

Three reproducible measurements fit the archive: whether death-over totals widen then tighten as the target nears, whether a top-order collapse reprices the winner inside a single over, and whether powerplay aggression shows up as a systematic early premium on the batting side.

The pull is the usual chain — series and market endpoints for the fixture, then the archive window across the innings — and the result is the complete two-sided ladder second by second, from first delivery to last.

Over boundaries are the repricing seams: the executable side moves hardest in the powerplay and the final two overs of a chase.

As long tail, a single match is a case study; a tournament run in one window is the honest minimal sample.

Starter holds 3 days (a full T20 doubleheader night); Pro extends to 120 days.

Study one: measure death-overs repricing across a T20 doubleheader, counting frames from each boundary to the new executable price on the totals market.

Study two: replay a top-order collapse and compare the winner-market reprise with the season's baseline rate, calibrated against the venue's recorded sub-second dynamics.

Study three: test whether powerplay aggression shows a systematic early premium on the batting book across a tournament round.

One T20 night fits the free tier; a full tournament in Pro's 120 days is the honest sample for death-over conclusions.

First exercise: a T20 chase. Pull the innings-window from the archive and count the executable-price moves across the powerplay and the death overs. Boundaries reprice totals inside two deliveries, and the record preserves each one at 250ms.

Then pull a top-order collapse in the same match and compare the winner-market reprise with the totals-market reprise at the identical second; the lag between the two books is the innings' full lesson.

Resolve the match and keep it queryable; one doubleheader night in the Starter window is the smallest honest sample, and a tournament in Pro is what turns the pattern into a finding.

• Sports data
• Market data
• Order book data