Head to head · Web search · October 2026 research run
Hyperresearch vs SERPHouse
Hyperresearch scores 68.1 (B) on agent readiness against SERPHouse's 44.9 (E), and leads in 5 of 7 scored categories. SERPHouse leads on reliability. 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 66
- Agent ergonomics, 83 against 64
- Security & auth, 79 against 11
- Maintenance & community, 88 against 23
- Transparency & trust, 71 against 50
Watch for
No status page, and the terms say there is no SLA and no uptime figure
Best for Low-cost Google, Bing and Yahoo result parsing for SEO and rank tracking, with many Google verticals.
Ahead on
- Reliability, 40 against 35
Also in its favour
- Runs on your own machine
Watch for
The hosted MCP server takes the API key only in its URL path, and the REST API also accepts api_token in the query string
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 +68
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.
SERPHouse 11
One key per account, one account per user, no scopes or rotation found (10). The REST API documents api_token in the query string and the hosted MCP server takes the key only in its URL path, less 10 (0 of 30). Searches only read, with no read-only or restricted key (8 of 20). Results are third-party snippets and AI Overview text, with no prompt-injection guidance (0). An account tool shows plan and credit usage; no per-call log was found (3 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0 of 20). 0 + 8 + 0 + 3 + 0 = 11.
Maintenance & community Hyperresearch +65
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.
SERPHouse 23
Read for a closed service, with its repositories read as code. No changelog or dated API change was found. The newest release is MCP server 1.1.0 on 6 July 2026, 123 days before 6 November, and the last commit in its repository was on 22 July (10). No release or dated change in the 90 days from 8 August; the about page's 2026 entry (Forums, Place Details and Scraper APIs) is undated (0). No changelog; support by email. Issues weren't read, since the GitHub API refused us for its rate limit (5 of 25). Not in the official MCP registry, though the repository's server.json names io.github.SERPHouse/serphouse-mcp. Node.js SDK last changed 24 June 2026, PHP SDK 10 May 2024, and no Python SDK repository was found under the SERPHouse organisation (5 of 15). The MCP repository has an npm publish workflow and no tests (3 of 10). 10 + 0 + 5 + 5 + 3 = 23.
Transparency & trust Hyperresearch +21
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.
SERPHouse 50
Closed service under terms naming Patoliya Infotech LLP in India, and the MCP server is MIT (18 of 30). The terms give retention periods (JSON results up to 6 months, HTML up to 1 month, search history indefinitely) and say personal data sits on DigitalOcean in India, and they advise EEA users not to use the service. The privacy policy is generic and neither document carries a date (15 of 30). No deprecation policy, and the terms allow products to be discontinued without notice (0 of 20). DigitalOcean in India named for account data; no sub-processor list (6 of 20). 18 + 15 + 0 + 6 = 39.
Agent ergonomics Hyperresearch +19
Hyperresearch 83
Answers is three compact tools (data_and_web_answer, data_and_web_search and the free get_pending_answer), and an answer returns only a short answer, its quotes and links. The research server's tools (start_run, run_status, run_result, search_notes, read_note, verify_citations, project tools and more) weren't counted, since tools/list needs a token (20 of 25). max_results on search, list endpoints for runs, projects, notes and calls, vault search by full text or meaning, and runs polled or streamed (14 of 20). Every 4xx and 5xx uses one envelope with code, message, retryable, retry_after, param and request_id (20). Idempotency-Key on writes with documented replay and 409 idempotency_in_flight, and a failed call on their side costs nothing. MCP tool annotations weren't readable (14 of 20). Only a query and a tier are required to start a run. Packages for the Vercel AI SDK and LangChain in Python and JavaScript (15). 20+14+20+14+15 = 83.
SERPHouse 64
23 MCP tools with no toolsets or filtering (15 of 25). num_result, max_pages, paging, device, location, language, date and video filters (16 of 20). Status codes are tabulated, but a 200 can also mean an error and the body carries only 'Please try again' (10 of 20). Searches only read and failed requests aren't charged, but the MCP tools carry no readOnlyHint or other annotations (10 of 20). serphouse_search needs only q and defaults to the US; most other tools need loc or loc_id. Official Node.js, PHP and Python SDKs are documented (13 of 15). 15 + 16 + 10 + 10 + 13 = 64.
Schema & documentation Hyperresearch +10
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.
SERPHouse 66
No OpenAPI or similar contract for the REST API. The MCP server's tools carry typed Zod schemas, published in the source and a static server card (18 of 25). llms.txt at the site and the docs, and every docs page as Markdown (10). MCP tool descriptions say which tool to use for what, such as serphouse_google_web when device or num_result is needed, while the docs pages lead with marketing lines such as 'Unlock captivating Google video content' (12 of 20). Enums for device, SERP type, engine and video duration, defaults and 37 described parameters (11 of 15). A status code table and request examples per engine, with a generic error body (12 of 15). No changelog or API versioning; only the MCP server has tags (3 of 15). 18 + 10 + 12 + 11 + 12 + 3 = 66.
Reliability SERPHouse +5
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.
SERPHouse 40
Read with the hosted lines. No status page is linked from the site or docs, and status.serphouse.com did not answer on 6 November 2026 (0). No readable incident history (5). Rate limits published, 60 requests a minute and 60 concurrent on every self-serve plan (15). 429 is documented as 'slow down', and a 200 can carry "status": "error" with 'Please try again', with no Retry-After or backoff guidance. Failed requests aren't charged (5 of 15). The pricing page lists a 99.99% uptime SLA on Basic and Regular and the docs a 99.95% one, but no SLA terms or credits were found in the terms (5 of 10). Generally available (10). 0 + 5 + 15 + 5 + 5 + 10 = 40.
Score by category
| Category | Weight | Hyperresearch | SERPHouse | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 40 | SERPHouse +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 66 | Hyperresearch +10 |
| Agent ergonomics | 13% | 83 | 64 | Hyperresearch +19 |
| Security & auth | 14% | 79 | 11 | Hyperresearch +68 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 23 | Hyperresearch +65 |
| Transparency & trust | 7% | 71 | 50 | Hyperresearch +21 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.1/100 | E 44.9/100 |
Facts side by side
| Fact | Hyperresearch | SERPHouse |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Hyperresearch | Patoliya Infotech LLP |
| Hosted endpoint | https://answers.hyperresearch.ai/mcp | https://mcp.serphouse.com/YOUR_API_KEY/mcp |
| Transports | Streamable HTTP | Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Paid |
| Price for web search | $0.05 per call | not published |
| x402 | no | no |
| Tools exposed | none | 23 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | ai.hyperresearch/answers | not listed |
| Last release | 2026-11-16 | 2026-07-06 |
| Terms last updated | 2026-11-17 | no date given |
| Privacy policy last updated | 2026-11-17 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| 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 |
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.
SERPHouse
SERPHouse returns parsed Google, Bing and Yahoo results at published prices from $0.62 per 1,000 requests, with a 23-tool MCP server and a 4,000-credit trial without a card. The hosted MCP puts the key in its URL, there is no status page, changelog or security contact, and the terms keep search history indefinitely.
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
SERPHouse
- Send the key as
Authorization: Bearer, not asapi_tokenin the URL - Treat a 200 with
"status": "error"and 'Please try again' as a failure and retry later - Pass
locorloc_idfor Google and Bing tools other thanserphouse_search; find IDs withserphouse_location_search - Use
serphouse_searchfor plain lookups andserphouse_serp_google_advancedonly when ranks beyond the top 10 are needed, at ten times the price - Keep under 60 requests a minute on self-serve plans
Questions
Which is better for AI agents, Hyperresearch or SERPHouse?
Hyperresearch scores 68.1 (B) on agent readiness against SERPHouse's 44.9 (E), and leads in 5 of 7 scored categories. SERPHouse leads on reliability.
Do Hyperresearch and SERPHouse need an API key?
Hyperresearch takes an API key or an OAuth sign-in. SERPHouse needs an API key.
Can an agent call Hyperresearch and SERPHouse without installing anything?
Yes. Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp and SERPHouse at https://mcp.serphouse.com/YOUR_API_KEY/mcp.
Other comparisons with Hyperresearch or SERPHouse
- Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch
- Web Search Tool on Amazon Bedrock AgentCore vs SERPHouse
- Grounding with Bing Search vs Hyperresearch
- Grounding with Bing Search vs SERPHouse
- Brave Search API + MCP vs Hyperresearch
- Brave Search API + MCP vs SERPHouse
- Cloudflare Web Search API vs Hyperresearch
- Cloudflare Web Search API vs SERPHouse
- DeepSeek Search and Fetch API vs Hyperresearch
- DeepSeek Search and Fetch API vs SERPHouse
- Exa API + MCP vs Hyperresearch
- Exa API + MCP vs SERPHouse
- Firecrawl MCP vs Hyperresearch
- Hyperresearch vs Kagi Search API
- Hyperresearch vs Mojeek Web Search API
- Hyperresearch vs SearchAPI.io
- Hyperresearch vs SerpApi
- Hyperresearch vs Serper
- Hyperresearch vs SerpKite
- Kagi Search API vs SERPHouse
- Linkup vs SERPHouse
- Mojeek Web Search API vs SERPHouse
- Parallel Search and Task APIs vs SERPHouse
- Perplexity Search API vs SERPHouse
- SearchAPI.io vs SERPHouse
- SerpApi vs SERPHouse
- Serper vs SERPHouse
- SERPHouse vs SpecStream
- SERPHouse vs Tavily API + MCP
- SERPHouse vs TinyFish Search
- SERPHouse vs Valyu
- SERPHouse 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
- Fetch (MCP reference server) vs SERPHouse
- NewsCatcher vs SERPHouse
- Liner Search MCP vs SERPHouse
- SERPHouse vs SerpKite
Machine-readable
- This page as Markdown
/compare/hyperresearch-vs-serphouse.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hyperresearch.json·/api/v1/tools/serphouse.json - From a terminal
anchor compare hyperresearch serphouse(the CLI) - Over MCP
compare_tools {"a": "hyperresearch", "b": "serphouse"}at/mcp, no key