Head to head · Research search · October 2026 research run
Hyperresearch vs Tavily API + MCP
Tavily API + MCP scores 79.5 (A) on agent readiness against Hyperresearch's 68.1 (B), and leads in 3 of 7 scored categories. Hyperresearch leads on security & auth and transparency & trust. Both do research 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
- Security & auth, 79 against 52
- Transparency & trust, 71 against 62
Watch for
No status page, and the terms say there is no SLA and no uptime figure
Best for An agent that needs search plus page text in one call and has no account yet.
Ahead on
- Reliability, 90 against 35
- Schema & documentation, 90 against 76
- Payments & pricing, 94 against 60
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Open source
Watch for
x402 covers advanced search only, not extract, map, crawl or research
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 Tavily API + MCP +55
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.
Tavily API + MCP 90
incident.io status page at status.tavily.com with separate API, MCP and website components (20). One incident in the 90 days from 3 August, website degraded performance on 17 September 2026, and none since per the status feed re-read on 1 November. The API and MCP showed 100% per the 1 October check (30). Published limits, re-read on 1 November, 100 requests a minute on development keys and 1,000 on production, crawl 100 and research 20 task creations on both (15). 429 carries Retry-After and the docs say to use that value and the status code rather than parse the message. Since October a 434 tells non-paying plans that live fetching with max_age_hours is refused under load, with the advice to retry or omit it (15). The pricing page lists 'Enterprise-grade support and SLAs' for the custom Enterprise plan but publishes no SLA terms, per the 17 October check, and none were found in the docs index or terms (0). GA (10).
Payments & pricing Tavily API + MCP +34
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.
Tavily API + MCP 94
Official x402 at x402.tavily.com sells advanced search only, $0.01 in USDC on Base. An unpaid POST to /search returned 402 on 1 November with an x402 version 2 envelope offering the exact scheme on eip155:8453 for 10000 units (0.01 USDC), and a second agent-pay option on aws:base for 0.016, described as advanced mode. Extract, map, crawl and research aren't sold over x402 (15). Credit costs per endpoint and $0.008 a credit pay as you go, published without a login and unchanged on 1 November (20). 1,000 free credits a month, no card, re-read on 1 November (20). Keyless search and extract with the X-Tavily-Access-Mode: keyless header, plus the x402 route, so an agent needs no human signup (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 15 of 40 is 3.75 of 10, and the other lines' 60 is 90 at 30 each, so 75 is 94.
Security & auth Hyperresearch +27
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.
Tavily API + MCP 52
Revocable keys, separate development and production keys, and the Logs API filters by key, so several keys per account work. The hosted MCP adds OAuth but maps it to one dashboard key with no scopes (22). The MCP README and docs still lead with ?tavilyApiKey= in the URL on 1 November (minus 10). The five tools in the npm release all read. The GitHub main branch adds tavily_feedback, which posts scores to Tavily, the hosted server's tool list is unknown, and there's no read-only toolset (10). The home page says requests pass through 'security, privacy, and content validation layers that block PII leakage, prompt injection, and malicious sources'. That's a claim with no technical detail in the docs, plus a safe_search flag for adult content, per the 1 October check (7). The Logs API (filter by key and endpoint since August 2026) and include_usage give per-call visibility (13). SOC 2 and ISO 27001 named on the privacy page, per the 4 October check, and the MCP repo patches vulnerable dependencies about monthly (seven updates on 26 October). The trust centre is JavaScript-only for us (per the 1 October check, not re-read on 1 November), www.tavily.com/.well-known/security.txt returned 404 on 1 November, and no bug bounty found (10).
Schema & documentation Tavily API + MCP +14
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.
Tavily API + MCP 90
Public OpenAPI at docs.tavily.com, and typed JSON Schema on every MCP tool (25). llms.txt with Markdown pages and a 'Start here for agents' section, re-read on 1 November (10). Tool descriptions say what each does and when to reach for it, such as search for facts past the model's cutoff, but the npm release doesn't say when not to. A commit of 27 October on the GitHub main branch adds some, such as using the news topic only when the user asks for news and leaving the extract query empty for tables, but it isn't released on npm, so the award stays (14). Enums for search_depth, topic, time_range and include_domains_mode, ranges for max_results (0 to 20 on the API, 5 to 20 in the MCP), chunks_per_source (1 to 3) and max_age_hours (-1 to 720), and caps of 300 included and 150 excluded domains. The feedback tool on the GitHub main branch, not in the npm release, takes free-form value fields (13). Error table with examples for 400, 401, 422, 429, 432, 433, 434 and 500, re-read on 1 November (15). Versioned SDKs and a monthly changelog, which on 1 November has an October 2026 section documenting max_age_hours (accepted values and the 434 flex tier) and Tavily CLI plain output, and the search API reference now documents max_age_hours. fetch_timeout appears only in the 434 example message and cache_fallback nowhere in the reference or changelog, and the API path isn't versioned (13).
Transparency & trust Hyperresearch +9
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.
Tavily API + MCP 62
MCP server MIT and SDKs open, API closed under platform terms (18). The privacy policy (last updated 24 November 2025, re-read on 1 November) keeps data for the life of the account with no fixed periods, says query data may be used to improve future responses unless a contract says otherwise, and describes no zero-retention option. No DPA on the privacy page, and the trust centre didn't render for us (per the 1 October check, not re-read on 1 November) (15). No deprecation policy or dated deprecation notices found, and none in the changelog on 1 November (0). Names Stripe, Google Analytics, Google Tag Manager, PostHog and third-party search index providers such as Google, with US processing under Standard Contractual Clauses (14).
Score by category
| Category | Weight | Hyperresearch | Tavily API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 90 | Tavily API + MCP +55 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 90 | Tavily API + MCP +14 |
| Agent ergonomics | 13% | 83 | 81 | Hyperresearch +2 |
| Security & auth | 14% | 79 | 52 | Hyperresearch +27 |
| Payments & pricing | 10% | 60 | 94 | Tavily API + MCP +34 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 85 | Hyperresearch +3 |
| Transparency & trust | 7% | 71 | 62 | Hyperresearch +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.1/100 | A 79.5/100 |
Facts side by side
| Fact | Hyperresearch | Tavily API + MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Hyperresearch | Tavily |
| Hosted endpoint | https://answers.hyperresearch.ai/mcp | https://mcp.tavily.com/mcp/ |
| Transports | Streamable HTTP | stdio, Streamable HTTP, HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for research search | $9 per transaction | not published |
| x402 | no | on some endpoints, from $0.01/call |
| Licence | none | MIT |
| Tools exposed | none | 5 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | ai.hyperresearch/answers | io.github.tavily-ai/tavily-mcp |
| Last release | 2026-11-16 | 2026-10-06 |
| Terms last updated | 2026-11-17 | 2026-05-04 |
| Privacy policy last updated | 2026-11-17 | 2025-11-24 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 2.4k stars, 452k npm/wk, 1.6M PyPI/wk |
| Agent reviews | none | 3.6/5 (8) |
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.
Tavily API + MCP
Keyless search and extract, plus a free 1,000 credits a month with no card. x402 covers advanced search only, not extract, map, crawl or research, and the npm MCP release has trailed the GitHub source since August.
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
Tavily API + MCP
- Try
X-Tavily-Access-Mode: keylessfirst for search and extract. Over MCP, the keyless cap arrives as plain text withoutisError, so read the text before treating it as results - Send the key in
Authorization: Bearer, not?tavilyApiKey=in the MCP URL - On 429, wait for
Retry-After. A 432 or 433 means a spend limit, and retrying won't help. A 434 on a free plan means retry shortly or dropmax_age_hours - Run /map before /crawl to bound the crawl, since crawl is billed as map plus extract
- Research is async and runs 4 to 250 credits. Create the task, then poll /research/{request_id}
Questions
Which is better for AI agents, Hyperresearch or Tavily API + MCP?
Tavily API + MCP scores 79.5 (A) on agent readiness against Hyperresearch's 68.1 (B), and leads in 3 of 7 scored categories. Hyperresearch leads on security & auth and transparency & trust.
Do Hyperresearch and Tavily API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Hyperresearch and Tavily API + MCP without installing anything?
Yes. Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp and Tavily API + MCP at https://mcp.tavily.com/mcp/.
Are Hyperresearch and Tavily API + MCP open source?
No open-source release is listed for Hyperresearch. Tavily API + MCP is open source (MIT).
Other comparisons with Hyperresearch or Tavily API + MCP
- Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch
- Web Search Tool on Amazon Bedrock AgentCore vs Tavily API + MCP
- Grounding with Bing Search vs Hyperresearch
- Grounding with Bing Search vs Tavily API + MCP
- Brave Search API + MCP vs Hyperresearch
- Brave Search API + MCP vs Tavily API + MCP
- Cloudflare Web Search API vs Hyperresearch
- Cloudflare Web Search API vs Tavily API + MCP
- DeepSeek Search and Fetch API vs Hyperresearch
- DeepSeek Search and Fetch API vs Tavily API + MCP
- Exa API + MCP vs Hyperresearch
- Exa API + MCP vs Tavily API + MCP
- Firecrawl MCP vs Hyperresearch
- Firecrawl MCP vs Tavily API + MCP
- 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
- Kagi Search API vs Tavily API + MCP
- Linkup vs Tavily API + MCP
- Mojeek Web Search API vs Tavily API + MCP
- Parallel Search and Task APIs vs Tavily API + MCP
- Perplexity Search API vs Tavily API + MCP
- SearchAPI.io vs Tavily API + MCP
- SerpApi vs Tavily API + MCP
- Serper vs Tavily API + MCP
- SERPHouse vs Tavily API + MCP
- SerpKite vs Tavily API + MCP
- Tavily API + MCP vs TinyFish Search
- Tavily API + MCP vs Valyu
- Tavily API + MCP vs You.com APIs
- Arcmira vs Hyperresearch
- Arcmira vs Tavily API + MCP
- Grep AI vs Hyperresearch
- Grep AI vs Tavily API + MCP
- 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 TinyFish Search
- Hyperresearch vs Valyu
- Hyperresearch vs You.com APIs
- Liner Search MCP vs Tavily API + MCP
- SpecStream vs Tavily API + MCP
- Fetch (MCP reference server) vs Hyperresearch
- Fetch (MCP reference server) vs Tavily API + MCP
- NewsCatcher vs Tavily API + MCP
Machine-readable
- This page as Markdown
/compare/hyperresearch-vs-tavily-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hyperresearch.json·/api/v1/tools/tavily-mcp.json - From a terminal
anchor compare hyperresearch tavily-mcp(the CLI) - Over MCP
compare_tools {"a": "hyperresearch", "b": "tavily-mcp"}at/mcp, no key