Head to head · Web search · October 2026 research run
Hyperresearch vs SerpApi
Hyperresearch scores 68.1 (B) on agent readiness against SerpApi's 65.3 (B), and leads in 4 of 7 scored categories. SerpApi leads on reliability, agent ergonomics and transparency & trust. Both do web search.
Best web search APIs for AI agents · All 353 search comparisons
Which one, for what
Best for Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.
Ahead on
- Schema & documentation, 76 against 67
- Security & auth, 79 against 40
- Payments & pricing, 60 against 45
- Maintenance & community, 88 against 82
Also in its favour
- Free to start without a card
Watch for
No status page, and the terms say there is no SLA and no uptime figure
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
- Reliability, 65 against 35
- Agent ergonomics, 88 against 83
- Transparency & trust, 84 against 71
Also in its favour
- Runs on your own machine
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.
Security & auth Hyperresearch +39
Hyperresearch 79
Bearer keys of 32 random bytes stored as salted hashes, shown once, scoped to runs:read, runs:write, vault:read, vault:write, verify, mcp and admin, with a last-used time, rotation with a 24-hour overlap and instant revocation, plus an IP allowlist. MCP uses OAuth with PKCE and a consent screen that lists each scope. The docs say never to put keys in URLs (30). A client that requests no scopes gets read-only access, billed scopes are marked on the consent screen, and every workspace has a spend cap. No confirmation step for deletes was found (16 of 20). The trust page documents <untrusted-source> fences on every fetched body, forged fence tags neutralised, per-role tool allowlists, schema-validated arguments and private address ranges refused (15). A workspace audit log exportable as NDJSON, a 365-day default window, and a list of agent connections that can be revoked (15). No security.txt (404), no formal disclosure policy and no bug bounty, and the trust page says there is no SOC 2 report. Vulnerabilities go to support@hyperresearch.ai (3 of 20). 30+16+15+15+3 = 79.
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).
Reliability SerpApi +30
Hyperresearch 35
Graded on the hosted API and the two remote MCP servers. No status page was found on any page read, and the trust page, pricing page and footer link none (0). No readable incident history (5). Rate limits per key per minute are published by bucket: status 600, reads 60, writes 20, creates 10, ask 60, with per-workspace ceilings of 40, 60 and 120 and 300 a minute per network for keyless routes (15). 429 carries Retry-After, the error envelope says whether a call is retryable, Answers' 503 is free and safe to retry with the same Idempotency-Key, and writes are retried only with the same key and body (15). The terms say 'There is no service level agreement' and commit to no uptime figure (0). The terms call the service 'a beta from a young company' (0). 0+5+15+15+0+0 = 35.
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.
Payments & pricing Hyperresearch +15
Hyperresearch 60
No x402, MPP or L402 (0). Per-call prices for Answers and flat per-run prices (Light $9, Deep $49) are published without login, with rerun discounts and refund rules (30). $5 of Answers credit and the first Light report free on every account, no card needed, and hr_test_ keys are never billed (30). A person signs up through Clerk in a browser and creates keys in the console, and MCP clients authorise in a browser (0). 0+30+30+0 = 60.
SerpApi 45
No x402, MPP or L402 on the pricing page or llms.txt (0). Monthly plans are public with search counts, but there's no pay-per-search option (10). Free plan of 250 searches a month, no card (20). An account needs a browser signup (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Transparency & trust SerpApi +13
Hyperresearch 71
The hosted service is closed with terms from Thalient Labs Inc. (version 1.7), and the CLI that runs the same pipeline is MIT (20 of 30). The trust page states retention per record type (content kept until deleted, verification inputs 7 days, billing at least 7 years, audit log 365 days by default), names the known gaps (the run index and questions are kept indefinitely, no automatic expiry), says customer content isn't used for training, and says it matches the privacy policy. No DPA on the shelf (26 of 30). A written deprecation policy: at least six months' notice, Deprecation and Sunset headers and a list of deprecations, plus 30 days' notice by email before a shutdown (20). Subprocessors are listed with what each receives and their countries, and the trust page says there is no data residency guarantee on Cloudflare's network (18 of 20). 20+26+20+18 = 84.
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).
Schema & documentation Hyperresearch +9
Hyperresearch 76
llms.txt and the versioning page name an OpenAPI 3.1 document at api.hyperresearch.ai/v1/openapi.json, and the API reference has one page per operation generated from it. api.hyperresearch.ai's robots.txt asked for a sign-in, so read.py closed the host and the file wasn't read (20 of 25). llms.txt, and every docs page as Markdown with .md (10). The Answers page says when to use fast, standard, max or auto and that fast skips structured sources, and the docs say Answers is for one fact and runs for a report. The research MCP server's tool descriptions couldn't be read (12 of 20). Modes and run tiers are enums, and examples show max_results, but the schemas themselves weren't read (10 of 15). Request and result examples, one error envelope with status meanings and a stable code (14 of 15). The version is in the path (/v1) with an additive-only promise, but the hosted service has no public changelog. The open-source CLI's CHANGELOG.md is dated (10 of 15). 20+10+12+10+14+10 = 76.
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).
Maintenance & community Hyperresearch +6
Hyperresearch 88
The pricing and about pages were updated on 17 November 2026, and the open-source CLI that the hosted service runs was tagged v0.13.3 on 16 November (30). Four tagged CLI releases in the 90 days to this check: v0.13.0 (27 October), v0.13.1 (9 November), v0.13.2 (12 November), v0.13.3 (16 November) (20). The CLI changelog credits fixes to issues and pull requests from outside contributors (#71, #201 to #206). We didn't read the issue threads (15 of 25). ai.hyperresearch/hyperresearch and ai.hyperresearch/answers are in the official MCP registry under the vendor's domain namespace (15). The repository has CI and publish workflows, and AI SDK and LangChain packages are published (8 of 10). 30+20+15+15+8 = 88.
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).
Score by category
| Category | Weight | Hyperresearch | SerpApi | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 65 | SerpApi +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 67 | Hyperresearch +9 |
| Agent ergonomics | 13% | 83 | 88 | SerpApi +5 |
| Security & auth | 14% | 79 | 40 | Hyperresearch +39 |
| Payments & pricing | 10% | 60 | 45 | Hyperresearch +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 82 | Hyperresearch +6 |
| Transparency & trust | 7% | 71 | 84 | SerpApi +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.1/100 | B 65.3/100 |
Facts side by side
| Fact | Hyperresearch | SerpApi |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Hyperresearch | SerpApi |
| Hosted endpoint | https://answers.hyperresearch.ai/mcp | https://serpapi.com/search |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Freemium |
| Price for web search | $0.05 per call | $25 per 1,000 requests |
| x402 | no | no |
| Tools exposed | none | 3 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | ai.hyperresearch/answers | io.github.serpapi/serpapi-mcp |
| Last release | 2026-11-16 | 2026-10-30 |
| Terms last updated | 2026-11-17 | 2026-08-27 |
| Privacy policy last updated | 2026-11-17 | 2026-08-27 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | 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 | none | 3.5/5 (2) |
How the scores have moved
Hyperresearch
No score change since it was listed.
Verdicts
Hyperresearch
Agents can buy one checked answer from 2 cents a call or a full research report for $9 or $49, with scoped, rotatable keys, stable error codes, idempotency keys and a six-month deprecation promise. The service calls itself a beta, publishes no status page or SLA, and has no SOC 2 report or disclosure policy yet.
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
Hyperresearch
- Use Answers (
data_and_web_answerwith modeauto) for one fact, and start a Light or Deep run only when the user wants a written report - Send an
Idempotency-Keyon every write and reuse it only with an unchanged body, so a retried run or answer is charged once - Poll a run with
GET /v1/runs/{id}about once a minute, or stream its events. A Light run takes about 30 to 40 minutes - If a response has
retryable: false, change the request rather than retrying. Branch onerror.code, never on the message - Use a key that starts
hr_test_to build and test an integration without spending
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, Hyperresearch or SerpApi?
Hyperresearch scores 68.1 (B) on agent readiness against SerpApi's 65.3 (B), and leads in 4 of 7 scored categories. SerpApi leads on reliability, agent ergonomics and transparency & trust.
Do Hyperresearch and SerpApi need an API key?
Hyperresearch takes an API key or an OAuth sign-in. SerpApi needs an API key.
Can an agent call Hyperresearch and SerpApi without installing anything?
Yes. Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp and SerpApi at https://serpapi.com/search.
Other comparisons with Hyperresearch or SerpApi
- Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch
- Web Search Tool on Amazon Bedrock AgentCore vs SerpApi
- Arcmira vs SerpApi
- Grounding with Bing Search vs Hyperresearch
- Grounding with Bing Search vs SerpApi
- Brave Search API + MCP vs Hyperresearch
- Brave Search API + MCP vs SerpApi
- Cloudflare Web Search API vs Hyperresearch
- Cloudflare Web Search API vs SerpApi
- DeepSeek Search and Fetch API vs Hyperresearch
- DeepSeek Search and Fetch API vs SerpApi
- Exa API + MCP vs Hyperresearch
- Exa API + MCP vs SerpApi
- Firecrawl MCP vs Hyperresearch
- Firecrawl MCP vs SerpApi
- Grep AI vs SerpApi
- Hyperresearch vs Kagi Search API
- Hyperresearch vs Mojeek Web Search API
- Hyperresearch vs SearchAPI.io
- Hyperresearch vs Serper
- Hyperresearch vs SERPHouse
- Hyperresearch vs SerpKite
- Kagi Search API vs SerpApi
- Linkup vs SerpApi
- Mojeek Web Search API vs SerpApi
- Parallel Search and Task APIs vs SerpApi
- Perplexity Search API vs SerpApi
- SearchAPI.io vs SerpApi
- 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
- Arcmira vs Hyperresearch
- Grep AI vs Hyperresearch
- Hyperresearch vs Liner Search MCP
- Hyperresearch vs Linkup
- Hyperresearch vs NewsCatcher
- Hyperresearch vs Parallel Search and Task APIs
- Hyperresearch vs Perplexity Search API
- Hyperresearch vs SpecStream
- Hyperresearch vs Tavily API + MCP
- Hyperresearch vs TinyFish Search
- Hyperresearch vs Valyu
- Hyperresearch vs You.com APIs
- Fetch (MCP reference server) vs Hyperresearch
- NewsCatcher vs SerpApi
- Liner Search MCP vs SerpApi
Machine-readable
- This page as Markdown
/compare/hyperresearch-vs-serpapi.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hyperresearch.json·/api/v1/tools/serpapi.json - From a terminal
anchor compare hyperresearch serpapi(the CLI) - Over MCP
compare_tools {"a": "hyperresearch", "b": "serpapi"}at/mcp, no key