Serper API

developer2026-10-28

On this page

Serper provides a hosted search endpoint that returns Google search results as JSON. Developers and agents read live results without scraping a results page. Serper is a third-party service; its product details are at https://serper.dev. APIbase exposes the same search capability as MCP tools that an agent calls directly, priced from 0 to 29.99 USD on the live listing.

What the Serper API returns

A search request takes a query string and returns structured JSON. The response holds organic results. Each result carries a title, a link, and a snippet. Depending on the query, the response can also include typed blocks such as news, images, and places. Check the provider documentation at https://serper.dev for current field names before you write a parser.

The Serper API returns search results, not the full body of each page. An agent that needs the text of a linked page makes a second request to that URL. Keep the two steps separate in your code so a failed page fetch does not discard the search results.

How APIbase exposes search to an agent

APIbase wraps search capabilities as MCP tools. The agent sees each tool with a defined input schema, sends a query, and receives JSON back. The agent does not handle the provider key or the raw HTTP request.

  • The tool exposes a named search action with a typed query input.
  • The gateway holds the provider credentials, so the key stays out of the agent prompt.
  • The response returns as JSON that the agent can parse before it answers.

Search tools fit agent loops where the model needs current facts. A research agent runs a query, reads the returned links, and decides which page to open next. The loop stops when the agent has enough evidence to answer.

Pricing for Serper calls through APIbase

The range for this integration runs from 0 to 29.99 USD. The live product listing holds the figure that applies at checkout. Check that figure before you budget an agent run that makes many search calls.

This page does not state the upstream rate, because no public direct pricing for Serper was checked. Compare the gateway range with the provider's own pricing at https://serper.dev before you choose between a direct integration and the gateway.

Search API or scraping

Use a search API when you need ranked results for a query. A scraper parses a results page, and that parser breaks when the page markup changes. A search API returns the same JSON structure on each call, so the parsing code stays stable.

Scraping can conflict with a site's terms of use, and a search API usually sets the terms for reuse of its output. Read the provider's terms before you store or redisplay results.

Scraping still fits a case the search API does not cover. One example is a specific page that you already know and need to read in full.

Caveats before you ship

Search results come from an upstream provider. The same query can return different links on different days, so store the query and the returned links with each answer.

  • Snippets are excerpts. Verify a fact from the linked page before the agent states it as true.
  • Rate limits and quotas apply at the provider and at the gateway. Handle a rate-limit response by waiting and retrying, not by sending more requests.
  • Check the provider terms for caching and redisplay of results.

Log each query and each returned link. That log shows which source supported each claim in an agent answer.

A minimal agent workflow

Give the agent one search tool and a short instruction. The instruction tells the agent to run a query, select the most relevant links, open those pages, and answer with citations to the URLs it used.

Keep the number of search calls per task small. Each call adds latency and cost. An agent that searches again and again for the same fact usually needs a clearer query, not more calls.

Test the workflow with questions that have a known answer. Compare the agent answer with the linked source. A mismatch shows that the agent summarized a snippet without reading the page.

Live pricing — developer

Price per call, developer tools Horizontal bar chart of the price per call and the cache-hit price, in US dollars, for 12 developer tools. The same values are in the table below the chart. Price per call Cache-hit price $0.0 $0.0005 $0.001 Usage Time SeriesUsage Time Series $0.0 $0.0 Per-Tool Usage BreakdownPer-Tool Usage Breakdown $0.0 $0.0 Usage SummaryUsage Summary $0.0 $0.0 Discover ToolsDiscover Tools $0.0 $0.0 Batch Tool CallsBatch Tool Calls $0.0 $0.0 Tool Quality MetricsTool Quality Metrics $0.0 $0.0 Tool Quality RankingsTool Quality Rankings $0.0 $0.0 List Programming LanguagesList Programming Languages $0.001 $0.0001 Check CVE ID Reservation Stat…Check CVE ID Reservation Status $0.001 $0.0001 Security Advisories (deps.dev)Security Advisories (deps.dev) $0.001 $0.0001 Dependency Tree (deps.dev)Dependency Tree (deps.dev) $0.001 $0.0001 Package Info (deps.dev)Package Info (deps.dev) $0.001 $0.0001 US dollars per call
Price per call for developer tools, cheapest first.

Data source: live tool catalog snapshot, fetched 2026-10-28.

Chart data as a table
ToolPrice per callCache-hit price
Usage Time Series$0.0$0.0
Per-Tool Usage Breakdown$0.0$0.0
Usage Summary$0.0$0.0
Discover Tools$0.0$0.0
Batch Tool Calls$0.0$0.0
Tool Quality Metrics$0.0$0.0
Tool Quality Rankings$0.0$0.0
List Programming Languages$0.001$0.0001
Check CVE ID Reservation Status$0.001$0.0001
Security Advisories (deps.dev)$0.001$0.0001
Dependency Tree (deps.dev)$0.001$0.0001
Package Info (deps.dev)$0.001$0.0001
ToolProviderPrice/callCache-hit
Usage Time Seriesaccount$0$0
Per-Tool Usage Breakdownaccount$0$0
Usage Summaryaccount$0$0
Discover Toolsapibase$0$0
Batch Tool Callsplatform$0$0
Tool Quality Metricsplatform$0$0
Tool Quality Rankingsplatform$0$0
List Programming Languagesjudge0$0.001$0.0001
Check CVE ID Reservation Statuscve-mitre$0.001$0.0001
Security Advisories (deps.dev)depsdev$0.001$0.0001
Dependency Tree (deps.dev)depsdev$0.001$0.0001
Package Info (deps.dev)depsdev$0.001$0.0001

Connect via MCP

How a tool call worksAn AI agent sends a tool call to the APIbase gateway. The gateway checks payment, calls the provider API, and returns the JSON result to the agent.Your agentAPIbase gatewayProvider API1. tool call2. paid call3. JSON result flows back to the agent
Diagram: the path of one tool call.

Data source: gateway design, no measured values.

$ curl -X POST https://apibase.pro/api/v1/tools/account.timeseries/call \
  -H "Content-Type: application/json" -d '{"params": {}}'

FAQ

Is the Serper API the same as Google Search?

No. Serper is a third-party service that returns search results through its own JSON API. Results can differ from a browser search session. Product details are at https://serper.dev.

How do I call Serper through APIbase?

Connect the search tool to your MCP client through the gateway, then send a query to the tool. The gateway handles the provider credentials and returns the JSON result. Start at the APIbase home page to find the connection steps.

What does a search call cost through APIbase?

The live listing sets the range at 0 to 29.99 USD. This page states no direct upstream rate.

Can an agent cite search results?

Yes. Instruct the agent to include the link for each result it uses. Store that link next to the answer so a reader can open the source and check the claim.

  1. STEP 1/2 Connect your MCP client
  2. STEP 2/2 Browse the full catalog

Published: 2026-10-28Source: live apibase.pro catalog snapshot