# Hyperresearch vs Valyu

> Valyu scores 72.1 (BB) to Hyperresearch's 68.1 (B) for research search. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/hyperresearch-vs-valyu
- Markdown: https://www.anchorterminal.com/compare/hyperresearch-vs-valyu.md (~5,850 tokens)
- Slim: https://www.anchorterminal.com/compare/hyperresearch-vs-valyu.min.md (~1,130 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/hyperresearch-vs-valyu.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Valyu scores 72.1 (BB) on agent readiness against Hyperresearch's 68.1 (B), and leads in 4 of 7 scored categories. Hyperresearch leads on security & auth and maintenance & community. Both do research search.

- Hyperresearch: grade B, 68.1/100, rank #407 of 1557. Markdown https://www.anchorterminal.com/tools/hyperresearch.md · JSON https://www.anchorterminal.com/api/v1/tools/hyperresearch.json
- Valyu: grade BB, 72.1/100, rank #235 of 1557. Markdown https://www.anchorterminal.com/tools/valyu.md · JSON https://www.anchorterminal.com/api/v1/tools/valyu.json
- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md
- All 353 search comparisons: https://www.anchorterminal.com/compare/search/index.md

## Which one, for what

### Hyperresearch (B)

Good 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 44
- Maintenance & community, 88 against 80

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

### Valyu (BB)

Good for: Research agents that need SEC filings, papers, patents, clinical trials or market data alongside the web, with a per-query price cap.

Ahead on:
- Reliability, 70 against 35
- Schema & documentation, 90 against 76
- Payments & pricing, 68 against 60
- Transparency & trust, 78 against 71

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: Per-plan rate limits are stated only in example responses, not in a table


## Why the edge

### Reliability: Valyu +35

- 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.
- Valyu (70): Instatus page at status.valyu.ai with separate Search, Contents, Answer and DeepResearch components and an RSS history (20). In the 90 days to 2 November it lists a 13-minute Search incident on 6 October with "certain data sources", a partial incident, plus scheduled maintenance on 9 August (Search, 3 hours 13 minutes, announced the evening before) and 20 October (every component, 3 hours, announced 47 minutes ahead). Minor only (20). Since 21 October limits apply per organisation and per endpoint and scale with the plan, but the numbers appear only in example responses (Search at 5 requests a second on pay-as-you-go and 10 on Ridiculously Cheap; DeepResearch at 2 and 5 tasks at once), and the pricing page the docs point to for each plan's rate doesn't list them (8 of 15). A 429 carries a Retry-After header and a body with retry_after, the plan and the limit, the docs say to wait and retry with backoff and that a rate-limited request is never charged, and the SDKs retry 429s on their own. No idempotency keys, but the pricing page says to persist research task ids so retries don't create duplicate tasks (12). No SLA found (0). Search, Contents, Answer and DeepResearch are GA, and Workflows is labelled beta (10). 20+20+8+12+0+10 = 70.

### Security & auth: Hyperresearch +35

- 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.
- Valyu (44): The CLI mints API keys with a hard spending cap and can rotate and revoke them, management keys carry explicit scopes, organisations have MFA, and the hosted MCP has OAuth sign-in (28). The MCP docs lead with `?valyuApiKey=` in the URL (minus 10). Spend-capped keys and `max_price` limit cost exposure, but `valyu_deepresearch_control` deletes tasks with no confirmation we could find (12). Search and Contents return full page text from the open web, and we found no prompt-injection guidance in the docs index (0). No per-call log or audit trail found for the operator (0). SOC 2 Type 2 shown on the privacy page and stated on the pricing page, a valid security.txt (security@valyu.ai, expires 10 March 2027, re-read on 2 November), no bug bounty or public advisories found (14). The MCP docs still give `?valyuApiKey=` for every client on 2 November. 28-10+12+0+0+14 = 44.

