Grail API
Sold-comps requests, priced like a utility.
Instant keys. Free tier. Overage credits at $3 / 1,000 requests. Commercial use included everywhere — no sales call, no approval queue.
Build and test, forever.
- 100 requests / mo
- 60 req / min
- 1 key
- ✓Up to 240 rows / request
- ✓Summary stats
- ✓JSON + receipts
- ✓Commercial use
For a live bot or a hobby app.
- 2,000 requests / mo
- 60 req / min
- 2 keys
- ✓Everything in Free
- ✓Async job queue
- ✓Live eBay sold comps
- ✓Usage dashboard
For a real product with users.
- 10,000 requests / mo
- 60 req / min
- 5 keys
- ✓Everything in Developer
- ✓Priority pacing
- ✓Highest freshness
- ✓Email support
For platforms and dashboards.
- 50,000 requests / mo
- 60 req / min
- Unlimited
- ✓Everything in Pro
- ✓Bulk jobs
- ✓Priority support
- ✓Custom rate limits
Enterprise
custom volume & SLAMillions of comps, whitelabel, custom markets, dedicated pacing and support. Tell us what you’re building — hello@grail.solutions.
FAQ
What is a “comp”?
A comp is one sold listing row. Billing is per search request, not per row returned. One request can return up to 240 rows.
Do I need OAuth or an app review?
No. Instant keys, no approval queue, commercial use on every plan including the free tier.
How far back does the data go?
eBay’s public sold window — roughly the last 90 days. Fresh, live, and cleaned on every request.
Can I use it in a commercial product?
Yes. Commercial use is included on every tier, free and paid.
What happens if I exceed my quota?
Overage credits are billed at $3 per 1,000 requests, or hard-cap your key. You choose.
Do you offer MCP?
Yes — point Claude, Cursor or any MCP client at the Grail comps server and ask for sold prices in plain language.