API and MCP | Hypothesis

Create a key

REST v2

Read account, map, and candle data

curl -sS -H "Authorization: Bearer hm_live_..." \
  https://hypothesis.services/v2/me

curl -sS -H "Authorization: Bearer hm_live_..." \
  "https://hypothesis.services/v2/history/BTC_USD?group=crypto_daily"

curl -sS -H "Authorization: Bearer hm_live_..." \
  "https://hypothesis.services/v2/candles/BTC_USD?group=crypto_daily&date=2026-08-15"

# Build a fresh prediction on demand (nothing is stored or posted)
curl -sS -H "Authorization: Bearer hm_live_..." \
  "https://hypothesis.services/v2/predict/BTC_USD?refresh=true"

MCP

Connect an authenticated MCP client

{
  "mcpServers": {
    "hypothesis": {
      "url": "https://hypothesis.services/mcp",
      "headers": {
        "Authorization": "Bearer hm_live_..."
      }
    }
  }
}

MCP tools include get_history, get_candles, get_latest_prediction, and predict_now — the last one computes a fresh map on demand from current bars.

Open routes include /v2/plans, /v2/catalog, and /v2/sample. API keys and MCP need The Works plan; Basic and Pro use the web app.