# CardCorpus > An open Pokémon TCG dataset as static JSON: every set and card in English, Japanese and Chinese, each card's variants (print runs, finishes, stamps, errors), the Pokémon and people on them, and the links between prints across languages and reprints. No key, no sign-up, CORS open. Read the JSON, not the HTML. For people, https://www.cardcorpus.com/docs has a quickstart and a page per topic, and https://www.cardcorpus.com/explore draws these same files in a browser. ## Where to start - https://pokemon.cardcorpus.com/v1/index.json: the manifest. `files` lists every file (a pattern like `sets/{set}.json`) with its JSON Schema; `pointers` says how to follow a pointer; `pictures`, `prices` and `marketplaces` are url patterns; `counts` says how many of each thing there are. - https://pokemon.cardcorpus.com/v1/sets/english.json: every set of one catalog, with its `id` (`sets/japanese.json`, `sets/zh-hans.json` and `sets/french.json` are the others; index.json lists them in `catalogs`). `sets/{id}.json` holds the set, its cards and each card's `variants`. - https://pokemon.cardcorpus.com/v1/cards/english.json (also `cards/japanese.json`, `cards/zh-hans.json` and `cards/french.json`): every card of a catalog in one list (about 8 MB each, about 1 MB compressed), each a pointer with its name, number, rarity, card type, language, release date and picture: enough to search, filter and sort cards without opening a set file. - https://pokemon.cardcorpus.com/v1/vocabulary.json: every coded word the files use (rarity, role, finish, language, set type…), each with a `label` and, where curated, a `tell`: how to spot it on the card. - https://pokemon.cardcorpus.com/v1/schema/: one JSON Schema per file; every field has a `description`. - https://pokemon.cardcorpus.com/v1/docs/guide.md: the guide, in Markdown: pointers, ids, a card's variants and which field names which, links between cards, pictures, prices. The schema descriptions cite it by section. - https://pokemon.cardcorpus.com/v1/docs/reference.md: every field of every file in one page, generated from the schemas. ## Download, source and license - https://github.com/cardcorpus/pokemon-card-dataset: the same files as the API, in the same layout, as dated snapshots. Pin a build to one, or diff two to see what changed. - https://github.com/cardcorpus/pokemon-card-dataset/releases/latest: the latest snapshot as one zip (about 37 MB), for loading everything into your own database or working offline. Card images aren't in it: each image is an id that becomes a url (`pictures.sized` in index.json). - The live API is updated more often than the snapshots; prefer it for apps that want the newest data. - License: the dataset is CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Credit CardCorpus, e.g. "Card data from CardCorpus (cardcorpus.com)". Pokémon names and card pictures belong to their owners; the license covers the compiled data. Details: https://www.cardcorpus.com/docs/download - Report a wrong or missing card, with a link to evidence: https://github.com/cardcorpus/pokemon-card-dataset/issues/new/choose - The scanner, which names the exact print of a card in a photo: code at https://github.com/cardcorpus/pokemon-card-scanner (a Python package), models and index at https://huggingface.co/cardcorpus/pokemon-card-scanner. Docs: https://www.cardcorpus.com/docs/scanner ## Building with it - Every file is plain JSON over HTTPS, served with `Access-Control-Allow-Origin: *`, so a web page can fetch it directly. No key, no sign-up. - Every file has a JSON Schema (draft 2020-12), named in `index.json` `files` and in each response's `Link: <…>; rel="describedby"` header. Generate types from the schemas rather than guessing shapes. - Responses may be cached for 5 minutes (`Cache-Control: public, max-age=300`); files change in place when the data updates. Every file has an `ETag`: send it back as `If-None-Match` and an unchanged file answers `304 Not Modified` with no body, the cheap way to check for updates. - Send a User-Agent with your app's name and a way to reach you (a URL or an email), such as `MyCardApp/1.2 (+https://example.com)`, so we can warn you before a breaking change. Nothing is refused without one. - A wrong address answers a JSON 404 that says where to start and names the catalogs; don't guess addresses, follow `index.json` `files`. - Store ids, not urls or names, and look a stored address up in `moved.json` if it stops resolving. - Fetch a set file for a set's cards; use `cards/{catalog}.json` for search across every card of a catalog. ## Common questions - A card's variants (print runs, finishes, stamps, errors) and how to tell them apart: the card's `variants` in its set file, each with a `tell`. - The same card in another language: the card's `links.counterparts`, by catalog. Its reprints: `links.reprints`; the card it reprints: `links.reprintOf`. - Every card of a Pokémon, oldest first: `pokemon-cards/{species}.json`, where the species is its National Pokédex number (`pokemon.json` lists them all). - Every card an artist drew, oldest first: `artists/{artist}.json` (`artists.json` lists them all). - Cards given out at an event or in a product: `distributions/{distribution}.json` (`distributions.json` lists them all). ## How to read it - A pointer is an object with `$kind` and the ids that find its target, e.g. `{"$kind": "card", "set": "english/base-set", "card": "4"}`. Look up `index.json` `pointers[$kind]`: fill its `file` from the pointer's ids, then walk its `path`, at each step picking from `list` the item whose `match` field equals the pointer's `by` field. - The schemas' `x-cc` notes say what JSON Schema can't: `ref` (the kinds a pointer points at), `vocabulary` (the vocabulary.json group a value comes from), `picture` (an image id), `label` (the field that names an object) and `record` (a list item that sums up a record with its own file). - An image is an id. Fill it into `pictures.sized`, with a `{width}` from `pictures.widths`. The images are AVIF. - Ids are opaque and never change once published; an address that stops resolving is listed in `moved.json`. - Absent means not known or not applicable: there are no nulls, and an absent list is an empty one. Every count is always present. - The vocabulary only gains values: a value is never renamed in place.