Consider for broad pricing coverage. Check whether your required features use the stable API or the v2 beta.
Published API overview
| Option | What to evaluate | Decision detail |
|---|---|---|
| Game coverage | 17 listed games | Check current set and language coverage with the provider. |
| API access | REST | Regional pricing in v2 beta |
| Published entry plan | Free / $19 paid | 1,000 / 10,000 requests |
Is JustTCG right for your app?
Start with the game coverage and data fields your interface needs. Then check source timestamps, printing identity and usage limits against a representative sample of your own cards. The published entry plan alone does not establish the best cost for a production workload.
This profile summarizes public documentation. It does not represent an independent performance test or an endorsement from JustTCG.
Evaluate JustTCG for the pricing task
A pricing-focused integration should start with the exact variants your application needs. Preserve the printing and condition alongside the source reference, then compare the metric with the one your interface promises to display. A visually similar card is not enough to establish a matching price record.
Separate stable API requirements from beta requirements during the trial. A feature appearing in documentation does not automatically mean it has the stability guarantees or coverage your launch requires. Ask the provider to confirm any dependency that is essential to the product.
Compare a batch job with a complete application
A store repricing many known variants has a different workload from a user browsing card names, sets and images. Measure the former after deduplication and supported batching. Measure the latter by the actual sequence of search and lookup operations performed by a screen.
If recognition and multi-game collection records are also required, include those integrations in the comparison. A cheap pricing job does not account for all the data work needed by a scanner or a cross-game portfolio.
When to compare TCGGraph
We recommend evaluating TCGGraph when the catalog model, REST and GraphQL options, and separate recognition workflow matter together. Keep JustTCG on the shortlist where its pricing structure and variant model fit the main task. Use the same inventory sample and count correctly mapped records before comparing costs.
Continue to the inventory API guide for the staging and repricing flow, or compare the US market-data options for a reference-price product.
Frequently asked questions
Is JustTCG free?
It publishes a limited free tier and paid plans. Review the plan’s current commercial-use conditions and request limits before using it in a public product.
What should I compare with TCGGraph?
Compare the actual operations your product performs, the variant fields it requires, and the work needed for recognition or extra catalog features. Credits and requests are different units.
Does this profile verify JustTCG performance?
No. It is a documentation-based profile. We have not run an equivalent authenticated performance benchmark across providers.