For marketplaces
Autofill listings from a photo. Route the hard ones to a human.
One REST call turns a seller's card photo into structured listing data — name, set, number, year, rarity — in about 2-3 seconds, backed by a live catalog of 3,341,118+ cards across 43 games and sports. Confidence and needsReview tell you which matches are safe to auto-fill and which need a person to confirm.
Manual entry is slow, and sellers get it wrong
Asking a seller to type the set, number, and year for every card they list is friction that costs you listings — and the fields they do fill in are often wrong: a misremembered set name, a transposed card number, a guessed year.
A generic image classifier doesn't fix this if it can't tell you when it's unsure. A model that force-matches every photo to its nearest neighbor will happily autofill the wrong card onto a listing, and now you've got a data-quality problem baked into your catalog instead of a UX problem in your intake form.
Built to be trusted with autofill, not just accuracy
See it identify a listing photo right now — no seller flow to build first. Try the live scanner.
Priced for listing volume, not per-seller seats
Plans scale from a free tier for testing your intake flow up through a high-throughput tier built for marketplace-scale traffic, with rate limits that rise alongside your plan. Credit packs cover seasonal listing spikes without a plan upgrade.
See the full pricing page for every tier, overage rate, and rate limit.
Frequently asked questions
Can we auto-fill a listing without a human ever looking at it?
You control that entirely via the confidence threshold you set on your side. Many marketplaces auto-fill above a high-confidence cutoff and route everything else — including every needsReview result — to a lightweight confirm-your-card step or a review queue.
What happens when a seller's photo doesn't match anything in your catalog?
You get needsReview:true and card:null instead of a forced guess, with the closest candidates in alternates. That's a normal, billable identify request — not an error — so your integration can treat it as 'ask the seller,' not 'something broke.'
Do you support bulk or batch listing import?
The API is one card photo per request today. Most marketplaces call it once per seller upload as part of their existing intake pipeline rather than as a separate batch job.
How much does this cost at marketplace scale?
See the plan cards below for exact monthly caps and overage rates, plus credit packs for one-off spikes. If you need volume or SLA terms beyond the published tiers, talk to us directly.
Stop asking sellers to type in card data by hand.
Get an API key, send a listing photo, and see structured data come back in seconds.