Head to head · Web search · October 2026 research run

SearchAPI.io vs Serper

SearchAPI.io scores 52 (D) on agent readiness against Serper's 11.7 (F), and leads in 5 of 7 scored categories. Serper leads on payments & pricing. Both do web search.

Best web search APIs for AI agents · All 353 search comparisons

Which one, for what

SearchAPI.io D

Best for Agents that need parsed results from many engines, especially shopping, ads, travel and social sources, at a low price per search.

Ahead on

  • Reliability, 90 against 30
  • Schema & documentation, 59 against 6
  • Agent ergonomics, 52 against 35
  • Security & auth, 28 against 20
  • Transparency & trust, 62 against 32

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
  • No incidents deducted, where Serper loses 15 points for them

Watch for

MCP loads one tool per engine with no toolsets

Serper F

Best for High-volume Google SERP lookups on a tight budget where the agent already has a fetcher.

Ahead on

  • Payments & pricing, 60 against 45

Watch for

No status page, SLA or incident history

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability SearchAPI.io +60

SearchAPI.io 90

Honeybadger status page at status.searchapi.io with Landing Page and API components and monthly history (20). Re-read on 4 November 2026, it shows no incidents in September, October or November 2026, and its incident feed's newest entry is the 11 February 2026 partial outage, so the window from 6 August is clean (30). The hourly cap is published, 20 per cent of the plan's monthly searches in any hour (15). The OpenAPI file lists a 429 response with an error string, but no Retry-After or backoff guidance was found. The partial 5 is kept pending the founder's rule on in-between values (5). The terms of 11 April 2026 give a 99.9% SLA for all plans with a credit of 100% of the monthly price, and the pricing page lists it on every plan (10). GA (10). 20 + 30 + 15 + 5 + 10 + 10 = 90.

Serper 30

No status page we could read. The site footer now has a "Status page" button drawn by script with no link, and status.serper.dev, whose robots.txt (Atlassian Statuspage) allows all but /api/ and /embed/, still redirects its home page and /history.atom to Atlassian's Statuspage marketing site on 11 November, as on 30 September (0). No readable incident history (5). Rate limits by pack, 50 queries a second on Starter, 100 on Standard, 200 on Scale and 300 on Ultimate, raised on request, now read from the served home page (15). No 429 or retry guidance found (0). No SLA in the terms (0). GA (10).

Schema & documentation SearchAPI.io +53

SearchAPI.io 59

OpenAPI 3.0 for the Google engine at /openapi/google.yaml with 25 typed parameters. We found no index of specs for the other engines, so 20 of 25. No llms.txt (404 on 4 November 2026) and no Markdown docs for agents (0). The API reference explains each parameter, and the MCP tool definitions aren't public (10). Enums for device, country, language, safe search and time period (14). Examples and a Postman collection, and the spec documents 400, 401, 403, 429 and 500 (12). /api/v1 in the path and no changelog anywhere we looked (3).

Serper 6

No OpenAPI or other spec (0). serper.dev/llms.txt returned 404 on 11 November and there are no Markdown docs (0). The documentation is the playground, a JavaScript page that showed us no text on 11 November. Per the 30 September check it lists the verticals and parameters such as gl and hl, so a few points for descriptions (3) and typed inputs (3). No examples or error responses we could read (0). No changelog or API versioning (0).

Transparency & trust SearchAPI.io +30

SearchAPI.io 62

Closed service with published terms (15). Privacy policy dated 11 April 2026. Data sits in the US, cached results are purged on an unstated schedule, and zero retention is Enterprise only (15). Google's num phase-out is documented, and there's no deprecation policy (3). US data location stated, and the privacy policy links a subprocessor page (15).

Serper 32

Closed service. The terms exist (updated 29 May 2024, UK law) but name no legal entity, only 'Serper' (8). The privacy policy (last reviewed 5 November 2025) says the service 'should normally not lead to the processing of personal data' and keeps most personal data for the life of the account, but states no retention period for queries or results (10). No deprecation policy or dated notices (0). Data processors are described by category without names, with transfers outside the EEA under an adequacy decision or standard contractual clauses (5).

Agent ergonomics SearchAPI.io +17

SearchAPI.io 52

The MCP exposes over 100 tools, one or more per engine, with no toolsets or filtering documented (5). page, time_period, location, country, language and safe search. Google's num has been fixed at 10 since September 2025 (18). Status codes are documented, but not how to recover from each (12). Searches are reads, and only HTTP 200 responses are billed, so retries are cheap. MCP annotations aren't visible (10). Two required parameters, engine and q. No official SDKs (7).

Serper 35

Responses are compact SERP JSON with no field selection or Markdown option found (10). Country and language parameters (the home page FAQ confirms both) and ten separate verticals. We couldn't confirm pagination or result-count parameters from the docs (8). No documented error responses (0). Searches are read-only, and the home page FAQ says credits are deducted only for successful responses (10). One required field (q) and no official SDK (7).

