Skip to content

Open to agents

Connect an AI assistant to GADUIN to read live markets, your positions and your balance. Any Model Context Protocol (MCP) client connects with a key you issue.

What is MCP?

Model Context Protocol is an open standard for connecting AI assistants to outside data and tools. GADUIN publishes an MCP endpoint that any MCP-compatible client — Claude Desktop, Claude.ai, your own agent — can connect to with an API key you issue. Every call is authenticated and limited to the account that issued the key.

Available tools

The v1 tools are read-only. Each one publishes its own input schema, so the client wires it up automatically and you never write the JSON by hand.

  • list_markets

    List open prediction markets on real-world transport outcomes (flight delays, train cancellations, ship-chokepoint throughput). Optional inputs: category (FLIGHT, TRAIN, SHIP), status (defaults to OPEN), limit (1–100). Returns market id, category, question, outcomes with current prices, total volume, and close time.

  • get_market

    Fetch a single market by id, including current prices and outcomes. Input: the market id.

  • get_my_positions

    List your open positions across every market. No inputs. Returns the market, the outcome, the shares you hold and what you paid for them.

  • get_balance

    Return your current balance. No inputs.

  • flight_status

    Look up a flight by number, such as BA117. Returns the leg in the air or next to depart, its departure and arrival times in UTC and local time, the last update, and links to the flight page and any open market on that journey.

  • flight_history

    Look up a flight's last 30 days by number. Returns on-time, late and cancelled counts, the sample size, the window and the rule used to count a flight as late.

Trading happens on the website

API and MCP access is read-only. A trade a program places on its own can go wrong in more ways than a read can, so trades and withdrawals happen only on the website, with a person in the loop. Every API key is read-only and limited to 1 request per second.

Connect a client

  1. Sign up and verify your account.
  2. Generate an API key from your account settings — every key is read-only.
  3. Drop the snippet below into your MCP-compatible client and swap in your key.
Endpoint
https://gaduin.com/mcp
Authorization
Bearer YOUR_API_KEY
Claude Desktop config
{
  "mcpServers": {
    "gaduin": {
      "url": "https://gaduin.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, swap in your API key, then restart Claude.

Endpoint reference

Prefer to wire things up directly? The Model Context Protocol endpoint and the read-only REST API are below; both take a token from your read-only API key. They serve the same markets and the same prices the site does.

MCP endpoint
https://gaduin.com/mcp
REST read API (base URL)
https://gaduin.com/api/v1
  • GET /markets

    List markets — every status unless you filter. Filter by category (FLIGHT, TRAIN, SHIP) and status, and page through results with limit and offset.

  • GET /markets/{id}

    Fetch a single market by id, including its settlement rule and evidence.

  • GET /markets/{id}/activity

    Recent trades for a market, newest first.

  • GET /markets/{id}/price-history

    Historical price snapshots for a market.

  • GET /markets/config

    Trading bounds — the minimum and maximum trade amount.

  • GET /healthz

    A health check.

Machine-readable discovery

Agents don't have to scrape this page. Every capability above is also described in a standards-based document served from the site root, so an MCP- or OpenAPI-aware client can discover the markets, the API, and how to authenticate on its own.

  • /.well-known/mcp/server-card.json

    MCP Server Card (SEP-1649) — the Model Context Protocol endpoint, its transport, and how to authenticate.

  • /.well-known/openapi.json

    OpenAPI 3.1 description of the read-only REST API, including how to authenticate.

  • /.well-known/api-catalog

    API Catalog (RFC 9727) — the linkset that ties every machine-readable surface together.

  • /.well-known/oauth-protected-resource

    OAuth 2.0 Protected Resource Metadata (RFC 9728) — which issuer to ask for access, and the scopes it can grant.

  • /.well-known/oauth-authorization-server

    OAuth 2.0 Authorization Server Metadata (RFC 8414) — the issuer, and how an API key is exchanged for short-lived access.

  • /.well-known/agent-skills/index.json

    Agent Skills index — the SKILL.md guides an agent can fetch to learn how to work with GADUIN, each pinned to an exact version.

  • /api/md

    Markdown rendering of any public page, via content negotiation (send Accept: text/markdown).

  • /auth.md

    A human- and agent-readable walk-through of authenticating and minting a read-only API key.