Skip to content

Open to agents

GADUIN runs a Model Context Protocol server so LLM agents and trading bots can read live markets, positions and balances on your behalf.

What is MCP?

Model Context Protocol is an open standard for connecting LLM clients to external data and tools. GADUIN exposes an MCP endpoint that any MCP-compatible client — Claude Desktop, Claude.ai, custom agents — can connect to with a user-issued API key. Each call is authenticated and scoped to the user who issued the key.

Available tools

The v1 tool catalogue is read-only. Each tool publishes its own input schema; the LLM client wires it automatically — you don't have to hand-roll JSON.

  • 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: id (market UUID).

  • get_my_positions

    List the authenticated user's open positions across all markets. No inputs. Returns market_id, outcome_idx, shares held, and total cost basis.

  • get_balance

    Return the authenticated user's current dollar balance, as a string. No inputs.

Trading is REST-only for now

Placing trades, deposits and withdrawals are deliberately not exposed through MCP yet — an MCP-driven trade has higher blast radius than a read, and we want the human in the loop until the UX is proven. Programmatic trading is available through the REST API with a scoped API key.

Connect a client

  1. 1.Sign up and verify your account.
  2. 2.Generate an API key from your account settings — read scope is enough for MCP.
  3. 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 anonymous, read-only REST API are below — the same markets, order books, and prices the site and the MCP server serve.

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

    List open markets. Filter by category (FLIGHT, TRAIN, SHIP) and status, and page through results with limit and cursor.

  • GET /markets/{id}

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

  • GET /markets/{id}/book

    Order-book snapshot for a market.

  • GET /markets/{id}/trades

    Recent trades for a market.

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

    Historical price snapshots for a market.

  • GET /markets/positions

    Live aggregate positions across every market.

  • GET /markets/config

    Trading bounds — the minimum and maximum trade amount.

  • GET /healthz

    Liveness probe.

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 anonymous, read-only REST API.

  • /.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 authorization server issues API tokens, and the scopes they carry.

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

    OAuth 2.0 Authorization Server Metadata (RFC 8414) — the issuer, token endpoint, and the API-key-to-token grant.

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

    Agent Skills index — the SKILL.md guides an agent can fetch to learn how to work with the platform, each pinned by digest.

  • /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 scoped API key.