Ranges API

GTO preflop ranges over HTTP — NLHE and PLO (6- & 9-max), every stack depth. $100/month, key-authenticated, JSON, CORS-open.

Subscription & keys

Loading…

Quickstart

curl "https://pokerdata.io/api/v1/ranges/nl/v2/range?stack=100&spot=UTG_60%25_HJ_Call" \
  -H "Authorization: Bearer pdk_YOUR_KEY"

Discovery endpoints are free without a key. The complete endpoint reference — NLHE, PLO 6-max, PLO 9-max, parameters and examples — lives on the public API docs.

Usage

Sign in (or open the link from your checkout receipt) to see your API usage — REST and MCP combined.

Connect via MCP

Give Claude (or any MCP client) direct access to the ranges data. The server speaks the Model Context Protocol over a single HTTP endpoint and authenticates with your existing API key.

MCP needs an API key. Create one first — it takes a minute.

Get an API key

Server

https://pokerdata.io/api/mcp — Streamable HTTP, stateless. Auth: Authorization: Bearer pdk_YOUR_KEY (any active key from Subscription & keys).

  • list_gamesCovered stack depths and positions for every game — call first.
  • get_rangeThe GTO range for one spot, by action path (e.g. UTG_60%_HJ_Call).
  • get_nodeA whole decision — every available action with its range.
  • list_spotsEvery valid decision node for a stack depth, tagged by depth.

Claude Code (CLI)

claude mcp add --transport http pokerdata https://pokerdata.io/api/mcp \
  --header "Authorization: Bearer pdk_YOUR_KEY"

Claude Desktop / claude.ai (custom connector)

Settings → Connectors → Add custom connector
URL:    https://pokerdata.io/api/mcp
Header: Authorization: Bearer pdk_YOUR_KEY

Generic MCP client config (Cursor, Windsurf, …)

{
  "mcpServers": {
    "pokerdata": {
      "url": "https://pokerdata.io/api/mcp",
      "headers": {
        "Authorization": "Bearer pdk_YOUR_KEY"
      }
    }
  }
}

Smoke test (no client needed)

curl -s https://pokerdata.io/api/mcp \
  -H "Authorization: Bearer pdk_YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

MCP calls count toward the same usage meter as the REST API. Keys are minted under Subscription & keys and require an active subscription.