Google Search API & Reader API Pricing
Google and Bing Search API requests start at $0.56 per 1K. Prepaid credit packs start at $18.
100 free credits after registration Current credit packs do not renew automatically
Prepaid API credit packs
Standard
- Get 20,000 credits
- 2 Parallel Lanes ? What are Parallel Lanes? A lane is one request running now. This plan has 2 lanes, so 2 requests can run at the same time. When one finishes, that lane is ready again.
- ≈2,400 throughput per hour ? How is throughput estimated? Throughput (RPM) = Lanes × (60s / 3s avg. latency). At 3s average latency, 1 lane ≈ 20 RPM ≈ 1,200 requests/hour.
- Real-time results
- Fast response time
- Email technical support
Credits valid for 6 months
Starter
- Get 132,000 credits
- 5 Parallel Lanes ? What are Parallel Lanes? A lane is one request running now. This plan has 5 lanes, so 5 requests can run at the same time. When one finishes, that lane is ready again.
- ≈6,000 throughput per hour ? How is throughput estimated? Throughput (RPM) = Lanes × (60s / 3s avg. latency). At 3s average latency, 1 lane ≈ 20 RPM ≈ 1,200 requests/hour.
- Real-time results
- Faster response priority
- Email technical support
- Eligible for Lane Stacking ? What is Lane Stacking? Add another eligible plan and your lanes add up in one account. More lanes mean more requests can run at the same time. 1× $99 = 5 Lanes 2× $99 = 10 Lanes $99 + $597 = 42 Lanes
Credits valid for 6 months
Pro
- ~1 Million credits
- 37 Parallel Lanes ? What are Parallel Lanes? A lane is one request running now. This plan has 37 lanes, so 37 requests can run at the same time. When one finishes, that lane is ready again.
- ≈44,400 throughput per hour ? How is throughput estimated? Throughput (RPM) = Lanes × (60s / 3s avg. latency). At 3s average latency, 1 lane ≈ 20 RPM ≈ 1,200 requests/hour.
- Real-time results
- Priority Request Routing
- Tier-1 Developer Support
- Eligible for Lane Stacking ? What is Lane Stacking? Add another eligible plan and your lanes add up in one account. More lanes mean more requests can run at the same time. 1× $99 = 5 Lanes 2× $99 = 10 Lanes $99 + $597 = 42 Lanes
Credits valid for 6 months
Ultimate
- Get 3,000,000 credits
- 113 Parallel Lanes ? What are Parallel Lanes? A lane is one request running now. This plan has 113 lanes, so 113 requests can run at the same time. When one finishes, that lane is ready again.
- ≈135,600 throughput per hour ? How is throughput estimated? Throughput (RPM) = Lanes × (60s / 3s avg. latency). At 3s average latency, 1 lane ≈ 20 RPM ≈ 1,200 requests/hour.
- Dedicated Cluster Node
- Zero Queue Latency
- Dedicated account manager
- Eligible for Lane Stacking ? What is Lane Stacking? Add another eligible plan and your lanes add up in one account. More lanes mean more requests can run at the same time. 1× $99 = 5 Lanes 2× $99 = 10 Lanes $99 + $597 = 42 Lanes
Credits valid for 6 months
Approximate requests per hour assume a 3-second average response time. Actual throughput varies by endpoint and response time.
Parallel Lanes and estimated throughput
Understanding Parallel Lanes and Lane Stacking
There are no hourly request caps. Your available Parallel Lanes determine how many requests can run at the same time. Actual throughput depends on endpoint and response time.
Estimated throughput formula:
Total Lanes = Plan A Lanes + Plan B Lanes Throughput (RPM) = Total Lanes × (60s / 3s avg. latency) Example estimate: At a 3-second average response time, 5 Lanes + 37 Lanes = 42 Total Lanes ≈ 840 Requests Per Minute (50,400/hour).
Enterprise / High Volume
Need a tailored concurrency plan? Contact support to discuss high-volume workloads and available enterprise arrangements.
Contact SalesCredit usage by API
One prepaid credit balance works across Search, Reader, File Extraction, and Screenshot APIs. Search APIs return results from search engines; Reader API extracts source content and is billed separately from SERP requests. See the Google Search API, Reader API, and Parallel Lanes pages for implementation details.
For other real-time data needs, please contact support.
Provider comparison guides
For provider-specific pricing, throughput, and endpoint differences, review the source-dated SearchCans vs SerpApi and SearchCans vs ScrapingBee guides.
FAQ: API credits, billing, and throughput
How are credits consumed, and do they expire?
Credits are valid for 6 months. Standard Google and Bing search requests use 1 credit each. Reader API standard mode uses 2 credits; Shared Pool with proxy:1 uses 4 credits total. Some advanced options use additional credits. One credit balance works across Search and Reader APIs, and credits are deducted only for successful HTTP 200 responses. See the credit-usage table below for the full breakdown.
How does billing work, and what payment methods do you accept?
Current SearchCans credit packs are prepaid one-time purchases and do not renew automatically. Buy credits for the workload you have now, then add credits when needed. Purchases support credit card payments through Stripe. Enterprise customers can contact us about invoice payments.
How reliable is the SearchCans API?
SearchCans targets 99.9% monthly uptime. This service-level objective is not a guarantee or warranty; check the status page for current service availability.
Can I get a refund?
Refund requests are eligible within 7 calendar days of payment when you have used less than 10% of the applicable plan credits. Approved refunds are subject to the fees described in Terms of Service Section 4.3.
Is the data provided through your API sourced legally?
Yes. We only extract publicly accessible search results using lawful, industry-standard technical methods. We never use illegal cracking techniques.