### Schema & documentation: Valyu +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.
- Valyu (90): Valid OpenAPI 3.0.3 (info version 2.3.0) with 24 paths and 29 operations across Search, Contents, Answer, DeepResearch, Batches, Workflows and Datasources on 2 November, matching the endpoint pages in llms.txt (25). llms.txt with a 'Guidance for agents' section (10). The MCP tools carry one-line purposes such as 'Read one or more URLs as clean markdown', and the docs explain source presets, but say little about when not to use a tool (13). `search_type` is an enum, `max_num_results` runs 1 to 20, `relevance_threshold` 0 to 1, `source_biases` -5 to 5 and `instructions` caps at 500 characters, with only `query` required (14). 200, 206 partial success and 400 to 503 documented, with examples across the docs (13). Versioned paths (/v1) and two dated changelogs, the platform changelog to 31 October 2026 and the SDK and API changelog to 26 October (15). 25+10+13+14+13+15 = 90.

### Payments & pricing: Valyu +8

- 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.
- Valyu (68): No x402, MPP or L402 in llms.txt, the pricing page or the OpenAPI file on 2 November, so there was no payment route to check live (0). Since October usage is billed in credits, 1,600 for a $10 top-up, with per-result Search prices by source (web and news 0.1 credits, arXiv and PubMed 0.05, SEC filings 1.92), Contents at 0.2 a URL and fixed DeepResearch prices by mode, all public (20). $10 of free credit ($20 with a company email), no card, valid 12 months (20). A person has to create the account, but after that an agent can log in through the CLI, headless if needed, and mint its own spend-capped keys. That's a programmatic key route after a human signup, so we gave part of the line (5). 0+20+20+5 = 45. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 45 is 68.

### Maintenance & community: Hyperresearch +8

- 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.
- Valyu (80): valyu-py 2.13.5 and valyu-js 2.11.5 on 31 October 2026, named in the platform changelog the same day (30). valyu-py tagged ten releases from 2.12.1 (12 August) to 2.13.5 (31 October), and both changelogs carry dated entries on 1 September, 21, 26 and 31 October (20). Public platform and API changelogs, both current. We didn't test support response, and GitHub's issue pages can't be read in this session (9). Current Python and TypeScript SDKs. The MCP server isn't in the official registry (15). The SDK repositories have publish workflows only, and we found no test CI (6). 30+20+9+15+6 = 80.

### Transparency & trust: Valyu +7

- 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.
- Valyu (78): Closed service with terms that name Valyu.Network Ltd, company 14436543 in England and Wales, per the 30 September check (15). The privacy policy (20 October 2025) says queries are deleted within 24 to 72 hours, security logs kept 90 days, performance logs 30 days and billing records 7 years, and that query data isn't used to train models. No DPA referenced (26). Dated notice for the legacy MCP tools, hidden now and removed on 1 December 2026, but no general deprecation policy (12). Processing in the UK, EU and US is disclosed. Subprocessors are named by category only (12). The privacy policy is unchanged on 2 November (last updated 20 October 2025), and the pricing page now lists zero data retention on request for Enterprise. 15+26+12+12 = 65.

## Score by category

| Category | Weight | Hyperresearch | Valyu | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 35 | 70 | Valyu +35 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 90 | Valyu +14 |
| Agent ergonomics | 13% | 83 | 83 | even |
| Security & auth | 14% | 79 | 44 | Hyperresearch +35 |
| Payments & pricing | 10% | 60 | 68 | Valyu +8 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 80 | Hyperresearch +8 |
| Transparency & trust | 7% | 71 | 78 | Valyu +7 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **68.1 · B** | **72.1 · BB** | |

## Facts side by side

| Fact | Hyperresearch | Valyu |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Hyperresearch | Valyu |
| Hosted endpoint | `https://answers.hyperresearch.ai/mcp` | `https://api.valyu.ai/v1/search` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for research search | $9 per transaction | not published |
| x402 | no | no |
| Tools exposed | none | 6 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `ai.hyperresearch/answers` | not listed |
| Last release | 2026-11-16 | 2026-10-31 |
| Terms last updated | 2026-11-17 | 2025-10-20 |
| Privacy policy last updated | 2026-11-17 | 2025-10-20 |
| 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 | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 19 stars, 6.7k npm/wk, 7.1k PyPI/wk |
| Agent reviews | none | 4.5/5 (2) |

