Google search as an API call: fast, clean JSON, first 2,500 queries free
Serper is a Google Search API: send it a query and it returns Google's results, organic listings, knowledge graph, news, images, maps, and more, as clean structured JSON in about a second. Priced as pay-as-you-go credits with 2,500 free searches to start and no subscription required, it has become the discovery layer of DIY prospecting stacks and one of the most common tools handed to AI agents.
Overview
A large share of go-to-market work reduces to a Google search: find the decision maker's LinkedIn profile, check what a company does, see who ranks for a keyword, confirm a news event. Serper's entire product is making that search programmable: an HTTPS endpoint that takes the same query you would type into Google, applies the same operators (site:, quoted phrases, minus terms), and returns the results page as structured JSON with the title, link, and snippet of each result, typically in one to two seconds.
The GTM engineering pattern that made it famous is people-finding without scraping: a query like site:linkedin.com/in "CEO" "acme.com" returns public LinkedIn profiles from Google's index, and the result snippets usually carry enough (name, title, company) to qualify the person before spending an enrichment credit. That routes around both the fragility and the terms-of-service problems of scraping LinkedIn directly, which is why the search-then-qualify step of enrichment waterfalls is so often a Serper call.
The commercial shape is deliberately simple: 2,500 free queries to start, then prepaid credit packs from $50, no subscription, no seats, volume discounts as packs get bigger. That simplicity plus speed made Serper a default in the AI ecosystem too; it is one of the most commonly wired-in web-search tools for LangChain agents and n8n AI workflows, where a model needs fresh information and the developer needs predictable JSON. The trade-off is that Serper is an interface to Google rather than a database of its own: no stored records, no enrichment, just the world's search engine as a function call.
Best for
Builders who need programmatic Google results: DIY prospecting pipelines finding people and companies, AI agents that must search the live web, SEO tooling checking ranks at scale, and any workflow where 'what does Google say' is a step, priced casually enough to start free and pay only for volume.
Not the right fit for
- Teams that want a contact database or enrichment provider; Serper returns search results, not emails, phones, or firmographics, those come from the next tool in the waterfall.
- Buyers needing guaranteed SLAs and enterprise procurement apparatus; Serper is a lean self-serve service, not an enterprise data vendor.
- Full-page HTML scraping of arbitrary websites; Serper reads Google's results, and fetching the underlying pages is a different tool's job.
- Compliance-sensitive organizations that require a vendor to warrant the licensing posture of SERP data; the category as a whole operates in a gray zone buyers should assess for themselves.
- Non-technical users with no automation tool; there is no app to log into beyond a dashboard and playground, the product is the API.
How it works
- 1
You call an HTTPS endpoint (POST to google.serper.dev/search) with your API key and a JSON body containing the query, plus optional country, language, location, and pagination parameters. The response arrives as structured JSON: an organic array with position, title, link, and snippet for each result, plus typed blocks for whatever the results page contained, knowledge graph, answer box, people-also-ask, top stories, sitelinks.
- 2
Everything Google's query language supports works in the query string: site: to restrict to a domain (the LinkedIn people-finding pattern), quoted phrases for exact matches, minus terms to exclude, OR groups, filetype:, and date restriction via parameters. Location and language controls return geo-specific results, which matters for local-market prospecting and rank checking alike.
- 3
Beyond web search, parallel endpoints cover the other Google surfaces: images, videos, news, maps and places (local listings with ratings and contact data), shopping, scholar, patents, and autocomplete. Each returns the same style of predictable JSON, one credit per query, so a workflow can chain 'find the company's site' into 'pull its local listing' into 'check recent news' with three calls.
- 4
In practice almost nobody calls it from a terminal: Serper runs as an HTTP node in n8n or Make, a tool wired into a LangChain or agent framework, or a step in a script. The standard enrichment-waterfall shape is one Serper query per lead row, take the top two or three organic results, and hand their snippets to a language model to judge which, if any, is the right person, spending a fraction of a cent to decide whether to spend real enrichment credits.
Feature breakdown
15 features in 3 modulesSearch API
The core: Google's results page as predictable JSON.- Web search endpoint
- Organic results with position, title, link, and snippet, plus knowledge graph, answer boxes, people-also-ask, and sitelinks when present, one POST per query.
- Full Google operator support
- site:, quoted phrases, exclusions, OR groups, and filetype: pass straight through, so the LinkedIn people-finding pattern and every other power-search idiom work unchanged.
- Geo and language targeting
- Country, locale, and city-level location parameters return the results a local user would see, essential for local prospecting and international rank checks.
- Fast responses
- Results typically return in one to two seconds, quick enough to sit inline in agent loops and per-row pipeline steps without batching gymnastics.
- Pagination and result-count control
- Request more results per query or subsequent pages when the top ten is not enough, with credits metered accordingly.
Beyond web results
The other Google surfaces, one endpoint each.- News search
- Recent coverage with source and date, the trigger-events feed for outreach timed to funding, launches, and leadership changes.
- Maps and Places
- Local business listings with names, categories, ratings, and contact details, a lightweight local-lead source for geo-targeted prospecting.
- Images and videos
- Structured image and video results for content research and monitoring workflows.
- Shopping, Scholar, and Patents
- Product listings, academic results, and patent records for niche research pipelines that would otherwise mean manual searching.
- Autocomplete
- Google's query suggestions as data, a staple input for keyword and content research tooling.
Developer experience
Why it became the default search tool in agent stacks.- Interactive playground
- Test queries in the dashboard and see the exact JSON response, then copy working code snippets (cURL, Python, JavaScript) into your pipeline.
- Simple key auth
- One API key in a header; no OAuth dance, which is part of why wiring Serper into an n8n HTTP node takes about a minute.
- Batch queries
- Submit multiple searches in one request to simplify high-volume pipelines.
- Framework presence
- First-class integrations in LangChain and the agent ecosystem make Serper a drop-in web-search tool for LLM applications.
- Usage dashboard
- Credit balance and consumption tracking, the whole administrative surface of a deliberately minimal service.
Use cases
4 documentedFounder building a DIY enrichment waterfall
Has a spreadsheet of company domains and needs the decision maker at each, without paying per-seat for a prospecting database or scraping LinkedIn.
One Serper query per domain (site:linkedin.com/in "CEO" "domain.com") returns candidate profiles whose snippets carry name and title; a model qualifies the top results, and only qualified leads proceed to paid enrichment. The first 2,500 domains cost nothing at the search step.
Developer giving an AI agent live web access
An internal assistant needs current information, prices, news, documentation, beyond its model's knowledge, with responses fast and structured enough for an agent loop.
Serper as the agent's search tool returns parseable JSON in about a second; the agent reads snippets, picks what to fetch, and cites links, with credits consumed only when the agent actually searches.
SEO consultant monitoring client rankings
Tracks keyword positions across markets for a dozen clients; rank-tracker subscriptions price per keyword and per locale in ways that punish breadth.
A scheduled n8n workflow runs the keyword list through Serper with per-country parameters and writes positions to a sheet; costs scale with actual queries run, and adding a market is a parameter, not a plan upgrade.
Local-services agency prospecting by geography
Sells to dentists, gyms, and restaurants city by city, and needs fresh local business lists with ratings and websites rather than a stale purchased database.
The Places endpoint pulls current listings per city and category with contact details; the list lands in the standard waterfall for enrichment, and coverage of a new city costs a few dollars in credits.
Pricing
from Free for the first 2,500 queries; credit packs from $50 (about $1 per 1,000 queries)Prepaid pay-as-you-go credits: one credit per query across endpoints, purchased in packs with per-credit price falling at larger volumes. No subscription, no seats, no platform fee; 2,500 free credits on signup with no card required. Credits carry a validity window (published as six months on standard packs).
| Plan | Price | Includes |
|---|---|---|
| Free credits | $0 on signup |
|
| Starter pack | $50 prepaid, ~50,000 credits |
|
| Volume packs | Falling per-credit rates prepaid, larger packs |
|
Billing notes
- One query = one credit regardless of endpoint; requesting extra results per query can meter additional credits, so pipeline math is queries times credits-per-query.
- Prepaid packs mean cost cannot run away silently: when credits exhaust, calls stop, the opposite failure mode of auto-billed overage.
- Credits expire on a published window (six months on standard packs), so buy to your actual run rate rather than stockpiling.
- No seats, no platform fee, and no minimum makes Serper one of the few tools in a GTM stack whose cost model needs no negotiation or forecasting.
- Prices as published August 2026; per-credit rates at volume shift occasionally, check the current table before committing large packs.
Value assessment: At roughly a tenth of a cent per search, Serper prices the discovery step of a pipeline into irrelevance: the search cost of qualifying a thousand leads is about a dollar, before which 2,500 free credits mean most small teams' first month costs zero. Against SERP-API competitors it competes aggressively on price and speed; against not using a search API at all, it replaces either brittle scraping or a human's copy-paste hours. The value boundary is scope: it finds and reads Google for you, and every downstream step, choosing, enriching, verifying, is another tool's spend.
Strengths & limitations
Strengths
- Pay-as-you-go with 2,500 free queries and no subscription; the lowest-commitment tool in the entire GTM stack.
- Fast (one to two seconds) and structured, which is exactly what agent loops and per-row pipeline steps require.
- Full Google operator pass-through makes the LinkedIn people-finding pattern and every power-search idiom programmable.
- Breadth of endpoints (news, places, images, scholar, patents, autocomplete) turns many one-off research chores into API calls.
- Trivial integration: key auth and clean JSON mean an n8n HTTP node or LangChain tool wires up in minutes.
- Prepaid credits fail safe: exhausted balance stops calls rather than surprising the invoice.
Limitations
- No data of its own: no contacts, no emails, no firmographics, Serper ends where the results page ends.
- Dependent on Google's results and subject to changes in how Google structures and gates them; the category's ground truth can shift under it.
- SERP-data licensing sits in an industry-wide gray zone; compliance-sensitive buyers must make their own assessment, as with every provider in this space.
- A lean company with minimal public enterprise apparatus: no published SLAs, thin procurement collateral, support by email.
- Credit expiry penalizes stockpiling, and very spiky usage needs modest planning.
- Result snippets are sometimes too thin to qualify a lead alone, which is why the pattern pairs Serper with a model rather than trusting position one.
Head-to-head comparisons
3 alternativesSerper vs n8n
from About $24/mo (Cloud Starter, 2,500 executions; roughly $20 on annual billing)Engine and instrument: n8n runs the workflow, Serper answers its search steps. Serper's key-auth JSON API is exactly what n8n's HTTP node wants, and the combination appears in most published enrichment-waterfall templates. There is no rivalry to adjudicate, only the observation that Serper without an automation engine is a playground, and n8n without a search step is blind to the live web.
Full Serper vs n8n comparisonSerper vs Make
from $9/mo (Core, 10,000 operations, annual billing)A pairing rather than a contest: Serper is a data source, Make is the engine that calls it. Make's HTTP module drives Serper's search API cleanly (one POST per query, one operation per call), and the combination gives no-code builders programmatic Google results inside visual scenarios, the discovery step of the DIY enrichment stack without touching code.
Full Serper vs Make comparisonSerper vs Findymail
from $49/mo (Basic, 1,000 finder + 1,000 verifier credits)Sequential steps of one waterfall: Serper identifies who the person is; Findymail turns that name and domain into a verified email. Serper costs a tenth of a cent and answers 'who'; Findymail costs a real credit and answers 'how to reach them', with verification built in. Running Findymail only on Serper-plus-model qualified leads is the cost discipline that makes the DIY stack's economics work.
Full Serper vs Findymail comparisonImplementation & onboarding
- Setup time
- Minutes: sign up, copy the key, test in the playground, paste a working snippet into an n8n HTTP node or script. There is nothing else to configure.
- Learning curve
- Trivial for anyone who has called an API; the real skill is Google's query language itself, site: patterns, quoting, and exclusions, which transfers directly from power searching.
- Onboarding
- Fully self-serve: dashboard, playground, and documentation. No sales motion exists below high-volume conversations.
- Migration notes
- Switching between SERP APIs is low-friction, request and response shapes differ modestly and adapters are small. The work lives in your prompts and parsers, not the vendor relationship; keep the query-building logic separate and portability is nearly free.
Platform, API & security
- Platforms
- REST APIWeb dashboard and playground
- API
- The product is the API: HTTPS endpoints per Google surface (search, news, images, videos, places, maps, shopping, scholar, patents, autocomplete), key authentication, JSON responses, batch support, with official snippets for common languages and first-class presence in LangChain and agent frameworks.
- Compliance
- GDPR (data-processing terms published)
- Data residency
- Not published; a cloud service fronting Google's public results.
- SSO
- Not applicable; dashboard accounts with API keys.
- Security notes
- The service processes queries rather than storing your business data, which keeps its security surface small; treat API keys like any credential and scope spend with prepaid packs.
Support & resources
- Channels
- Email supportDocumentation and playground
- Documentation
- Concise, accurate API documentation with per-endpoint examples and an interactive playground that doubles as a query-debugging tool.
- Community
- No formal community; presence is strongest in the AI-agent and automation ecosystems, where templates and integrations circulate.
Company
- Founded
- 2023
- Headquarters
- Not disclosed (remote)
- Ownership
- Bootstrapped, independent
- Employees
- Small team (not disclosed)
- Funding
- No disclosed outside funding.
Timeline
- 2023Launches as a minimal, fast Google Search API with pay-as-you-go credits and a generous free allowance.
- 2024Becomes a default web-search tool in the LangChain and AI-agent ecosystem; endpoint coverage grows across Google's surfaces.
- 2025The DIY enrichment playbook popularizes the site:linkedin.com/in pattern, making Serper the discovery step of budget prospecting stacks.
- 2026Established as the GTM engineer's search primitive: 2,500 free queries in, roughly a dollar per thousand after.
Integrations
- n8n (HTTP node)
- Make (HTTP module)
- Zapier (webhooks/code)
- LangChain
- OpenAI tool use / function calling
- Python / JavaScript (official snippets)
- cURL / any HTTP client
- Google Sheets (via automation engines)
Frequently asked questions
10 questionsWhat is Serper?
Serper is a Google Search API: it takes a query, runs it against Google, and returns the results page as structured JSON, organic results, knowledge graph, news, images, maps, and more, typically in one to two seconds. It is priced as prepaid credits with 2,500 free searches on signup and no subscription.
How much does Serper cost?
The first 2,500 queries are free with no card. After that, prepaid credit packs start at $50 for roughly 50,000 queries (about $1 per 1,000), with per-credit prices stepping down toward roughly $0.30 per 1,000 at large volumes. One query consumes one credit, and standard packs carry a six-month validity window.
How do people use Serper to find LinkedIn profiles?
By searching Google's index of public profiles rather than touching LinkedIn: a query like site:linkedin.com/in "CEO" "acme.com" returns matching profiles, and each result's title and snippet usually carry the person's name, role, and company, enough to qualify the lead before spending enrichment credits. This avoids scraping LinkedIn directly, which is both fragile and against its terms.
Does Serper return emails or contact data?
No. Serper returns search results, whatever Google shows for your query. Contact data comes from the next step in a pipeline: once a search identifies the person, an enrichment tool like Findymail resolves the verified email, and a verifier like NeverBounce double-checks it.
What Google surfaces does Serper cover?
Web search plus parallel endpoints for news, images, videos, maps and places (local listings with ratings and contact details), shopping, scholar, patents, and autocomplete, each returning structured JSON at one credit per query.
Do Google search operators work through Serper?
Yes, the query string passes through Google's own language: site:, exact-phrase quotes, minus exclusions, OR groups, and filetype: all behave as they do in the search box, and country, language, and location parameters control which market's results you see.
Why is Serper popular for AI agents?
Because agent loops need exactly what it offers: live web results, returned fast, in predictable JSON, behind simple key auth, priced per call. LangChain and similar frameworks ship Serper integrations, making it a drop-in 'web search' tool for LLM applications.
Is using a Google Search API allowed?
The SERP-API category operates in a long-standing gray zone: these services fetch and structure publicly served search results, and the entire competitive field (Serper included) works this way. It sidesteps scraping the target sites themselves, but compliance-sensitive organizations should make their own assessment of the model, as no provider in the category can fully warrant it for you.
How fast is Serper?
Typical responses land in one to two seconds, which is fast enough to run inline per lead row in an automation or inside an agent's reasoning loop, the speed positioning the service was built around.
What happens when my credits run out?
Calls stop until you buy another pack, prepaid credits are the whole billing model, so there is no auto-billed overage and no surprise invoice. For always-on workflows, watch the balance in the dashboard and repurchase ahead of exhaustion.
Editorial verdict
Serper does one thing, turns Google into a function call, and does it with exactly the properties the job needs: speed, clean JSON, operator pass-through, and pricing so light it rounds out of most budgets. That makes it the discovery primitive of the DIY prospecting stack and the default search tool of the agent ecosystem, with 2,500 free queries lowering the cost of trying it to zero. It is deliberately not a data vendor: no contacts, no enrichment, no enterprise apparatus, and its ground truth belongs to Google, whose changes it inherits. As the first step of a waterfall that hands off to a model for judgment and an enrichment tool for contact data, it is close to unimprovable for the price.
Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.
Awards & badges
1 heldSerper holds 1 award from the SaaSTracker editorial program. Badges may be displayed by the vendor; each embed links back to this profile.
Innovation · GTM Engineering
“Turned Google's results page into a sub-cent API call, making programmatic prospecting a line item instead of a scraping project.”
<a href="https://saastracker.org/products/serper"><img src="https://saastracker.org/badges/embed/serper/innovation-summer-2026.svg" width="180" height="180" alt="Serper: Innovation, GTM Engineering. SaaSTracker Summer 2026 Awards." /></a>