Skip to main content
This page takes you from a key to your first useful responses: an event priced on both venues, the proven relation behind a cross-venue gap, a lead sized against order books, a market’s rules, then the live stream and MCP. Every response shown was recorded from the API on 17 September 2026; the markets in the examples settle after that date, so pick current ids from GET /v1/events when you follow along.

Get a key

Keys are issued by the Routeur team during the private preview. A key looks like rk_live_<12-character id>_<43-character secret> and is shown once. Put it in an environment variable and only use it server-side:
Send it as X-API-Key or as a bearer token; see Authentication.

Check the service

GET /v1/status names the latest finished graph run and the crawls it was built from.
The output above is trimmed; edge_counts lists every relation kind per venue and across venues.

An event with its outcomes

Events group a venue’s markets the way people browse them. cross_venue=true keeps only events listed on both venues.
What to read:

The relation behind a cross-venue gap

Take the venue and market_id from a price and ask what that market is proven to relate to. cross_venue=true keeps only markets on the other venue.
The two markets are equivalent: both pay Yes when the game’s total exceeds 54.5, stated as the exact rational 109/2. To see the proof step by step, ask for the trail:
The full response also carries both contract versions, the runs that found and last confirmed the relation, and first_seen_at. See Proof trail. The whole list of cross-venue pairs is GET /v1/cross-venue; see Cross-venue pairs.

A lead with depth

A lead is a two-leg purchase that a proven relation says pays at least $1 in every outcome. depth sizes it against the live order books.
Read depth.executable before anything else. Here the two No contracts cost 0.993 together and pay $1, a gross edge of 0.007, but fees of about 0.019 make the net negative, so executable is false and limited_by is price. Add executable=true to list only leads whose books could be filled at a profit. See Leads.

A market’s rules

rules_hash fingerprints this version of the terms; relations are proven against a specific version. versions lists every version recorded with a diff from the one before, and changes is the ledger of every change to the market’s terms, including changes to a rulebook above it. See Rules.

Stream what changes

The stream is Server-Sent Events over one keyed connection. Name the topics you want; min_usd drops small trades.
Every data event has an id. After a drop, reconnect with it in Last-Event-ID (or as cursor) and the events since are replayed, for up to an hour. Topics are quotes, trades, books, relations, leads and rules. See Live stream.

MCP in 60 seconds

The same endpoints are MCP tools at https://api.routeur.app/mcp, with the same key. In Claude Code:
Or call a tool by hand. compare_venues prices one question on both venues in a single call:
The tool result’s text is JSON:
A tool call counts against your key as the REST requests it makes. See Agents and MCP and the tool reference.