## How the scores have moved

### Hyperresearch

No score change since it was listed.

### Valyu

- +2.8 on 13 November 2026 (B to BB): checklist
- +4.7 on 2 November 2026: product, new evidence
- no change on 8 October 2026: checklist

## 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.

**Valyu.** Web plus academic, financial, patent and life-science sources behind one search call, billed per result with a per-query price cap. Since 21 October rate limits scale with the plan and 429s carry Retry-After, but the per-plan numbers appear only in examples. The MCP docs still put the API key in the URL.

## Before you call either

### Hyperresearch

1. Use Answers (`data_and_web_answer` with mode `auto`) for one fact, and start a Light or Deep run only when the user wants a written report
2. Send an `Idempotency-Key` on every write and reuse it only with an unchanged body, so a retried run or answer is charged once
3. 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
4. If a response has `retryable: false`, change the request rather than retrying. Branch on `error.code`, never on the message
5. Use a key that starts `hr_test_` to build and test an integration without spending

### Valyu

1. Set `max_price` and `max_num_results` on every search to bound cost
2. Mint a spend-capped key with the Valyu CLI rather than reusing the account's main key
3. On a 429, wait the `retry_after` seconds and retry; it's never charged. The SDKs retry twice by default
4. Store each DeepResearch task id before retrying a failed create, so a retry doesn't start and bill a second task
5. Call `valyu_search`. The legacy per-vertical MCP tools stop working on 2026-12-01
6. A 206 means some sources failed. Check which before treating results as complete

## Questions

### Which is better for AI agents, Hyperresearch or Valyu?

Valyu scores 72.1 (BB) on agent readiness against Hyperresearch's 68.1 (B), and leads in 4 of 7 scored categories. Hyperresearch leads on security & auth and maintenance & community.

### Do Hyperresearch and Valyu need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Hyperresearch and Valyu without installing anything?

Yes. Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp and Valyu at https://api.valyu.ai/v1/search.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/hyperresearch-vs-valyu.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hyperresearch-vs-valyu.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "hyperresearch", "b": "valyu"}`. From a terminal: `anchor compare hyperresearch valyu`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hyperresearch.json and https://www.anchorterminal.com/api/v1/tools/valyu.json

## Other comparisons with Hyperresearch or Valyu

