Credit-based plans built for every stage
Credits equal the number of searches. Pay monthly or save with yearly billing.
Developer
For solo builders and early API integrations.
25,000 credits
- ✓25,000 credits API Credits
- ✓5 concurrent requests
- ✓Worldwide locations
Email support
Starter
For early-stage products and MVPs.
70,000 credits
- ✓70,000 credits API Credits
- ✓10 concurrent requests
- ✓Worldwide locations
Email support
Growth
For scaling teams and live workloads.
800,000 credits
- ✓800,000 credits API Credits
- ✓100 concurrent requests
- ✓Worldwide locations
Priority support
Scale
For high-volume production traffic.
2,250,000 credits
- ✓2,250,000 credits API Credits
- ✓250 concurrent requests
- ✓Worldwide locations
Priority support
Best for growing teams
One-time credits never expire. If you exceed your monthly plan, add top-ups to continue without interruption.
Simple credit model
1 credit equals 1 search request.
Developers choose OrbitScraper for predictable pricing
From startups to enterprise platforms, teams rely on our transparent credit model and reliable search coverage.
“We replaced a brittle in-house workflow with OrbitScraper and reduced monthly SERP infrastructure spend by around one-third.”
Nadia Tan
Growth Analytics Lead at 42 Singapore
“The credit model is predictable enough for client billing. We stopped overprovisioning infrastructure and improved project margins.”
Ravi Menon
Delivery Manager at Digital Impact
“Normalized JSON across engines removed response rewrite work from our sprint plan. Our team now focuses on insights, not maintenance fixes.”
Kenji Sato
Head of Data Products at Evolution Japan
“For recruitment keyword discovery, OrbitScraper made result collection stable and cost-effective compared with our DIY stack.”
Maya Singh
Automation Lead at RK Recruitment
“We needed reliable rank snapshots for weekly reporting. OrbitScraper cut failure retries and made turnaround times consistent.”
Arjun Patel
SEO Operations Manager at STIR
“Switching to API-based SERP collection reduced maintenance overhead and gave us clean data our product team could ship with immediately.”
Yuki Nakamura
Founder at Tokyo FinTech
“We replaced a brittle in-house workflow with OrbitScraper and reduced monthly SERP infrastructure spend by around one-third.”
Nadia Tan
Growth Analytics Lead at 42 Singapore
“The credit model is predictable enough for client billing. We stopped overprovisioning infrastructure and improved project margins.”
Ravi Menon
Delivery Manager at Digital Impact
“Normalized JSON across engines removed response rewrite work from our sprint plan. Our team now focuses on insights, not maintenance fixes.”
Kenji Sato
Head of Data Products at Evolution Japan
“For recruitment keyword discovery, OrbitScraper made result collection stable and cost-effective compared with our DIY stack.”
Maya Singh
Automation Lead at RK Recruitment
“We needed reliable rank snapshots for weekly reporting. OrbitScraper cut failure retries and made turnaround times consistent.”
Arjun Patel
SEO Operations Manager at STIR
“Switching to API-based SERP collection reduced maintenance overhead and gave us clean data our product team could ship with immediately.”
Yuki Nakamura
Founder at Tokyo FinTech
Payments, search, and credits
Quick answers to the most common questions about billing and usage.
Is 1 credit exactly equal to 1 SERP request?
Yes. Each successful /v1/search request consumes exactly 1 credit.
Does 1 credit cover one page of results or a full SERP session?
One request equals one page response for the parameters you send.
Do Ads, People Also Ask, Maps, or Shopping cost extra credits?
No. SERP features included in the same successful response do not add extra credit cost.
Does pagination (page=2, page=3) consume more credits?
Yes. Each additional page is a new request and uses 1 credit when it succeeds.
Which search engines are supported?
OrbitScraper currently supports Google, Bing, Brave, and DuckDuckGo.
Do you support Google News, Images, Shopping, and Maps?
Google vertical parameters are supported for common search views. Availability depends on query and engine response shape.
Can I target by country, city, and language?
Yes. Use gl for country, location for city/region context, and hl for language.
Can I choose desktop vs mobile?
Yes. Device targeting is supported with desktop and mobile options.
Do you support GPS coordinate targeting?
Not as a dedicated coordinate field in the public request schema today.
What is pricing for 1M–2M searches per month?
High-volume pricing is handled via enterprise plans. Contact sales for 1M+ and 2M+ monthly pricing.
What are the concurrency and rate limits?
Limits are plan-based and can include per-key policy overrides for RPM, quotas, and concurrency.
Do unused credits roll over?
Plan usage follows billing-cycle limits. For long-horizon usage, top-up credits are available.
Do top-up credits expire?
No. Top-up credits are one-time credits and do not expire.
Who handles checkout, taxes, and invoices?
Purchases may be processed by a merchant-of-record payment partner, which may handle checkout, tax calculation, invoicing, renewals, and eligible refunds.
Are taxes included in the listed prices?
Applicable taxes may be calculated at checkout based on billing location and merchant-of-record requirements.
Do subscriptions renew automatically?
Yes. Subscription plans renew automatically unless canceled before the next billing date. Cancellation stops future renewals at the end of the active billing period.
What uptime commitment do you provide?
OrbitScraper is built for high availability with monitored infrastructure; enterprise SLA terms are available for qualified plans.
Are only successful responses billed?
Yes. Credit deduction is tied to successful request completion.
What happens if a provider blocks a request?
The system uses retries and fallback provider paths. If a request cannot be completed, it returns a failure status.
Do responses come in structured JSON?
Yes. Responses are normalized JSON and include SERP sections when available.
Do you return organic positions, ads, snippets, PAA, and knowledge graph?
Yes, where present in the source SERP and normalized response output.
Do you return normalized JSON?
Yes. Public API responses are normalized JSON by default.