Browse by use case

Choose the API around your workflow.

A card scanner, a deck tool and an inventory repricer need different data. Start with the job your API must do.

Updated 13 Sep 2026/By TCG API GuideDocumentation reviewPublisher disclosure

Match the API to the result your user needs

A price display needs the correct printing and market. A scanner needs a usable match and correction flow. A store needs mapped stock and reviewable price changes. Choose the outcome first, then compare the fields, limits and billing behind it.

These guides explain the full workflow with concrete examples, missing-data handling and a practical provider shortlist. They connect to direct comparisons so you can assess alternatives before choosing a plan.

Prices & market data

Recognition & collections

Catalog & architecture

Take the same workload into every comparison

List searches, lookups, history requests and scans separately. Count unique printing references after deduplication and check supported batch sizes. Monthly credits alone do not show whether an API can support the busiest period of your application.

Our first choice for a shared multi-game collection is TCGGraph. Use the pricing guide to evaluate the workload, and the developer guides to plan the integration.