Our pick for expansion beyond Pokémon: TCGGraph
Choose TCGGraph when you need several games in one model or a recognition service alongside your catalog. For a free Pokémon-only project, TCGdex may already meet your needs.
The published features, side by side
| Decision point | TCGGraph | TCGdex |
|---|---|---|
| Game focus | 9 games | Pokémon |
| Access | Paid data plans from $19/month | Free and open source |
| Interfaces | REST + GraphQL | REST + GraphQL |
| Market data | EU and US sources | Cardmarket + TCGplayer fields |
| Card recognition | Separately billed service | Not documented in reviewed catalog docs |
| Integration approach | One catalog across games | Pokémon-focused schema and SDKs |
Source-reported features and monthly USD plans reviewed during 9–13 September 2026. See source links below; recognition, tax, overage and limits can affect total cost.
GraphQL and European prices are not exclusive
TCGdex documents both REST and GraphQL. It also exposes marketplace pricing in card responses. Comparing it as a REST-only database without prices would miss capabilities it already offers.
For a Pokémon collection prototype, start by checking language coverage, printing identity, image access and the price fields your interface needs. A free service can be a sensible long-term choice when the scope stays focused.
Pay for the complexity you actually remove
The commercial case for a unified API becomes stronger when your app adds another game or another workflow. Estimate the development time involved in reconciling schemas and maintaining integrations alongside the service fee.
That is a product decision, not a blanket claim that open-source data is unsuitable for production. Review the operating requirements and data-use conditions of either option before you rely on it.
Handle missing prices in either implementation
TCGdex explicitly notes that a marketplace can be omitted when a card has no matching listing. Your application should distinguish an unavailable value from a zero price. Use that same expectation when validating any other card-price API.
Choose TCGGraph for the combined multi-game workflow. Keep TCGdex on the shortlist when Pokémon is the whole product and its documented fields cover the experience you want.
Compare the cost of staying Pokémon-only
For a free Pokémon project, test the current catalog, languages, images and missing-price behavior before introducing a paid provider. If the complete workflow succeeds and the operating requirements fit, there may be no reason to replace the specialist.
If the roadmap adds other games, estimate the new adapters, schema mapping and maintenance. Keep that estimate distinct from the monthly data charge so the paid service is evaluated for the work it actually removes.
Plan an identity-safe migration
Retain your internal holding IDs and create a mapping between provider printings. Review ambiguous matches before switching price refreshes. A similar card name does not prove that two provider records describe the same finish or release.
Use the Pokémon pricing guide for matching and the GraphQL guide for query choices. We recommend TCGGraph for expansion into a combined multi-game workflow, while recognizing that TCGdex can remain sufficient for a focused application.
Frequently asked questions
Is GraphQL exclusive to TCGGraph?
No. Both TCGGraph and TCGdex document GraphQL access. Compare scope and actual schema requirements rather than treating the protocol as exclusive.
Does paying automatically improve catalog completeness?
No. Test the records your product requires and inspect missing fields directly. A price plan alone is not evidence of complete coverage.
Sources & review notes
Based on provider documentation reviewed during 9–13 September 2026. No independent benchmarks were performed. “Not documented” is not proof that a feature is unavailable.