Scraping API PricesSerpApi vs Serper.dev
The cash-commitment and consumption-window boundary between monthly searches and expiring prepaid credits.
SerpApi
Serper.dev
The difference
Both paths, one ruler
SerpApi
Successes you want
100,000 standard searches
Your stated workload. Every vendor on this site is priced against this same number.
- × 1
Attempts you are billed for
100,000 standard searches
SerpApi does not bill failed fetches, so failures cost nothing here.
- × 1
What the meter counts
100,000 searchs
One attempt is one billed unit for this workload.
- =
Cash per month
$725.00 /mo
Searcher. Cheapest of every eligible purchase option, not the first plan that fits.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
Serper.dev
Successes you want
100,000 standard searches
Your stated workload. Every vendor on this site is priced against this same number.
- × 1
Attempts you are billed for
100,000 standard searches
Serper.dev does not bill failed fetches, so failures cost nothing here.
- × 1
What the meter counts
100,000 credits
One attempt is one billed unit for this workload.
- =
One-time prepaid cash
$375.00 prepaid
Standard. Cheapest of every eligible purchase option, not the first plan that fits.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
Both ladders share one linear scale, topping out at 100,000 counted units, so a longer bar means more billed work rather than a different drawing.
These figures are for one stated workload: 100,000 standard search calls with one default-depth result set per call. The comparison below names where the answer changes.
The boundary
After signup allowances are exhausted, the paid boundary is cash commitment over time, not just the displayed unit rate. For a one-month project at or below 1,000 successful searches, SerpApi’s entry plan requires the smaller purchase. If the same Google-style workload continues into a third month, Serper.dev’s minimum prepaid package can cover the accumulated searches without a third SerpApi monthly payment, provided the total remains inside the package and the credits are consumed before their six-month expiry. The decision also flips to SerpApi whenever the required engine or response type is outside Serper.dev’s published Google-centered APIs. (SerpApi pricing, retrieved 2026-07-26; SerpApi engine catalog, retrieved 2026-07-26; Serper.dev pricing, retrieved 2026-07-26)
This baseline counts one successful response as one billable search. SerpApi says cached, errored, and failed searches do not count, while a successful search counts once regardless of returned result count. Serper.dev says one credit is deducted for each successful response. The page does not infer equal result coverage, latency, or delivery quality, and it does not convert either vendor’s marketing into a benchmark. (SerpApi pricing, retrieved 2026-07-26; Serper.dev pricing, retrieved 2026-07-26)
How the billing models differ
SerpApi sells monthly search allowances in a long sequence of plans. It publishes hourly throughput by plan, no standard automatic overage rate, and an early-renewal path when the allowance runs out. Serper.dev sells prepaid credit packages rather than monthly subscriptions. Larger packages publish lower credit rates and higher query-per-second limits, and purchased credits remain valid for six months. The cost comparison therefore needs both monthly demand and the time needed to consume a package. (SerpApi pricing, retrieved 2026-07-26; SerpApi FAQ, retrieved 2026-07-26; Serper.dev pricing, retrieved 2026-07-26)
Throughput can move the boundary before total volume. SerpApi publishes an hourly capacity for every plan. Serper.dev publishes query-per-second limits that increase by package. A buyer should compare the required batch completion time, not treat an hourly number and a per-second number as interchangeable without conversion. (SerpApi pricing, retrieved 2026-07-26; Serper.dev pricing, retrieved 2026-07-26)
What each offers that the other does not
SerpApi publishes a broad catalog of engine-specific APIs and an Account API that exposes plan and usage information programmatically. Serper.dev concentrates on Google-oriented search types and offers a prepaid commercial model with a six-month consumption window rather than a recurring monthly commitment. SerpApi is the direct fit when a non-Google engine or a specific engine adapter is mandatory. Serper.dev is the direct fit when the Google-centered endpoint set is enough and a prepaid balance is operationally preferable. (SerpApi engine catalog, retrieved 2026-07-26; SerpApi Account API, retrieved 2026-07-26; Serper.dev pricing, retrieved 2026-07-26)
Who should pick which
Pick SerpApi for a one-month job at or below 1,000 successful searches, for broader engine coverage, or when a recurring monthly procurement model is preferable. Pick Serper.dev when its Google-centered endpoints are sufficient, use continues beyond two monthly SerpApi payments, the package will be consumed before expiry, and its published rate limit meets the batch deadline. For higher volume, compare the exact package purchase against the exact SerpApi plan rather than treating Serper.dev’s package rate as if it had no minimum top-up. (SerpApi pricing, retrieved 2026-07-26; Serper.dev pricing, retrieved 2026-07-26)
SerpApi does not clearly publish monthly-search rollover in the reviewed pricing material. Serper.dev does not state whether multiple top-up packages can be combined at one tier. Those unknowns matter for irregular demand and are not filled with assumptions. (SerpApi pricing, retrieved 2026-07-26; Serper.dev pricing, retrieved 2026-07-26)