Overview

A proposal you can evaluate

BinderDex API is in development. These docs describe an intended integration, not an available service. You cannot obtain API keys or make live data requests yet. All examples are synthetic, and schemas and limits may change.

The proposal covers Pokémon card prices, One Piece card prices, and sealed-product reference prices. The first workflow we’re exploring is a nightly inventory review for US card shops: identify an exact card printing or sealed product and compare a matching reference price with inventory records.

Four proposed operations

• Find products: browse by game and product kind, or resolve an external identifier against a curated catalog.
• Read a product: inspect a card’s set, collector number, printing, and price options, or a sealed product’s edition and package contents.
• Read prices in a batch: select a card’s exact variant and condition or a sealed product, then receive an explicit freshness or missing-data status for each selection.
• Read usage: inspect the organization’s intended request allowance.

Start with the preview walkthrough, then review data quality. The OpenAPI preview contains the proposed request and response schemas.

What this preview does not establish

The example catalog is not a coverage list. A schema field is not a promise of licensed access to that data. Example limits are design values, not a subscription plan. We have not published pricing, a launch date, or service-level commitments.

Raw card prices for both games and sealed-product prices are in the proposal. Historical series, sales feeds, graded-card prices, grading data, images, and additional games remain outside it. We still want to hear if your integration needs them.

Help shape the API

Tell us what you’re building. A useful starting point is your current workflow, the exact data you need, and what prevents your current approach from working. No account is required to get in touch.