BinderDex API

BinderDex API

Use with AI assistants

Muse, Claude, ChatGPT, and MCP.

Point your agent at the OpenAPI spec

The fastest integration for an AI assistant is the OpenAPI 3.1 document at https://api.binderdex.com/openapi.json. It has a summary, parameter descriptions, and a worked example for every operation, so most tool-calling agents can build a working connector from the URL alone plus a bearer key.

MCP server

BinderDex also runs a remote MCP server at https://api.binderdex.com/mcp, for clients that speak Model Context Protocol instead of OpenAPI tool-calling. It is a stateless Streamable HTTP endpoint: every request is a single JSON-RPC call over POST /mcp, there are no sessions to manage, and GET /mcp returns 405 (it never opens an SSE stream). It supports protocol versions 2025-06-18 and 2025-11-25.

Auth. Send the same live API key you'd use against /v1, as Authorization: Bearer <key> (or X-API-Key: <key>). A missing or invalid key gets a 401 with a WWW-Authenticate: Bearer header. Sandbox keys are rejected with a 403; the MCP server only serves live data.

Quota. initialize, tools/list, and ping are free. Each tools/call counts as one request against your normal 30/minute and 2,000/day limits and appears in your usage ledger tagged mcp:<tool_name>. If you're rate limited, the call still returns a normal MCP tool result (not a protocol error), with isError: true and a plain-text message telling you how many seconds to wait.

Tools. Six read-only tools, each accepting a response_format of "concise" (default) or "detailed". BinderDex tracks Pokemon and One Piece; pass game ("pokemon" or "one-piece") when the user names a specific game:

  • binderdex_search_cards: fuzzy name search with optional set/number/rarity/price/game filters.
  • binderdex_get_card: full detail and current prices for one card by id.
  • binderdex_get_price_history: a downsampled price history (at most 60 points) plus a computed trend summary.
  • binderdex_value_cards: totals a list of up to 50 cards (by id or by name/set/number/game); ambiguous or unmatched lines come back with up to 3 candidate suggestions instead of a guess.
  • binderdex_browse_sets: list sets (optionally filtered by game), or get one set's detail and top cards.
  • binderdex_get_market_movers: the biggest 7-day gainers or decliners, optionally filtered by game.

Every tool call returns both structuredContent (typed JSON matching its outputSchema) and a compact human-readable text block. Every price is USD with a price_updated_at timestamp; every card and set includes game/game_name, an id, and a url back to binderdex.com.

Claude

Code exampletext
claude mcp add --transport http binderdex https://api.binderdex.com/mcp \
  --header "Authorization: Bearer <your-live-api-key>"

Or add a custom connector in claude.ai pointed at https://api.binderdex.com/mcp with the same bearer key.

Muse

Add BinderDex as a custom MCP connector using the server URL https://api.binderdex.com/mcp and a live API key as the bearer credential. All six tools are read-only.

ChatGPT

For agent builders using MCP-compatible tool sources, point the connector at https://api.binderdex.com/mcp with the same bearer key. If your client only supports OpenAPI Actions, use the spec above instead; the MCP tools call the same underlying /v1 operations.

Claude (OpenAPI path)

If you'd rather integrate against the REST API directly, add a custom connector pointed at https://api.binderdex.com/openapi.json, and supply a live API key as a bearer credential when prompted. Claude will read the operation summaries and call the right one for a "what is this card worth" or "what's spiking this week" question.

ChatGPT (Actions)

In a custom GPT's Actions configuration, import the schema from https://api.binderdex.com/openapi.json and set authentication to API Key, Bearer. ChatGPT Actions caps operation summaries at 300 characters and parameter descriptions at 700; every operation in this spec is within those limits.

Notes for agent builders

  • All data is read-only. There are no write, purchase, or account-mutating operations.
  • Prices are BinderDex market estimates in USD cents, each with a price_updated_at timestamp. State the timestamp when quoting a price.
  • prices_batch is the efficient path for "what is my list worth": one call, up to 100 ids, one request credit.
  • Attribution to BinderDex is required whenever a response is shown to an end user; see the API Terms.