Key takeaways:
- Serper is prepaid, not a subscription. You buy credit packs ($50–$3,750), and the price drops from $1.00 down to $0.30 per 1,000 queries as your volume grows.
- Every new account gets 2,500 free queries with no credit card, and paid credits expire 6 months after purchase.
- A standard search returning up to 10 results costs 1 credit. Ask for 11–100 results and it costs 2 credits, so your effective price doubles.
- At $0.30–$1.00 per 1,000 queries, Serper badly undercuts SerpAPI ($9–$25 per 1,000) and sits close to DataForSEO ($0.60–$2.00) and Bright Data ($1.50).
If you've landed on the Serper dev pricing page, you've seen four numbers ($50, $375, $1,250, $3,750) and not much else. There's no monthly plan to compare, no per-seat math, just credit packs and a promise that it's the cheapest Google Search API around. That's clean, but it hides the questions that actually decide your bill: how much is one query, when do credits expire, and does asking for more results cost more?
This guide breaks down Serper pricing in full, with prices verified live on July 5, 2026. You'll get the credit model, the per-endpoint costs, a worked example that maps credits to a real workload, and a straight comparison against SerpAPI, DataForSEO, and Bright Data. By the end you'll know what Serper costs you, not what the pricing page implies.
What Serper Is and Who Pays for It
Serper is a Google Search API. You send it a query, it returns Google's results as clean JSON in about 1–2 seconds, and you skip the work of running proxies and parsing HTML yourself. It covers search, images, news, maps, places, videos, shopping, scholar, patents, and autocomplete.
The buyers fall into two camps. First are developers building SEO tools, rank trackers, and lead-gen scripts who need Google data at scale. Second, and growing fast, are AI engineers wiring live search into agents and retrieval-augmented generation (RAG) pipelines.
That second group is why demand keeps climbing. Language models store knowledge in their weights but can't reach anything past their training cutoff, which is exactly the gap RAG was designed to close in the 2020 NeurIPS paper by Lewis and colleagues that introduced the technique. An agent that needs today's facts has to fetch them, and a fast, cheap search API is the cheapest way to do it. With 84% of developers now using or planning to use AI tools, up from 76% a year earlier per Stack Overflow's 2025 survey, the pool of people who need something like Serper is only getting bigger.
Serper Pricing at a Glance
Serper API pricing follows a prepaid credit model, not monthly plans.
You buy a pack of credits, spend them as you make queries, and buy more when you run low. Bigger packs cost less per query. Here's the full lineup as of July 5, 2026.
Plan | Price | Credits (queries) | Price per 1,000 | Notes |
Free | $0 | 2,500 | $0.00 | No credit card required |
Starter | $50 | 50,000 | $1.00 | Entry paid pack |
Standard | $375 | 500,000 | $0.75 | 100 queries per second |
Scale | $1,250 | 2,500,000 | $0.50 | High-volume |
Ultimate | $3,750 | 12,500,000 | $0.30 | Lowest per-query rate |
Two details matter as much as the headline prices. Every paid credit is valid for 6 months from purchase, so buying the Ultimate pack to chase the $0.30 rate only pays off if you'll actually burn 12.5 million queries in half a year. And there's no enterprise tier published above Ultimate, so if you need a contract, an SLA, or invoicing, you'd have to ask Serper directly rather than pick a plan off the page.
How Serper's Credit System Works
One credit buys one search that returns up to 10 results. That's the rule that governs your whole bill, and it has a catch worth knowing before you write a line of code.
If you request more than 10 results in a single query (say you set the results count to 100), Serper charges 2 credits instead of 1. Your effective price doubles: the $1.00 Starter rate becomes $2.00 per 1,000 queries, and the $0.30 Ultimate rate becomes $0.60. So the pack you buy is only half the equation; how many results you request on each call is the other half.
This got more tangled in September 2025, when Google removed the num=100 parameter that let a single request pull 100 results at once. SERP APIs now page through results 10 at a time, which means deep result sets cost more calls than they used to. If your workload only needs the top 10 (most RAG and agent lookups do), you sidestep the whole problem and stay at 1 credit per query.
The prepaid model has one more edge worth naming. Because there's no subscription, you never pay for a month you didn't use, but you also can't roll unused credits past the 6-month mark. Plan your pack size around what you'll realistically spend in that window, not the lowest sticker rate.
What Each Serper Endpoint Costs
Serper's endpoints share the same credit rule, which keeps the math simple. A call to search, images, news, maps, places, videos, shopping, scholar, patents, or autocomplete each costs 1 credit for up to 10 results, and 2 credits if you ask for more.
That flat treatment is unusual. Some competitors charge a premium for specialized endpoints like maps or scholar, so a rank-tracking job and a local-listings job cost different amounts. With Serper, a scholar lookup costs the same as a plain web search, which makes budgeting across mixed workloads far easier.
Speed is consistent too. Independent testing by Scrapingdog clocked Serper's search endpoint at roughly 1.8–2.9 seconds, with scholar and news in the same range, so you're not paying a latency tax on the less-common endpoints. For an agent firing off image, news, and web queries in one run, that predictability in both price and speed is the practical payoff.
How to Calculate Your Real Cost per Query
The pricing page tells you the per-1,000 rate. It doesn't tell you what your workload will actually cost, and that gap is where teams overspend. Here's how to run the number before you commit.
As one engineer put it in an r/WebScrapingInsider thread on picking a SERP API, "Serperdev looks cheap until you map credits to your real workload." That mapping is the whole job. Do it in four steps.
Step 1: Count Searches per Task
Break one unit of work into its queries. An AI research agent answering a single user question might run 5 searches: one main query plus four follow-ups. A rank tracker checking 200 keywords daily runs 200 searches a day. Write down the real number, not the average you hope for.
Step 2: Check Your Results Setting
Confirm how many results each call requests. If 10 results cover the job, every query is 1 credit. If any step asks for more, that step costs 2 credits, so flag it and count it double.
Step 3: Multiply by Your Tier Rate
Take your credit count and multiply by the per-query price of the pack you'll buy. The research agent at 5 searches per question, running 10,000 questions a month, spends 50,000 credits. On the Starter pack that's $50; on Standard it's about $37.50.
Step 4: Add a Buffer for Retries and Expiry
Real workloads retry failed calls and hit occasional duplicates, so add 10–15% for waste. Then check the total against the 6-month expiry: if 50,000 credits a month means 300,000 over the window, the Standard pack (500,000 credits) leaves headroom without overbuying.
Run those four steps and you get a spend figure you can defend, not a sticker price. The difference between guessing and calculating here is often the difference between the Starter and Standard pack.
Serper vs SerpAPI, DataForSEO, and Bright Data on Price
Serper's pitch is that it's the cheapest Google Search API, and on raw per-query cost that mostly holds up. Here's how the entry-level rates compare, all verified July 5, 2026.
Provider | Entry price per 1,000 | Lowest per 1,000 | Free tier | Billing model |
Serper | $1.00 | $0.30 | 2,500 queries | Prepaid credits |
SerpAPI | $25.00 | ~$9.00 | 250 searches/month | Monthly subscription |
DataForSEO | $0.60 (standard queue) | $0.60 | $1 signup credit | Pay-as-you-go |
Bright Data | $1.50 | ~$0.55 (volume) | $5 signup credit | Pay per successful request |
Serper clears SerpAPI by a wide margin. SerpAPI's cheapest paid rate is $25 per 1,000 on its $25 Starter plan, dropping to about $9 per 1,000 on the $275 Big Data plan, so even at scale it's roughly 30 times Serper's Ultimate rate. What SerpAPI charges for is breadth and a U.S. legal indemnity, not price.
Against DataForSEO and Bright Data the gap narrows or flips. DataForSEO's standard queue runs $0.60 per 1,000 (cheaper than Serper's entry rate), though its live endpoint costs $2.00 and results take up to 5 minutes on the cheapest queue. Bright Data starts at $1.50 per 1,000 and only beats Serper once you're on a $499-plus monthly plan. Serper's real advantage over these two is simplicity and speed, not always the lowest number.
Serper Alternatives Worth Comparing
Price isn't the only reason to shop around. Support, endpoint coverage, and billing style vary enough that the "cheapest" tool isn't always the right one for your stack. Here are the alternatives worth a look, described plainly.
SerpAPI is the mature, feature-rich option with 24/7 support and the widest Google-product coverage, at a real price premium. DataForSEO is built for SEO platforms and rank tracking, with the cheapest standard-queue rate but slower turnaround. Bright Data and Oxylabs are enterprise data vendors: heavy infrastructure, high floors, best when you're already buying proxies at volume.
For lighter or more specialized needs, Serpstack and Zenserp offer simple subscription SERP APIs, ScrapingBee and SearchAPI.io bundle general scraping with search, and Scrapingdog undercuts most on price (1,000 free credits, rates below $0.0003 per call at volume). On the AI side, Tavily and Exa are search APIs designed for agents and RAG rather than raw SERP scraping, which can save you post-processing.
One classic option is effectively off the table for newcomers. Google's own Custom Search JSON API (100 free queries a day, then $5 per 1,000, capped at 10,000 a day) is now closed to new customers, with existing users given until January 1, 2027 to migrate. If you were counting on Google's official API, that door is closing, which is part of why the third-party market exists at all.
How to Keep Your Serper Bill Down
Serper is cheap per query, but a busy agent can still burn credits faster than you'd guess. A few habits keep the bill in check without cutting your data.
Cache Repeated Queries
Agents ask the same thing constantly. Store each query's JSON result with a timestamp and serve it from cache for a sensible window (an hour for news, a day for static facts). Every cache hit is a credit you didn't spend, and on repetitive workloads that can cut usage by a third or more.
Ask for 10 Results, Not 100
Since 11-plus results cost 2 credits, set your results count to 10 unless a task genuinely needs deeper coverage. Most RAG lookups only read the top few results anyway, so requesting 100 doubles your cost for data the model never uses.
Batch and Deduplicate
Before a run, strip duplicate queries and near-duplicates from your input list. A keyword file often has the same term in three casings; collapse them first. Deduplication is free, and Serper credits aren't.
Watch Your Credit Burn
Check your credit balance against your calendar, not just your usage. Because paid credits expire after 6 months, a slow month can quietly waste a chunk of a big pack. Buy the pack that matches your real 6-month run rate, then top up rather than overbuying for a discount you won't fully use.
Put together, these four habits routinely shave real money off a scaled workload, and none of them touch the quality of the data you get back.
Is Serper Worth It?
For most developers and AI builders, yes, and the reason is narrow: speed and price. If you need fast Google results as JSON and you're cost-sensitive, Serper's $0.30–$1.00 per 1,000 queries is hard to beat, and its 1–2-second responses keep agents snappy. That combination is why it keeps coming up in agent-building circles. In an r/AI_Agents thread on the cheapest realtime web search API, one builder's recommendation was blunt: try Serper at roughly $0.30 per 1,000 queries, far cheaper than the LLM-native search options.
Serper is the wrong pick in a few cases. If you need a signed SLA, guaranteed uptime, or a legal indemnity for scraping, the lack of a published enterprise tier and email-only support will bite. If your data lives outside the top 10 results, the 2-credit rule and Google's num=100 removal make deep result sets pricier than they look. And a recurring gripe on Reddit is payment friction from some regions, including reported card issues in India, so confirm you can actually pay before you build on it.
Weigh it against your workload, not the marketing. For a fast agent that reads the top few results and cares about cost, Serper is close to ideal. For a compliance-bound enterprise scrape, look at SerpAPI or Bright Data instead.
Picking Serper with Clear Eyes
Serper pricing is genuinely simple once you know the two rules that run it: you prepay for credits that get cheaper by volume, and one query costs 1 credit for 10 results or 2 for more. Start on the 2,500 free queries, map your real workload with the four-step calculation above, and buy the pack that matches your 6-month run rate rather than chasing the lowest sticker price.
Do that and Serper is one of the cheapest ways to put live Google data into your code. Skip the calculation and you'll either overbuy a pack that expires half-used or get surprised by a doubled bill on deep result sets. The tool is cheap; the discipline is what keeps it that way.
