DEV Community

Pokedex Oracle
Pokedex Oracle

Posted on

Pokemon TCG card lookup starts with identity before price

#data #webdev

Pokemon TCG data has a different failure mode from species data.

A species lookup asks:

Which Pokemon is this?
Enter fullscreen mode Exit fullscreen mode

A card lookup asks:

Which exact printed object is this?
Enter fullscreen mode Exit fullscreen mode

That difference matters.

The public notes for this part of the reference stack are here:

This article builds on
the auditable Pokemon reference-stack note
and applies the same separation-of-concerns idea to card data.
For the game-data side of the model, see
the type matchup note
and
the evolution-route note.

Charizard Base Set card

A card name is not enough

"Charizard" is a Pokemon name.

It is not a complete TCG card identity.

To identify a card cleanly, I want at least:

  • card name
  • set id
  • set name
  • collector number
  • rarity
  • finish or variant
  • language
  • condition, if value is discussed
  • reference URL

Without those fields, price notes and collection notes become easy to mix.

Identity and value should be separate

One of the most common mistakes in TCG content is blending identity and price too early.

These are different layers:

{
  "identity": {
    "name": "Charizard",
    "set": "Base Set",
    "number": "4",
    "rarity": "Rare Holo"
  },
  "marketContext": {
    "condition": "near-mint raw",
    "currency": "USD",
    "snapshotType": "recent-market-signal"
  }
}
Enter fullscreen mode Exit fullscreen mode

The card identity should remain stable.

The market context can change every day.

That is why the price notes and set checklist notes are separate pages.

Set checklists are a useful middle layer

A set page helps connect individual cards to their printed context.

For a collector, the set layer answers questions like:

  • how many cards are in this set?
  • which collector numbers are missing?
  • which cards are variants or chase cards?
  • which sealed products belong to the era?
  • which cards need condition notes?

That is different from a species page and different from a price page.

Why this is useful for developer tools

If you are building a widget, MCP tool, spreadsheet helper, or collector app, separating identity from value keeps the output safer.

An assistant should not answer "what is this worth?" until it knows which exact card is being discussed.

Likewise, a collection checklist should not link every Charizard card to one generic species note. It should preserve card identity first, then add species context when useful.

Reference

For the canonical Pokemon reference layer, use Pokedex.me.

The local TCG cluster is a workflow layer. It explains how I separate card identity, set context, price signals, and collection notes before pushing the data into a larger Pokemon reference system.

Top comments (0)