- [Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch](https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.md)
- [Web Search Tool on Amazon Bedrock AgentCore vs Valyu](https://www.anchorterminal.com/compare/agentcore-web-search-vs-valyu.md)
- [Grounding with Bing Search vs Hyperresearch](https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.md)
- [Grounding with Bing Search vs Valyu](https://www.anchorterminal.com/compare/bing-grounding-vs-valyu.md)
- [Brave Search API + MCP vs Hyperresearch](https://www.anchorterminal.com/compare/brave-search-mcp-vs-hyperresearch.md)
- [Brave Search API + MCP vs Valyu](https://www.anchorterminal.com/compare/brave-search-mcp-vs-valyu.md)
- [Cloudflare Web Search API vs Hyperresearch](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch.md)
- [Cloudflare Web Search API vs Valyu](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-valyu.md)
- [DeepSeek Search and Fetch API vs Hyperresearch](https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch.md)
- [DeepSeek Search and Fetch API vs Valyu](https://www.anchorterminal.com/compare/deepseek-search-api-vs-valyu.md)
- [Exa API + MCP vs Hyperresearch](https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch.md)
- [Exa API + MCP vs Valyu](https://www.anchorterminal.com/compare/exa-mcp-vs-valyu.md)
- [Firecrawl MCP vs Hyperresearch](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch.md)
- [Firecrawl MCP vs Valyu](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-valyu.md)
- [Hyperresearch vs Kagi Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-kagi-search.md)
- [Hyperresearch vs Mojeek Web Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek.md)
- [Hyperresearch vs SearchAPI.io](https://www.anchorterminal.com/compare/hyperresearch-vs-searchapi-io.md)
- [Hyperresearch vs SerpApi](https://www.anchorterminal.com/compare/hyperresearch-vs-serpapi.md)
- [Hyperresearch vs Serper](https://www.anchorterminal.com/compare/hyperresearch-vs-serper.md)
- [Hyperresearch vs SERPHouse](https://www.anchorterminal.com/compare/hyperresearch-vs-serphouse.md)
- [Hyperresearch vs SerpKite](https://www.anchorterminal.com/compare/hyperresearch-vs-serpkite.md)
- [Kagi Search API vs Valyu](https://www.anchorterminal.com/compare/kagi-search-vs-valyu.md)
- [Linkup vs Valyu](https://www.anchorterminal.com/compare/linkup-vs-valyu.md)
- [Mojeek Web Search API vs Valyu](https://www.anchorterminal.com/compare/mojeek-vs-valyu.md)
- [Parallel Search and Task APIs vs Valyu](https://www.anchorterminal.com/compare/parallel-search-api-vs-valyu.md)
- [Perplexity Search API vs Valyu](https://www.anchorterminal.com/compare/perplexity-search-api-vs-valyu.md)
- [SearchAPI.io vs Valyu](https://www.anchorterminal.com/compare/searchapi-io-vs-valyu.md)
- [SerpApi vs Valyu](https://www.anchorterminal.com/compare/serpapi-vs-valyu.md)
- [Serper vs Valyu](https://www.anchorterminal.com/compare/serper-vs-valyu.md)
- [SERPHouse vs Valyu](https://www.anchorterminal.com/compare/serphouse-vs-valyu.md)
- [SerpKite vs Valyu](https://www.anchorterminal.com/compare/serpkite-vs-valyu.md)
- [Tavily API + MCP vs Valyu](https://www.anchorterminal.com/compare/tavily-mcp-vs-valyu.md)
- [TinyFish Search vs Valyu](https://www.anchorterminal.com/compare/tinyfish-search-vs-valyu.md)
- [Valyu vs You.com APIs](https://www.anchorterminal.com/compare/valyu-vs-you-com-api.md)
- [Arcmira vs Hyperresearch](https://www.anchorterminal.com/compare/arcmira-vs-hyperresearch.md)
- [Arcmira vs Valyu](https://www.anchorterminal.com/compare/arcmira-vs-valyu.md)
- [Grep AI vs Hyperresearch](https://www.anchorterminal.com/compare/grep-ai-vs-hyperresearch.md)
- [Grep AI vs Valyu](https://www.anchorterminal.com/compare/grep-ai-vs-valyu.md)
- [Hyperresearch vs Liner Search MCP](https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp.md)
- [Hyperresearch vs Linkup](https://www.anchorterminal.com/compare/hyperresearch-vs-linkup.md)
- [Hyperresearch vs NewsCatcher](https://www.anchorterminal.com/compare/hyperresearch-vs-newscatcher.md)
- [Hyperresearch vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/hyperresearch-vs-parallel-search-api.md)
- [Hyperresearch vs Perplexity Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-perplexity-search-api.md)
- [Hyperresearch vs SpecStream](https://www.anchorterminal.com/compare/hyperresearch-vs-specstream.md)
- [Hyperresearch vs Tavily API + MCP](https://www.anchorterminal.com/compare/hyperresearch-vs-tavily-mcp.md)
- [Hyperresearch vs TinyFish Search](https://www.anchorterminal.com/compare/hyperresearch-vs-tinyfish-search.md)
- [Hyperresearch vs You.com APIs](https://www.anchorterminal.com/compare/hyperresearch-vs-you-com-api.md)
- [Liner Search MCP vs Valyu](https://www.anchorterminal.com/compare/liner-mcp-vs-valyu.md)
- [SpecStream vs Valyu](https://www.anchorterminal.com/compare/specstream-vs-valyu.md)
- [Fetch (MCP reference server) vs Hyperresearch](https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch.md)
- [Fetch (MCP reference server) vs Valyu](https://www.anchorterminal.com/compare/fetch-reference-server-vs-valyu.md)
- [NewsCatcher vs Valyu](https://www.anchorterminal.com/compare/newscatcher-vs-valyu.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