Payments & pricing Serper +15

SearchAPI.io 45

No x402, MPP or L402 (0). Monthly plans only, priced in public, from $40 for 10,000 searches to $5,000 for 5 million (10). 100 free requests with no card (20). A person has to sign up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Serper 60

No x402, MPP or L402. The FAQ lists major credit cards and PayPal only (0). Per-1,000 prices published without a login, from $1.00 on the $50 pack to $0.30 on the $3,750 pack, excluding sales tax (20). 2,500 free queries on sign-up, "No credit card required" on the home page (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Security & auth SearchAPI.io +8

SearchAPI.io 28

API keys with a documented api_key query-string option, and OAuth with expiring, rotating tokens for the MCP. The MCP page, re-read on 4 November 2026, now tells clients to send the token in the X-MCP-Token header and not in a URL. The registry's ?token= reading came from a JSON API this run doesn't use and is struck. The api_key query option stays documented in the API reference. 20 less 10 (10). Every action is a read, and there are no tool subsets (15). Results are third-party snippets and scraped AI answers, with no injection guidance (0). No per-call audit log found. The privacy policy says account logins are logged by IP (0). The trust centre at security.searchapi.io answers robots.txt with an app page, so it was left unread on 4 November 2026. No certifications, bounty or security.txt (404 on 4 November 2026) found. The partial 3 is kept pending the founder's rule on in-between values (3).

Serper 20

API key in the X-API-KEY header, never in the URL. No scopes, multiple keys or rotation found (10). Read-only search with no write surface, but no MCP annotations or least-privilege mode (10). Returns third-party titles and snippets with no prompt-injection guidance (0). No per-call log or audit trail found outside the logged-in dashboard, which we couldn't see (0). serper.dev/.well-known/security.txt returned 404 on 11 November, and we found no disclosure policy, bug bounty or certification (0).

Score by category

CategoryWeightSearchAPI.ioSerperEdge
Reliability16%9030SearchAPI.io +60
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%596SearchAPI.io +53
Agent ergonomics13%5235SearchAPI.io +17
Security & auth14%2820SearchAPI.io +8
Payments & pricing10%4560Serper +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%03Serper +3
Transparency & trust7%6232SearchAPI.io +30
Negative events≤150-15
TotalD 52/100F 11.7/100

Facts side by side

FactSearchAPI.ioSerper
KindHTTP APIHTTP API
VendorSearchApiSerper
Hosted endpointhttps://www.searchapi.io/api/v1/searchhttps://google.serper.dev/search
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
Price for web search$4 per 1,000 requestsnot published
x402nono
Read-only variant documentednono
llms.txtnono
MCP registryio.searchapi/mcpnot listed
Terms last updated2026-04-112024-05-29
Privacy policy last updated2026-04-112025-11-05
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates SearchAPI.io higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

SearchAPI.io

A 99.9% SLA in the terms on every plan, no status-page incidents since 11 February 2026, and over 150 engine endpoints behind one URL. The MCP loads one tool per engine with no toolsets, there is no changelog or official SDK, and every account starts with a browser signup.

Serper

$0.30 to $1.00 per 1,000 queries on prepaid packs, with no subscription. No status page, SLA or incident history.

Before you call either

SearchAPI.io

  1. Send the key as Authorization: Bearer, not api_key= in the URL
  2. Connect the MCP through OAuth or the X-MCP-Token header. Never put the token in the MCP URL
  3. Call the REST API with engine= when context is tight. The MCP loads one tool definition per engine
  4. Page Google results with page. num is fixed at 10
  5. Pace bursts. One hour can use at most 20 per cent of the plan's monthly searches

Serper

  1. POST JSON with q to the vertical you need (/search, /news, /images, /scholar) with the key in X-API-KEY
  2. Set gl and hl, since Google results vary by country and language
  3. Pair it with a fetcher. Serper returns links and snippets, not page text
  4. Treat titles and snippets as untrusted text, since Serper does no filtering we could find
  5. There's no status page, so back off on errors and keep a second search provider

Questions

Which is better for AI agents, SearchAPI.io or Serper?

SearchAPI.io scores 52 (D) on agent readiness against Serper's 11.7 (F), and leads in 5 of 7 scored categories. Serper leads on payments & pricing.

Do SearchAPI.io and Serper need an API key?

SearchAPI.io takes an API key or an OAuth sign-in. Serper needs an API key.

Can an agent call SearchAPI.io and Serper without installing anything?

Yes. SearchAPI.io has a hosted endpoint at https://www.searchapi.io/api/v1/search and Serper at https://google.serper.dev/search.

Other comparisons with SearchAPI.io or Serper

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.