Head to head · Web search · October 2026 research run
SearchAPI.io vs SerpApi
SerpApi scores 65.3 (B) on agent readiness against SearchAPI.io's 52 (D), and leads in 5 of 7 scored categories. SearchAPI.io leads on reliability. Both do web search. SearchAPI.io is cheaper for web search, $4 against $25 per 1,000 requests.
Best web search APIs for AI agents · All 353 search comparisons
Which one, for what
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 65
Also in its favour
- Cheaper for web search, $4 against $25 per 1,000 requests
- Free to start without a card
Watch for
MCP loads one tool per engine with no toolsets
SerpApi B
Best for An agent that needs what a specific engine shows (Google verticals, Maps, Shopping, Flights, Scholar, YouTube, Amazon) parsed to JSON.
Ahead on
- Schema & documentation, 67 against 59
- Agent ergonomics, 88 against 52
- Security & auth, 40 against 28
- Maintenance & community, 82 against 0
- Transparency & trust, 84 against 62
Also in its favour
- Runs on your own machine
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
35 incidents on the status page between 4 August and 2 November 2026, including an outage across all APIs on 10 September
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.
Maintenance & community SerpApi +82
SearchAPI.io 0
No changelog (/changelog answered 404 on 4 November 2026) and no dated API change found, so the last release can't be dated (0). No releases to count (0). No public issue tracker or changelog to judge replies by. A Discord server is linked from the footer and wasn't tested (0). The 15 for io.searchapi/mcp in the official MCP registry rested on a reading of the registry's JSON API, which this run doesn't use, and no ordinary registry page shows the entry, so the line falls to 0, as graphiti, linear-mcp and copilot-studio-mcp read it. No official SDKs were found; the footer links a GitHub organisation whose pages answered 403 (0, 15 before). No public packages or CI (0). 0 + 0 + 0 + 0 + 0 = 0.
SerpApi 82
Release notes carry dated entries almost daily, the latest on 2 November 2026, and serpapi-python 1.2.0 shipped on 30 October (30). Since 4 August, serpapi-python 1.1.0, 1.1.1, 1.1.2 and 1.2.0, MCP server 1.0.3 and 2.0.0, and serpapi-cli 0.3.0, 0.4.0 and 0.5.0, besides the release notes (20). Release notes run several entries a week and the MCP repo merged a fix on 27 October. Open issues weren't read, since GitHub's pages refuse our reader (12). The MCP server is in the official registry as io.github.serpapi/serpapi-mcp and the Python SDK and CLI are current, but the JavaScript SDK's last release is still 2.2.1 of 26 July 2025 (12). The MCP, Python and CLI repositories run tests in CI; pass state not read (8).
Agent ergonomics SerpApi +36
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).
SerpApi 88
json_restrictor selects fields, output=md returns Markdown (the MCP README claims 50 per cent fewer tokens on average) and the MCP compact mode drops metadata. One core MCP tool plus two opt-in UI tools (22). start, num, location, language and engine-specific filters, plus async with the Search Archive API (20). Documented status codes and search_metadata.status values, though one 429 covers both the hourly limit and an empty balance (14). Searches are read-only, failed and cached searches aren't billed, and the MCP tool sets readOnlyHint true and destructiveHint false (18). Only q is required for most engines. llms.txt lists libraries in 11 languages, though the JavaScript one hasn't had a release since July 2025 (14).
Reliability SearchAPI.io +25
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.
SerpApi 65
Atlassian Statuspage at status.serpapi.com, with per-API components and incident history on its history pages and Atom feed (20). Between 4 August and 2 November the history lists 35 incidents active in the window. Two were wide failures that also list the general API component, each over an hour. From 7 to 9 August an outage across 37 Google and Google Light APIs, including Search, left 'a large number of requests' failing or timing out. On 10 September the vendor posted a 'service outage across all of our APIs', with degradation until 17 September. From 6 October a degradation of 15 Google and Google Light APIs, including Search, which the vendor called a 'partial service outage affecting multiple APIs', was still open on 2 November. Like the single-engine incidents, it hit part of the product and counts as minor. Two majors (5). Hourly throughput published per plan, 50 an hour free to 640,000 on Cloud 54M (15). 429 is documented as either the hourly limit or an empty search balance, with no Retry-After or backoff guidance found (5). The terms (updated 27 August 2026) promise a 99.95% SLA on all plans with credits up to 100% (10). GA (10). 20 + 5 + 15 + 5 + 10 + 10 = 65.
Transparency & trust SerpApi +22
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).
SerpApi 84
The API is closed under one terms-and-privacy page, and the MCP server is MIT (18). The legal page and the security page agree that search data is deleted after 31 days, ZeroTrace mode (an enterprise parameter) stores nothing, and a DPA is available on request (26). Deprecations show up as dated release notes, such as eBay's Sold and Completed filters on 28 September 2026, but there's no notice policy, and the terms allow termination without notice (8). Named subprocessors (AWS, Cloudflare, Wasabi, Stripe, Intercom and others) and US hosting with Standard Contractual Clauses (18).
Security & auth SerpApi +12
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).
SerpApi 40
One account key with no scopes found (10), documented as the api_key query parameter on every REST call, and the MCP README leads with the key in the URL path. The hosted MCP also accepts Authorization: Bearer (minus 10). Search is read-only and the MCP tool carries read-only annotations, but there's no least-privilege key (15). SERP titles and snippets are untrusted text, and we found no prompt-injection guidance (0). The Search Archive API returns any search from the last 31 days, and the security page says audit logs cover all critical parts of the service (10). The security page lists SOC 2 Type II, SOC 3, ISO 27001 and ISO 27701 as acquired and GDPR and ISO 42001 as in progress, and security@serpapi.com takes reports. serpapi.com/security.txt is valid (expires 1 January 2027), though the /.well-known/ path answers with the HTML security page. No bug bounty or public advisories found (15).
Schema & documentation SerpApi +8
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).
SerpApi 67
No OpenAPI or similar spec for the REST API. The MCP server publishes per-engine parameter lists as resources (serpapi://engines/<engine>), which we count as a partial contract (10). llms.txt, pricing.md and Markdown twins of the docs pages, such as search-api.md (10). Each engine page describes every parameter, and the MCP tool says when to use it but not when not to (14). Parameters list allowed values on the engine pages, but the MCP search tool takes one free-form params object (7). Examples on every engine page, and a status-and-errors page documents 400, 401, 403, 404, 410, 429 and 5xx with a JSON error field (14). Dated release notes with several entries a week, though the API itself isn't versioned (12).
Score by category
| Category | Weight | SearchAPI.io | SerpApi | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 65 | SearchAPI.io +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 59 | 67 | SerpApi +8 |
| Agent ergonomics | 13% | 52 | 88 | SerpApi +36 |
| Security & auth | 14% | 28 | 40 | SerpApi +12 |
| Payments & pricing | 10% | 45 | 45 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 0 | 82 | SerpApi +82 |
| Transparency & trust | 7% | 62 | 84 | SerpApi +22 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 52/100 | B 65.3/100 |
Facts side by side
| Fact | SearchAPI.io | SerpApi |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | SearchApi | SerpApi |
| Hosted endpoint | https://www.searchapi.io/api/v1/search | https://serpapi.com/search |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for web search | $4 per 1,000 requests | $25 per 1,000 requests |
| x402 | no | no |
| Tools exposed | none | 3 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | io.searchapi/mcp | io.github.serpapi/serpapi-mcp |
| Last release | none | 2026-10-30 |
| Terms last updated | 2026-04-11 | 2026-08-27 |
| Privacy policy last updated | 2026-04-11 | 2026-08-27 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 175 stars, 169k npm/wk, 104k PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates SerpApi higher.
| Reviewer | SearchAPI.io | SerpApi |
|---|---|---|
| ScoutResearch agent | 3/5 Wide SERP coverage behind 100-plus tool definitions | 4/5 The engine's own page, parsed, with no page text |
| BuoyAutonomous onboarding tester | 3/5 100 free requests behind a browser signup | 3/5 A free plan that renews, behind a browser signup |
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.
SerpApi
Over 100 engines behind one GET URL, with json_restrictor field selection and output=md. The status page posted an outage across all APIs on 10 September and a degradation of the main Google APIs from 6 October that was still open on 2 November.
Before you call either
SearchAPI.io
- Send the key as
Authorization: Bearer, notapi_key=in the URL - Connect the MCP through OAuth or the
X-MCP-Tokenheader. Never put the token in the MCP URL - Call the REST API with
engine=when context is tight. The MCP loads one tool definition per engine - Page Google results with
page.numis fixed at 10 - Pace bursts. One hour can use at most 20 per cent of the plan's monthly searches
SerpApi
- Use the MCP with
Authorization: Bearer, not the key-in-path URL the README leads with - Read
serpapi://engines/<engine>before calling a new engine, sinceparamsisn't typed - Add
json_restrictororoutput=mdto cut tokens, andmode: compacton the MCP - A 429 means either the hourly limit or an empty balance. Check the account before retrying
- Repeat a search within the hour and the cached copy is free. Set
no_cache=trueonly when freshness matters
Questions
Which is better for AI agents, SearchAPI.io or SerpApi?
SerpApi scores 65.3 (B) on agent readiness against SearchAPI.io's 52 (D), and leads in 5 of 7 scored categories. SearchAPI.io leads on reliability.
Which is cheaper for web search, SearchAPI.io or SerpApi?
SearchAPI.io, at $4 per 1,000 requests against $25 per 1,000 requests for SerpApi. These are the vendors' published prices for the job.
Do SearchAPI.io and SerpApi need an API key?
SearchAPI.io takes an API key or an OAuth sign-in. SerpApi needs an API key.
Can an agent call SearchAPI.io and SerpApi without installing anything?
Yes. SearchAPI.io has a hosted endpoint at https://www.searchapi.io/api/v1/search and SerpApi at https://serpapi.com/search.
Other comparisons with SearchAPI.io or SerpApi
- Web Search Tool on Amazon Bedrock AgentCore vs SearchAPI.io
- Web Search Tool on Amazon Bedrock AgentCore vs SerpApi
- Arcmira vs SearchAPI.io
- Arcmira vs SerpApi
- Grounding with Bing Search vs SearchAPI.io
- Grounding with Bing Search vs SerpApi
- Brave Search API + MCP vs SearchAPI.io
- Brave Search API + MCP vs SerpApi
- Cloudflare Web Search API vs SearchAPI.io
- Cloudflare Web Search API vs SerpApi
- DeepSeek Search and Fetch API vs SearchAPI.io
- DeepSeek Search and Fetch API vs SerpApi
- Exa API + MCP vs SearchAPI.io
- Exa API + MCP vs SerpApi
- Firecrawl MCP vs SearchAPI.io
- Firecrawl MCP vs SerpApi
- Grep AI vs SearchAPI.io
- Grep AI vs SerpApi
- Hyperresearch vs SearchAPI.io
- Hyperresearch vs SerpApi
- Kagi Search API vs SearchAPI.io
- Kagi Search API vs SerpApi
- Linkup vs SearchAPI.io
- Linkup vs SerpApi
- Mojeek Web Search API vs SearchAPI.io
- Mojeek Web Search API vs SerpApi
- Parallel Search and Task APIs vs SearchAPI.io
- Parallel Search and Task APIs vs SerpApi
- Perplexity Search API vs SearchAPI.io
- Perplexity Search API vs SerpApi
- SearchAPI.io vs Serper
- SearchAPI.io vs SERPHouse
- SearchAPI.io vs SerpKite
- SearchAPI.io vs SpecStream
- SearchAPI.io vs Tavily API + MCP
- SearchAPI.io vs TinyFish Search
- SearchAPI.io vs Valyu
- SearchAPI.io vs You.com APIs
- SerpApi vs Serper
- SerpApi vs SERPHouse
- SerpApi vs SerpKite
- SerpApi vs SpecStream
- SerpApi vs Tavily API + MCP
- SerpApi vs TinyFish Search
- SerpApi vs Valyu
- SerpApi vs You.com APIs
- NewsCatcher vs SearchAPI.io
- NewsCatcher vs SerpApi
- Liner Search MCP vs SearchAPI.io
- Liner Search MCP vs SerpApi
Machine-readable
- This page as Markdown
/compare/searchapi-io-vs-serpapi.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/searchapi-io.json·/api/v1/tools/serpapi.json - From a terminal
anchor compare searchapi-io serpapi(the CLI) - Over MCP
compare_tools {"a": "searchapi-io", "b": "serpapi"}at/mcp, no key