BinderDex API / Preview
Pokémon and One Piece pricing data for inventory tools.
Match cards and sealed products, select the variant and condition you need, and evaluate the proposed price responses for your workflow.
In development. API access is not available yet.
Planned scope: English cards · US market · USD · Pokémon + One Piece · Raw cards + sealed products
Real BinderDex catalog data
Real BinderDex data · Select a product
Saved catalog data. See preview docs for the proposed API format.
Selected productPikachu exHolofoil · Near Mint$29.67 USDPokémon example selected.
Selected product
Pikachu ex
{
"record_type": "card",
"id": "EjEoW0K5lWyfUnKaPiDkM",
"name": "Pikachu ex",
"game": "Pokémon TCG",
"set": "Surging Sparks",
"card_number": "219/191",
"binderdex_url": "https://www.binderdex.com/cards/pikachu-ex-ssp-219191"
}{
"price_cents": 2967,
"currency": "USD",
"source": "binderdex",
"source_url": "https://www.binderdex.com/cards/pikachu-ex-ssp-219191",
"updated_at": "2026-09-06T14:36:59.120Z",
"source_as_of": null,
"captured_at": "2026-09-06T22:49:05Z",
"condition": "Near Mint",
"variant": "Holofoil"
}Fixed snapshot. No live price request is made.
Identity and price selection
Keep each selection explicit.
Keep a card’s identity distinct from the price lane you ask for. Sealed products use their exact package identity.
- 01Product identity
Game, set, collector number, and verified printing identify a raw card.
- 02Variant + condition
They select a price lane; they do not create a new card identity.
- 03Price context
Integer USD cents, a recorded update, and unknown observation time stay visible.
Read the proposal
See how an inventory integration would work.
Endpoints, nested schema fields, examples, errors, and the draft contract are documented as previews.
FAQ
Before you reach out.
Is API access available?
No. This is preview documentation for a proposed paid API. We are not issuing keys or operating an API endpoint.
What is the initial scope?
The proposal covers English US raw-card prices for Pokémon and One Piece, plus sealed-product identity and reference pricing for both games.
What remains a future request?
Price history, completed sales, grading data, and additional games are useful integration requests, but they are not available or committed features.
What will it cost?
Commercial terms are still under evaluation. The preview shows proposed request semantics, not an offer or price list.
What can I do today?
Read the proposed data model, assess the constraints against your workflow, and tell us what you need.
Shape the API
Have a real integration in mind?
Tell us about your product, the identifiers you rely on, and the data you need to make useful decisions.
Discuss your integration