Data and limits

This page covers what data Routeur records and serves, its volumes and retention, what the API deliberately does not provide, and the request limits that apply everywhere. Read it before relying on any figure in a product or a study.

Coverage

Venue	What is read	Not included
Kalshi	Every listed market and event, rule text, series and event rulebooks, contract terms documents, top-of-book asks and bids, public trades, order books, settled history from Kalshi’s archive	Nothing venue-side is excluded
Polymarket (global)	Every listed market and event on the global exchange, rule text and resolution metadata, top-of-book asks and bids, public trades, order books, imported history from before recording began	Polymarket’s US exchange

Both venues are read as public data. No account, wallet or identity is recorded with a trade. Categories, with the number of events in the latest graph on 17 September 2026:

Category	Events
Sports	20,071
Politics	6,645
Crypto	4,009
Economics	1,716
Culture	994
Weather	530
Tech & Science	395
Other	117
World	10

GET /v1/categories returns the current counts.

Volumes

Observed on 17 September 2026 from GET /v1/status and GET /v1/books/health:

Figure	Value
Kalshi markets in the latest crawl	130,310
Polymarket markets in the latest crawl	174,810
Markets in the latest graph run	304,955
Structured propositions (markets with terms a proof can read)	131,409
Cross-venue games matched	148
Cross-venue relations: equivalent / contradicts / subset / superset / overlaps	1,301 / 1,265 / 7,218 / 7,099 / 11
Within-venue relations (Kalshi + Polymarket)	about 1.5 million, mostly `contradicts`
Markets recorded at full order-book depth	4,352 on Kalshi, 1,803 on Polymarket
Order-book messages per minute	about 253,000 from Kalshi, 88,000 from Polymarket

Retention

Series	Kept	Read through
Rule text versions, rulebook versions, rule changes	Forever, from the day a version was first seen	`GET /v1/markets/{venue}/{id}/rules`, `GET /v1/rulebooks/{venue}/{kind}/{id}`
Quote history (change-only top-of-book asks)	Served for the last 90 days, at most 5,000 points per request	`GET /v1/markets/{venue}/{id}/quotes?days=`
Trades	All recorded fills, newest first with a cursor	`GET /v1/markets/{venue}/{id}/trades`
Order-book level changes (raw events)	7 days	`GET /v1/markets/{venue}/{id}/book?at=` rebuilds a book from them. The parameter accepts up to 90 days back, but a moment older than the raw events returns `404 book_not_found`.
Order-book snapshots	30 days, then exported to an archive	Used by `book?at=` rebuilds
Top of book per second	30 days, then exported to an archive	`GET /v1/markets/{venue}/{id}/book/history`
Live stream replay	1 hour guaranteed (rows are kept for 2 hours)	`GET /v1/stream?cursor=` or `Last-Event-ID`
Flow signals	Detections are kept; the trade rollups behind them for 35 days	`GET /v1/flow`
Graph runs	Relations and leads are read from the latest finished run; the proof trail names the run that found a relation and the one that last confirmed it	`GET /v1/relations/...`
Settled history	Kalshi’s archive and imported Polymarket history, marked `archive` where it appears	`GET /v1/insights/calibration`, `/strategies`, quotes before recording began

What is not provided

No trading. There is no order placement, no positions, no balances and no venue credentials. Every endpoint is GET; the MCP server is read-only.
No accounts. No endpoint creates, lists or revokes keys, and nothing is stored about you beyond request counts.
No identities. Trades carry the venue’s trade id, price, quantity and time, never the account or wallet behind them.
No raw order-book export. Raw level changes are kept for 7 days and dropped; their redistribution rights are under review and until that clears they are not exported or served in bulk. Snapshots and top-of-book history are kept.
No proofs from prose. Markets without structured terms are listed, priced and searchable, but no relation is proven for them.
No quotes. Prices are observations recorded on a crawl. They can move before an order reaches the venue.
No predictions. A relation says how two contracts’ outcomes constrain each other, not how either will resolve. Calibration and strategies describe settled markets; past gaps can close.
No browser access to the stream. EventSource cannot send a key header; connect from a server.

Informational leads

A lead is offered as executable only when its live order books could fill at least one whole pair for less than it pays after fees and minimum sizes. One class of lead is never offered as executable however the books look: cross-venue relations between economic-release markets (for example CPI or a Fed decision) where the two venues settle a delayed or cancelled release differently. Such a lead carries depth.limited_by = "informational" and the issue:

informational: the venues settle a delayed or cancelled release differently; not offered as executable until a release guard exists

It is still listed with its prices and depth, and the relation behind it is still proven, so you can size it yourself; it is left out of executable=true lists and of lead.executable webhooks.

Fees

estimated_fee_usd on a lead and fees_usd in its depth are estimates from published schedules. Where the crawl has read a market’s own fee terms, they are used; otherwise the taker fee is 0.07 × p × (1 − p) per contract, Kalshi’s published coefficient. Venues change fees; check the venue before trading.

Request limits

Limit	Value
Request timeout	15 seconds, then `504 timeout`
MCP tool call timeout	25 seconds, including every REST request the tool makes
Free-text `q`	Up to 200 characters, no control characters
Stream lifetime	45 to 55 minutes, then a `reconnect` event
Markets named on one stream	50
Relations one graph run pushes to a stream	10,000; more sends `relations_truncated` instead
Leads one graph run pushes to a stream	1,000
Search results	300
Per-minute limit, daily quota, concurrent streams	By tier; see Rate limits

Not advice

Nothing in the API or these docs is investment advice. Check a venue’s own terms, book and fees before trading.

Get started

Concepts

Agents & MCP

Webhooks

Reference

Data and limits

Coverage

Volumes

Retention

What is not provided

Informational leads

Fees

Request limits

Not advice

Coverage

Volumes

Retention

What is not provided

Informational leads

Fees

Request limits

Not advice

Related