> ## Documentation Index > Fetch the complete documentation index at: https://docs.routeur.app/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Prices are US dollars per contract that pays $1: 0.46 means 46 cents. Spread is the Yes ask plus the No ask minus $1. Liquidity grades are deep, tradeable and thin; lists hide thin markets unless include_thin=true. Relations are proven from contract terms, never inferred from wording; a lead marked informational is never executable. Every figure carries a graph_run; read /agents/reading-order first, then /concepts/relations and /concepts/liquidity. # Did a relation hold when the markets settled > Whether a proven relation held once both markets settled, and how a reviewer judged it, stated from the left market's side. Unlike the proof trail this works after the markets have left the listing, since settled markets are no longer in the latest graph: the newest stored proof between the two markets is used. `verification` is present once both markets have settled: `consistent` when the relation held, `violated` when it did not, `unverifiable` when a side settled scalar or void or the relation makes no claim (overlaps). `label` is present once a reviewer has judged the relation. `bucket` carries the figures for the relation's type and proof family, as on `/v1/accuracy`, so one verdict can be weighed against its family's record. ## OpenAPI ````yaml /openapi.yaml get /v1/relations/{left_venue}/{left_id}/{right_venue}/{right_id}/verification openapi: 3.1.0 info: title: Routeur Graph API version: '2026-09-15' summary: >- Proven relations between Kalshi and Polymarket contracts, with the history and signals built on them. description: > Routeur reads every open market on Kalshi and global Polymarket, and proves which ones imply, exclude or equal each other from each venue's structured contract terms and exact arithmetic. No relation is inferred from prose, and ambiguous or conflicting evidence is withheld. ## Authentication Send your key in the `X-API-Key` header, or as `Authorization: Bearer `. Keys look like `rk_live_<12-character id>_<43-character secret>` and are shown once when issued. Keep them server-side. One endpoint needs no key: `/v1/accuracy`, the public record of how often proven relations held when their markets settled. ## Rate limits Every key has a per-minute limit and a per-day quota set by its tier: | Tier | Requests per minute | Requests per day | |---|---|---| | free | 30 | 2,000 | | trader | 120 | 50,000 | | pro | 600 | 500,000 | | institutional | 3,000 | 10,000,000 | Responses carry `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset` (Unix seconds) for the minute window, and `X-Daily-Quota-Limit` and `X-Daily-Quota-Remaining` for the day (UTC). A request over either limit returns `429` with `Retry-After` in seconds. ## Conventions - Money and prices are decimal strings in USD (for example `"0.4100"`), never floats. Prices are per contract that pays $1. - Times are RFC 3339 in UTC. - Successful responses wrap results in `data`. Graph-derived responses also name the `graph_run` they were read from; runs finish hourly. - Paginated lists return `next_cursor` when more results exist. Pass it back as `cursor` unchanged; cursors are opaque. - Unknown or repeated query parameters are rejected with `400`, so typos never silently widen a query. ## Liquidity Every object that names a market carries its 24-hour volume, its spread and a `liquidity` grade, because a price nobody can trade at is not a price: | Grade | 24-hour volume or open interest | Round-trip spread | |---|---|---| | `deep` | $25,000 traded, or $250,000 open interest | 2¢ or less | | `tradeable` | $1,000 traded, or $25,000 open interest | 5¢ or less | | `thin` | anything less, or no quoted round trip | | Lists that suggest something to act on — price gaps, leads, movers, flows, large fills, closing soon, strategy matches — leave thin markets out by default, and rank what is left by the money behind it. Three parameters change that wherever it applies: `min_volume_usd`, `max_spread_usd` and `include_thin=true`, which drops both floors. Search and event listings show thin markets but rank them below what can be traded. ## Errors Errors return a JSON body `{"error": {"code": "...", "message": "..."}}`. Branch on `code`; messages may change. | Status | Code | Meaning | |---|---|---| | 400 | `invalid_parameter` | A query parameter is unknown, repeated or out of range. | | 400 | `invalid_market` | The venue is not `kalshi` or `polymarket`, or the market id is malformed. | | 400 | `invalid_rulebook` | The venue, rulebook kind or id is malformed. | | 400 | `invalid_event` | The venue is not `kalshi` or `polymarket`, or the event id is malformed. | | 400 | `invalid_topic` | The topic name is malformed; use lowercase words joined by dashes. | | 401 | `api_key_required` | No key was sent. | | 401 | `invalid_api_key` | The key is malformed or unknown. | | 401 | `api_key_revoked` | The key was revoked. | | 401 | `invalid_token` | The bearer credential is not an API key and is not a valid service identity token. | | 403 | `caller_not_allowed` | The service identity token is valid but its identity may not call the API. | | 404 | `market_not_found` | The market is not in the latest graph. | | 404 | `event_not_found` | The event is not in the latest graph. | | 404 | `topic_not_found` | No listed markets are labeled with that topic. | | 404 | `strategy_not_found` | No strategy with that id is supported by settled history right now. | | 404 | `relation_not_found` | Both markets are listed, but no current proof relates them. | | 404 | `rulebook_not_found` | No such rulebook has been recorded. | | 404 | `book_not_found` | No order book is recorded for the market at that time. | | 404 | `not_found` | No such endpoint. | | 429 | `rate_limited` | The per-minute limit was exceeded. | | 429 | `daily_quota_exceeded` | The daily quota is used up. | | 429 | `too_many_streams` | The key already holds its concurrent live streams. | | 503 | `graph_unavailable` | No graph run has finished yet. | | 503 | `database_unavailable` | The database is not reachable; the readiness check answers this while it is down. | | 503 | `stream_unavailable` | No live stream capacity is free; retry shortly. | | 504 | `timeout` | The request took longer than 15 seconds. | | 500 | `internal` | Something failed on our side. | ## Webhooks Mispricing alerts are delivered as signed `POST` requests; see the `webhooks` section. Each request carries `Routeur-Signature: t=,v1=`, where `v1` is HMAC-SHA256 of `.` keyed by your subscription's signing secret. Reject requests whose signature does not match or whose `t` is more than five minutes old, and respond `2xx` within 10 seconds. `Routeur-Delivery` identifies the delivery and stays the same across retries, so use it to ignore duplicates. Any response other than `2xx` or `410`, or no response, is retried with exponential backoff from 30 seconds for up to 8 attempts; responding `410 Gone` disables the subscription. Endpoints must be HTTPS on a public address, and redirects are not followed. contact: name: Routeur url: https://routeur.app servers: - url: https://api.routeur.app security: - apiKey: [] - bearer: [] tags: - name: Events description: Real-world events across both venues, the way people browse them. - name: Graph description: Markets and the relations proven between them. - name: History description: Recorded quotes and trades. - name: Rules description: | Contract terms and their history. Every version of every market's rule text is kept from the day it was first seen, along with the rulebooks above it (Kalshi series and event terms, Polymarket resolution metadata) and the venue's contract terms documents, with diffs between versions. - name: Books description: >- Order books recorded live from each venue's feed, their history, and the health of the feeds. - name: Signals description: Mispricing leads and unusual trading derived from the graph and history. - name: Live description: Quotes, trades, relations and leads pushed as they happen. - name: Service description: Service status and this document. paths: /v1/relations/{left_venue}/{left_id}/{right_venue}/{right_id}/verification: parameters: - name: left_venue in: path required: true description: The left market's venue. schema: $ref: '#/components/schemas/Venue' example: kalshi - name: left_id in: path required: true description: The left market's id. schema: $ref: '#/components/schemas/MarketID' example: KXNFLTOTAL-26SEP14DENKC-42 - name: right_venue in: path required: true description: The right market's venue. schema: $ref: '#/components/schemas/Venue' example: polymarket - name: right_id in: path required: true description: The right market's id. schema: $ref: '#/components/schemas/MarketID' example: nfl-den-kc-2026-09-15-total-41pt5 get: tags: - Graph summary: Did a relation hold when the markets settled description: | Whether a proven relation held once both markets settled, and how a reviewer judged it, stated from the left market's side. Unlike the proof trail this works after the markets have left the listing, since settled markets are no longer in the latest graph: the newest stored proof between the two markets is used. `verification` is present once both markets have settled: `consistent` when the relation held, `violated` when it did not, `unverifiable` when a side settled scalar or void or the relation makes no claim (overlaps). `label` is present once a reviewer has judged the relation. `bucket` carries the figures for the relation's type and proof family, as on `/v1/accuracy`, so one verdict can be weighed against its family's record. operationId: getRelationVerification responses: '200': description: The verdict and label. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' X-Daily-Quota-Limit: $ref: '#/components/headers/X-Daily-Quota-Limit' X-Daily-Quota-Remaining: $ref: '#/components/headers/X-Daily-Quota-Remaining' content: application/json: schema: type: object additionalProperties: false required: - data properties: data: $ref: '#/components/schemas/RelationVerification' example: data: relation: equivalent graph_relation: equivalent family: sports cross_venue: true first_seen_run: 790 verification: verdict: consistent left_result: 'yes' right_result: 'yes' settled_at: '2026-09-15T03:10:00Z' verified_at: '2026-09-15T03:37:12Z' label: label: correct reason: Same game, same total, both settle on the final score. labeled_at: '2026-09-14T16:02:11Z' bucket: relation: equivalent family: sports cross_venue: true checked: 412 violated: 0 unverifiable: 9 violation_rate: '0.0000' violation_rate_low: '0.0000' violation_rate_high: '0.0093' first_settled_at: '2026-08-02T01:15:00Z' last_settled_at: '2026-09-15T03:10:00Z' labels: correct: 38 wrong: 0 unsure: 2 precision: '1.0000' precision_low: '0.9075' precision_high: '1.0000' wrong_relations_still_live: 0 released: true '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '404': description: No stored proof relates the two markets (`relation_not_found`). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: relation_not_found message: No stored proof relates these markets. '429': $ref: '#/components/responses/TooManyRequests' default: $ref: '#/components/responses/Error' components: schemas: Venue: type: string enum: - kalshi - polymarket MarketID: type: string pattern: ^[A-Za-z0-9][A-Za-z0-9_.-]{0,199}$ RelationVerification: type: object additionalProperties: false required: - relation - graph_relation - family - cross_venue - first_seen_run properties: relation: $ref: '#/components/schemas/RelationFromMarket' graph_relation: $ref: '#/components/schemas/GraphRelation' family: $ref: '#/components/schemas/ProofFamily' cross_venue: type: boolean first_seen_run: $ref: '#/components/schemas/GraphRunID' verification: $ref: '#/components/schemas/OutcomeVerdict' label: $ref: '#/components/schemas/RelationLabel' bucket: $ref: '#/components/schemas/AccuracyBucket' Error: type: object additionalProperties: false required: - error properties: error: type: object additionalProperties: false required: - code - message properties: code: type: string description: A stable machine-readable code. message: type: string description: A human-readable explanation. RelationFromMarket: type: string description: | A relation from the requested market's side. `implies`: if this market resolves Yes, the other does. `implied_by`: the reverse. `contradicts`: both cannot resolve Yes. `overlaps`: the outcome sets intersect without containment. enum: - equivalent - implies - implied_by - contradicts - overlaps GraphRelation: type: string description: A relation stated from the left market's side. enum: - equivalent - subset - superset - contradicts - overlaps ProofFamily: type: string description: | The kind of proof behind a relation: `ladder` (exact strike bounds on one variable within a venue's event), `sports` (a game line paired across venues), `econ` (an economic or crypto variable paired across venues), `exclusive` (a source-asserted mutually exclusive event) or `other`. enum: - ladder - sports - econ - exclusive - other GraphRunID: type: integer description: The graph run the response was read from. minimum: 1 OutcomeVerdict: type: object additionalProperties: false required: - verdict - left_result - right_result - settled_at - verified_at properties: verdict: type: string enum: - consistent - violated - unverifiable left_result: type: string enum: - 'yes' - 'no' - scalar - void right_result: type: string enum: - 'yes' - 'no' - scalar - void settled_at: $ref: '#/components/schemas/Timestamp' description: The later of the two settlements. verified_at: $ref: '#/components/schemas/Timestamp' RelationLabel: type: object additionalProperties: false required: - label - labeled_at properties: label: type: string enum: - correct - wrong - unsure reason: type: string labeled_at: $ref: '#/components/schemas/Timestamp' AccuracyBucket: type: object additionalProperties: false required: - relation - family - cross_venue - checked - violated - unverifiable - violation_rate - violation_rate_low - violation_rate_high - labels - wrong_relations_still_live - released properties: relation: $ref: '#/components/schemas/AccuracyRelation' family: $ref: '#/components/schemas/ProofFamily' cross_venue: type: boolean checked: type: integer description: >- Relations whose markets both settled Yes or No: consistent plus violated. violated: type: integer unverifiable: type: integer description: >- Pairs where a side settled scalar or void, or the relation makes no claim. violation_rate: $ref: '#/components/schemas/Decimal' violation_rate_low: $ref: '#/components/schemas/Decimal' violation_rate_high: $ref: '#/components/schemas/Decimal' first_settled_at: $ref: '#/components/schemas/Timestamp' last_settled_at: $ref: '#/components/schemas/Timestamp' labels: $ref: '#/components/schemas/AccuracyLabels' wrong_relations_still_live: type: integer released: type: boolean description: Whether this family and venue scope have passed the release guard. Timestamp: type: string format: date-time AccuracyRelation: type: string description: >- A relation type as accuracy reports it; subset and superset edges are one type, implies. enum: - equivalent - implies - contradicts - overlaps Decimal: type: string description: An exact decimal number. pattern: ^-?[0-9]+(\.[0-9]+)?$ example: '0.4100' AccuracyLabels: type: object additionalProperties: false required: - correct - wrong - unsure properties: correct: type: integer wrong: type: integer unsure: type: integer precision: $ref: '#/components/schemas/Decimal' description: correct / (correct + wrong); absent until one is labelled. precision_low: $ref: '#/components/schemas/Decimal' precision_high: $ref: '#/components/schemas/Decimal' headers: X-RateLimit-Limit: description: Requests allowed per minute for this key. schema: type: integer X-RateLimit-Remaining: description: Requests left in the current minute. schema: type: integer X-RateLimit-Reset: description: Unix time when the minute window resets. schema: type: integer X-Daily-Quota-Limit: description: Requests allowed per UTC day. schema: type: integer X-Daily-Quota-Remaining: description: Requests left today. schema: type: integer responses: BadRequest: description: Invalid parameter or market. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: invalid_parameter message: 'Invalid or unsupported query parameter: limit.' Unauthorized: description: Missing, invalid or revoked API key. headers: WWW-Authenticate: schema: type: string content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: api_key_required message: Send an API key in the X-API-Key header or as a Bearer token. TooManyRequests: description: Rate limit or daily quota exceeded. headers: Retry-After: description: Seconds until the limit resets. schema: type: integer content: application/json: schema: $ref: '#/components/schemas/Error' Error: description: Any other error. content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: apiKey: type: apiKey in: header name: X-API-Key bearer: type: http scheme: bearer description: The same API key sent as a Bearer token. ````