面向代理开放

什么是 MCP？

Model Context Protocol 是一个连接 LLM 客户端与外部数据和工具的开放标准。GADUIN 提供一个 MCP 端点，任何兼容 MCP 的客户端 —— Claude Desktop、Claude.ai、自定义代理 —— 都可以使用用户签发的 API 密钥连接。每次调用都会被认证，并仅限于签发该密钥的用户。

可用工具

v1 工具目录为只读。每个工具都会自行发布输入 schema，LLM 客户端会自动接入 —— 无需手写 JSON。

• list_markets

  列出关于真实运输结果（航班延误、列车取消、海运瓶颈通过量）的当前开放预测市场。可选输入：category（FLIGHT、TRAIN、SHIP）、status（默认 OPEN）、limit（1–100）。返回市场 id、类别、问题、含当前价格的结果、累计成交量与关闭时间。

• get_market

  根据 id 获取单个市场，包含当前价格与结果。输入：id（市场 UUID）。

• get_my_positions

  列出已认证用户在所有市场中的未平仓位。无输入。返回 market_id、outcome_idx、持有份额与总成本基础。

• get_balance

  返回已认证用户当前的美元余额（以字符串形式）。无输入。

目前交易仅限 REST

交易、充值与提现暂未通过 MCP 开放 —— MCP 驱动的交易比读取动作影响面更大，我们希望在 UX 验证完成前继续保持人工参与。可使用按权限范围签发的 API 密钥通过 REST API 进行程序化交易。

连接客户端

1. 1.注册并完成账户验证。
2. 2.在账户设置中生成 API 密钥 —— MCP 使用 read 权限即可。
3. 3.将下方代码片段粘贴到兼容 MCP 的客户端中，并替换为你的密钥。

{
  "mcpServers": {
    "gaduin": {
      "url": "https://gaduin.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

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.

• 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 source 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.