Pricing
One credit, one search
Same price whichever engine you target and whichever country you ask for. Start on the free tier, move up when the volume justifies it.
Pricing is being finalised
The tiers below are drafts. Amounts, limits and tier names will change before launch, and nothing on this page is a published price. Email [email protected] if you need a firm number for a decision you are making now.
Free
Draft$0 to start
Enough to wire the integration up and see real results.
- Live and test API keys
- Both targets, all 190+ countries
- Single and bulk endpoints
- Community support
Growth
DraftTBC per month
For a product feature that runs searches on a schedule.
- Higher per-minute rate limit
- Bulk up to 50 queries per request
- Usage analytics in the dashboard
- Email support
Scale
DraftTBC per month
For sustained volume across several countries.
- Volume credit pricing
- Multiple keys per account
- Priority support
- Marketplace billing on request
FAQ
Credits, plainly
What counts as one credit?
One search. A cache hit costs the same as a live fetch, because the result still leaves our infrastructure and the freshness window is yours to choose with max_age.
Does a bulk request cost less?
No. A bulk call is billed per query inside it, exactly as if each one had been sent on its own. Bulk saves round trips, not credits.
Do failed searches cost anything?
A request rejected for a bad parameter costs nothing. A search the upstream engine failed to answer is charged, because the fetch was performed and only the answer is missing.
When will pricing be final?
Packaging is still being decided. The tiers on this page are drafts and will change before launch.
Start on the free tier.
Create an account, mint a key, and see what the responses look like against your own queries before any of this pricing matters.