Skip to content

For agents

AI agents & MCP

Routeur speaks the Model Context Protocol, so an agent can read every market on Kalshi and Polymarket, the relations proven between their contracts, the mispricings those relations expose, and strategies measured against settled history — with the same key, limits and data as the REST API. Everything is read-only: no tool places an order or changes anything.

Connect

One HTTP endpoint, authenticated with your Routeur API key.

Endpoint
https://api.routeur.app/mcp
Transport
Streamable HTTP
Auth
Authorization: Bearer $ROUTEUR_API_KEY

Claude Code

claude mcp add --transport http routeur https://api.routeur.app/mcp --header "Authorization: Bearer $ROUTEUR_API_KEY"

Codex CLI

codex mcp add routeur --url https://api.routeur.app/mcp --header "Authorization: Bearer $ROUTEUR_API_KEY"

stdio-only clients

npx mcp-remote https://api.routeur.app/mcp --header "Authorization: Bearer ${ROUTEUR_API_KEY}"

Any client with a config file

{
  "mcpServers": {
    "routeur": {
      "type": "http",
      "url": "https://api.routeur.app/mcp",
      "headers": {
        "Authorization": "Bearer ${ROUTEUR_API_KEY}"
      }
    }
  }
}

Need a key? Write to hello@routeur.app. The same key works for MCP and the REST API, and one tool call counts as the API requests it makes.

Tools

Five tools answer whole questions; every documented REST endpoint is a tool as well, generated from the API description, so new endpoints appear automatically.

  • find_opportunities

    Mispricing leads, cross-venue price gaps and open markets fitting a backtested strategy, liquid by default.

  • compare_venues

    One question priced on Kalshi and Polymarket, outcome by outcome, with the gap in cents.

  • explain_relation

    Why two markets are linked: the proven relation, the evidence, and whether prices respect it.

  • market_snapshot

    One market in full: price, spread, recent trading, price history and what it is linked to.

  • search_markets

    Find markets in plain language, with filters for venue, category, price, volume and close date.

The full list, with every argument, is in the tool reference. The server also carries resources explaining how relations are proven, what fees and spreads mean and which categories and topics exist, and prompts for scanning a category for mispricings, briefing you on an event, and testing a price band against settled history.

What agents should know before quoting a number

  • Prices are asks per contract that pays $1, as exact decimal strings. The spread is what crossing costs, and a wide spread is a thin book.
  • A relation is proven from both contracts' structured terms and exact arithmetic. No relation coming back means none was proven, not that two markets are unrelated.
  • A gap between venues is only money when both books have size and fees leave something; only leads marked executable could be filled at a profit when the books were read.
  • Strategy and calibration figures are settled history, before fees, and are not a forecast.
  • Kalshi is read every 15 minutes, Polymarket every 30, and the relation graph is rebuilt hourly.

Also machine-readable

Routeur is an information service, not a broker, exchange or adviser. Prices come from Kalshi and Polymarket, which do not endorse Routeur, and may be delayed or incomplete. Nothing here is investment advice; see the risk disclosure.