Data freshness - Routeur

Routeur reads the venues on a schedule. Each response tells you what it was built from, so you never have to guess how current it is.

Data	Recorded	How to tell
Kalshi markets and asks	Every 15 minutes	`observed_at` on each price
Polymarket markets and asks	Every 30 minutes	`observed_at` on each price
Trades on both venues	Every minute	`executed_at` on each trade
The graph: relations, events, leads	Hourly, 10 minutes past the hour	`graph_run` on the response; `GET /v1/status` for its timing
Unusual flow, moves, one-sided money	Every 5 minutes	`last_detected_at`, `detected_at`
Settled markets, calibration, strategies	Every 30 minutes	`refreshed_at` on calibration

Checking the service

GET /v1/status returns the latest finished graph run, with when it started and finished and the crawls it read, plus the latest crawl of each venue and the latest complete one.

curl https://api.routeur.app/v1/status -H "X-API-Key: $ROUTEUR_API_KEY"

A graph run only reads complete crawls. If a venue’s latest crawl did not finish, the graph keeps using the previous complete one, and its markets stay listed rather than disappearing.

Prices are observations

Prices are the venues’ top-of-book asks as recorded, not live quotes. Between recordings the book can move, and a venue can have more size at worse prices behind the top level. For an order, read the venue’s book directly; for sizing a lead, use its depth.