Ladder data

Polymarket Ladder Data

The ladder is the whole book — every price level and size on both sides, captured at 250ms — and it is the data this site is built on. This page covers the ladder surface, level behavior, and the honest research role of full-depth capture.

Figures measured as of 2026-09-24 on the published PolyOrderbooks archive.

Surface

What the ladder dataset contains

Each 250ms frame carries aligned bids and asks — price and size per level — sorted best-first on both sides, plus depth, spread, and the flags that describe the frame. It is the only view that preserves how the venue's bound actually stood.

The derived views (top-of-book, metrics, imbalance) all reduce to the ladder, which is why the archive ships it canonically and treats every other series as a view.

Measured

Measured level behavior

Levels near the bound are the venue's gravity: executable prices bunch on the 0.99/0.995 grid 98.6% of the time, the winner side rests a median 42,254 shares at 0.99 in the 5m corpus, and one-sided frames (16.9%) show the ladder with a side missing — recorded, not repaired.

The honest research use of level data is capacity and cost: how much could trade at each level, and what walking the ladder costs — the inputs to the fill model.

Honest

The honest framing

Ladder data is the ground truth and the hardest to summarize: a study that reduces it to mid-means is studying a projection, and the honest habit — kept everywhere on this site — is keeping the levels in the artifacts and the summaries labeled as views.

FAQ

What is ladder data?

The full bid/ask ladder — every price level with size on both sides — captured at 250ms per frame.

Why keep every level?

Because capacity, slippage, and fill cost all read from levels; summary views hide them.

How does the ladder behave at the bound?

Executable prices bunch on the 0.99/0.995 grid and the winner side rests a median ~42k shares at 0.99 in the 5m corpus.