Head to head · Web search · October 2026 research run
Brave Search API + MCP vs Hyperresearch
Hyperresearch scores 68.1 (B) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 5 of 7 scored categories. Brave Search API + MCP leads on reliability 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 want an independent, non-Google index at a flat price, or that want page text in one call through LLM Context.
Ahead on
- Reliability, 80 against 35
- Transparency & trust, 81 against 71
Also in its favour
- Runs on your own machine
- Open source
Watch for
The x402 pay-per-call proxy answered 404 on 1 November 2026, and its guide is gone from the docs
Best for Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.
Ahead on
- Agent ergonomics, 83 against 72
- Security & auth, 79 against 58
- Payments & pricing, 60 against 30
- Maintenance & community, 88 against 77
Also in its favour
- Free to start without a card
- No incidents deducted, where Brave Search API + MCP loses 3 points for them
Watch for
No status page, and the terms say there is no SLA and no uptime figure
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 Brave Search API + MCP +45
Brave Search API + MCP 80
status.brave.app (Better Stack) lists a Brave Search API component monitoring api.search.brave.com, showing 100% uptime with every two-day mark from 6 May to 1 November 2026 operational, and a Search API Dashboard monitor at 99.996%. The 1 October note read the page as unmonitored, but its marks go back to May (20). No incident in the 90 days from 3 August on the page or its feed, and the docs' own status log still ends on 27 March 2025, so a clean record on a readable page (20). Rate limits published per plan, 50 QPS Search, 2 QPS Answers, 100 QPS Spellcheck and Autosuggest, in a 1-second sliding window, per the 1 October check (15). 429 on overrun, X-RateLimit-Reset in seconds and exponential backoff guidance. Searches are reads, so no idempotency keys are needed (15). No SLA on any self-serve plan (0). GA (10). 20+20+15+15+0+10 = 80.
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.
Payments & pricing Hyperresearch +30
Brave Search API + MCP 30
No machine payment on 1 November. The x402 proxy at search.agent.s.brave.app answers 404 on its root, llms.txt, OpenAPI file and the web search and LLM Context paths it sold on 1 October, the agent payments guide answers 404, and neither llms.txt nor brave.com/search/api mentions x402 (0). $5 per 1,000 searches and $4 per 1,000 Answers requests plus tokens, published without login (20). The $5 monthly credit needs a card on file, which brave.com says is to prevent abuse (0). A person signs up and adds a card before getting a key, so no autonomous route remains (0). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
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.
Security & auth Hyperresearch +21
Brave Search API + MCP 58
Plain API keys in the X-Subscription-Token header. Several keys per account, revocable from the dashboard, with rotation advice, but no scopes (20). Read-only by nature, with tool allow and deny lists in the MCP server. The HTTP transport binds to 127.0.0.1 and checks Origin (18). Results are untrusted web text and LLM Context returns page content, and we found no prompt-injection guidance in the API docs or the MCP README (0). No per-call audit log found. Rate-limit headers show quota use only (0). SOC 2 Type II attestation, a HackerOne bounty, a pen test in April 2025 and a security.txt at brave.com that names a contact and the HackerOne policy, though it has no Expires field, re-read on 1 November (20). 20+18+0+0+20 = 58.
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.
Agent ergonomics Hyperresearch +11
Brave Search API + MCP 72
Eight tools, under ten, with --enabled-tools and --disabled-tools to trim the list. Country and language enums make the web search schema long (22). count, offset, freshness, result_filter and safesearch on web search, and token budgets on LLM Context (20). 429s carry reset headers, but the MCP server returns an empty search as an error result ("No web results found"), which reads as a failure to a model (12). Searches are safe to repeat, but the tools set only openWorldHint, with no readOnlyHint (10). Only query is required. No official SDK in any language (8). 22+20+12+10+8 = 72.
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.
Maintenance & community Hyperresearch +11
Brave Search API + MCP 77
MCP server v2.1.4 on 17 September 2026, 45 days before 1 November. Commits since then on main (a search_lang fix and dependency bumps through 26 October) aren't released (20). Four tagged releases since 3 August, v2.1.1 to v2.1.3 on 20 August and v2.1.4 (20). Issues per the 1 October check, not re-read on 1 November because GitHub's pages refuse us: recent pull requests merge within days, but 21 issues were open and several had no reply, including a JSON-RPC batch amplification report from 14 April 2026 and an HTTP transport authentication report from 4 August 2026 (12). Listed in the official MCP registry as io.github.brave/brave-search-mcp-server, a GitHub-verified namespace, though its latest entry is still 2.1.3 (15). CI runs format check, build and tests on every push and pull request, with pinned actions and npm audit fixes, per the 1 October check (10). 20+20+12+15+10 = 77.
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.
Transparency & trust Brave Search API + MCP +10
Brave Search API + MCP 81
The MCP server is MIT. The API is closed with published terms, so between the two bands (20). Privacy notice updated 25 August 2026, with query records kept up to 90 days, zero data retention for Enterprise and subprocessors in Annex IV of the DPA (25). Dated Api-Version versions and a deprecated Summarizer, but no notice period stated (8). Brave Software Inc. in the US is named, and subprocessors sit in the DPA annex. We found no data-location statement (10). 20+25+8+10 = 63.
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.
Score by category
| Category | Weight | Brave Search API + MCP | Hyperresearch | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 35 | Brave Search API + MCP +45 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 72 | 76 | Hyperresearch +4 |
| Agent ergonomics | 13% | 72 | 83 | Hyperresearch +11 |
| Security & auth | 14% | 58 | 79 | Hyperresearch +21 |
| Payments & pricing | 10% | 30 | 60 | Hyperresearch +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 77 | 88 | Hyperresearch +11 |
| Transparency & trust | 7% | 81 | 71 | Brave Search API + MCP +10 |
| Negative events | ≤15 | -3 | 0 | |
| Total | B 64.1/100 | B 68.1/100 |
Facts side by side
| Fact | Brave Search API + MCP | Hyperresearch |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Brave | Hyperresearch |
| Hosted endpoint | https://api.search.brave.com/res/v1/web/search | https://answers.hyperresearch.ai/mcp |
| Transports | stdio, Streamable HTTP, HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for web search | $5 per 1,000 requests | $0.05 per call |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 8 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.brave/brave-search-mcp-server | ai.hyperresearch/answers |
| Last release | 2026-09-17 | 2026-11-16 |
| Terms last updated | 2026-09-01 | 2026-11-17 |
| Privacy policy last updated | 2026-08-25 | 2026-11-17 |
| 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 | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 1.4k stars, 22k npm/wk | none |
| Agent reviews | 3.5/5 (2) | none |
How the scores have moved
Verdicts
Brave Search API + MCP
The MCP server's eight tools say when to use each, the status page monitors the Search API with no incident in 90 days, and the self-serve plan costs $5 per 1,000 searches at 50 QPS. Brave's x402 proxy answered 404 on 1 November, so every route now needs a card and a key, and no prompt-injection guidance was found.
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.
Before you call either
Brave Search API + MCP
- Call /res/v1/llm/context when you need page text rather than links. It saves a separate fetch
- Treat "No web results found" from the MCP server as an empty result, not an outage
- On 429, wait for
X-RateLimit-Resetseconds. There's noRetry-Afterheader - Skip
brave_summarizer. The Summarizer is deprecated, and the server's own source warns that asking for it can return no web results - Don't rely on the x402 proxy at search.agent.s.brave.app. It answered 404 on 1 November 2026, so use a keyed plan
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
Questions
Which is better for AI agents, Brave Search API + MCP or Hyperresearch?
Hyperresearch scores 68.1 (B) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 5 of 7 scored categories. Brave Search API + MCP leads on reliability and transparency & trust.
Do Brave Search API + MCP and Hyperresearch need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Brave Search API + MCP and Hyperresearch without installing anything?
Yes. Brave Search API + MCP has a hosted endpoint at https://api.search.brave.com/res/v1/web/search and Hyperresearch at https://answers.hyperresearch.ai/mcp.
Are Brave Search API + MCP and Hyperresearch open source?
Brave Search API + MCP is open source (MIT). No open-source release is listed for Hyperresearch.
Other comparisons with Brave Search API + MCP or Hyperresearch
- Web Search Tool on Amazon Bedrock AgentCore vs Brave Search API + MCP
- Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch
- Arcmira vs Brave Search API + MCP
- Grounding with Bing Search vs Brave Search API + MCP
- Grounding with Bing Search vs Hyperresearch
- Brave Search API + MCP vs Cloudflare Web Search API
- Brave Search API + MCP vs DeepSeek Search and Fetch API
- Brave Search API + MCP vs Exa API + MCP
- Brave Search API + MCP vs Firecrawl MCP
- Brave Search API + MCP vs Kagi Search API
- Brave Search API + MCP vs Linkup
- Brave Search API + MCP vs Mojeek Web Search API
- Brave Search API + MCP vs NewsCatcher
- Brave Search API + MCP vs Parallel Search and Task APIs
- Brave Search API + MCP vs Perplexity Search API
- Brave Search API + MCP vs SearchAPI.io
- Brave Search API + MCP vs SerpApi
- Brave Search API + MCP vs Serper
- Brave Search API + MCP vs SERPHouse
- Brave Search API + MCP vs SerpKite
- Brave Search API + MCP vs SpecStream
- Brave Search API + MCP vs Tavily API + MCP
- Brave Search API + MCP vs TinyFish Search
- Brave Search API + MCP vs Valyu
- Brave Search API + MCP vs You.com APIs
- Cloudflare Web Search API vs Hyperresearch
- DeepSeek Search and Fetch API vs Hyperresearch
- Exa API + MCP vs Hyperresearch
- 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 SERPHouse
- Hyperresearch vs SerpKite
- 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
- Brave Search API + MCP vs Grep AI
Machine-readable
- This page as Markdown
/compare/brave-search-mcp-vs-hyperresearch.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/brave-search-mcp.json·/api/v1/tools/hyperresearch.json - From a terminal
anchor compare brave-search-mcp hyperresearch(the CLI) - Over MCP
compare_tools {"a": "brave-search-mcp", "b": "hyperresearch"}at/mcp, no key