# Cloudflare Web Search API vs Hyperresearch

> Cloudflare Web Search and Hyperresearch score within a point of each other for web search, 68.1 and 68.1 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch
- Markdown: https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch.md (~6,350 tokens)
- Slim: https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch.min.md (~1,230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch.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

Cloudflare Web Search API and Hyperresearch score within a point of each other on agent readiness, 68.1 (B) and 68.1 (B). Hyperresearch leads on agent ergonomics, security & auth, payments & pricing and maintenance & community. Both do web search.

- Cloudflare Web Search API: grade B, 68.1/100, rank #403 of 1557. Markdown https://www.anchorterminal.com/tools/cloudflare-web-search.md · JSON https://www.anchorterminal.com/api/v1/tools/cloudflare-web-search.json
- 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
- 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

### Cloudflare Web Search API (B)

Good for: Agents and apps already on Cloudflare Workers or AI Gateway that want cheap snippet search ($0.25 per 1,000 with Ceramic.ai) on the same bill and logs as their inference.

Ahead on:
- Reliability, 77 against 35
- Schema & documentation, 81 against 76

Watch for: Open beta, with no SLA found for AI Gateway

### 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:
- Agent ergonomics, 83 against 63
- Security & auth, 79 against 74
- Payments & pricing, 60 against 30
- Maintenance & community, 88 against 71

Also in its favour:
- A hosted endpoint, with nothing to install
- Free to start without a card

Watch for: No status page, and the terms say there is no SLA and no uptime figure


## Why the edge

### Reliability: Cloudflare Web Search API +42

- Cloudflare Web Search API (77): Scored as a hosted API. www.cloudflarestatus.com lists AI Gateway, Workers AI and AI Search among its services, each with 30-day and 90-day incident bars (20). Web search has no component of its own and runs through AI Gateway. On 2 November 2026 the services page showed AI Gateway with no days with incidents in 90 days. The five Workers AI incident days (13 and 19 August, 9 September, 15 and 27 October) name model errors, a model outage and AI Security for Apps, not AI Gateway or web search, so a clean record (30). The 5 October reading from the status page's JSON feed is struck. 200 requests per 60 seconds per gateway on Unified Billing credentials, and 1,200 requests per five minutes per Cloudflare API token (15). The Cloudflare API returns 429 with `retry-after` and `Ratelimit` headers, and the error body carries a `retryable` flag. Searches have no side effects, but 429 isn't among the responses the OpenAPI operation lists (12 of 15). No SLA for AI Gateway found (0). The docs still label it open beta on 2 November, although the OpenAPI operation is tagged generally-available. We scored from the docs (0). 20 + 30 + 15 + 12 + 0 + 0 = 77.
- 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

- Cloudflare Web Search API (30): No x402, MPP or L402 on /ai/websearch. AI Gateway Machine Payments covers only /ai/run for four open models (0, Machine Payments page unchanged since 30 September and still limited to `/ai/run`). Per-search prices published without a login, $0.25, $5.00 and $7.00 per 1,000 by provider. The 5 per cent fee on credit purchases sits on the Unified Billing page, not the providers page (20). No free allowance found. Credits need a payment method, and the BYOK route needs an account with the provider (0). A person signs up for Cloudflare in a browser and buys credits or stores a provider key (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.

### Agent ergonomics: Hyperresearch +20

- Cloudflare Web Search API (63): Results are small by default (URL, title, description), and `limit` caps them at 1 to 10. The default provider, Ceramic.ai, returns descriptions of up to 8,000 characters a result with no parameter to shorten them (15 of 25). `limit` is the only control. No pagination, offset, domain, date, country or freshness filters (6 of 20). Errors come back with `category` (gateway, credential, provider, internal), `code`, `status`, `retryable` and `gatewayRequestId`. The codes themselves aren't listed (16 of 20). Searches only read, the error body says whether a retry helps, and gateways can retry upstream failures up to five times. No idempotency keys, which a read doesn't need (16 of 20). Only `query` and the gateway ID are required. The Workers binding is TypeScript, and the Cloudflare TypeScript SDK 7.3.0 of 3 October has no web search method. We didn't check the Python or Go SDKs (10 of 15).
- 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 +17

- Cloudflare Web Search API (71): Read for a closed service. The web search launch entry is dated 2 October 2026, 31 days ago. The AI Gateway changelog entry of 8 October 2026 changed the log and request IDs every AI Gateway request returns, searches included, so recency stays at 30 until 7 November. Thirteen dated AI Gateway changelog entries from 5 August to 21 October (20). A public changelog with RSS and a developer Discord. We didn't check support response times (8 of 15). The Workers binding has the method. The Cloudflare TypeScript SDK's newest tag is still 7.3.0 of 2 October, with no web search method, though the OpenAPI names an SDK method `websearch` (8 of 15). The OpenAPI spec carries the path. Nothing else to measure for a hosted endpoint (5 of 10). 30 + 20 + 8 + 8 + 5 = 71.
- 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.

### Schema & documentation: Cloudflare Web Search API +5

- Cloudflare Web Search API (81): Cloudflare's public OpenAPI has `/accounts/{account_id}/ai/websearch` with a typed body, `additionalProperties: false` and typed 200, 400, 403 and 502 responses. `provider` is a free string there where the docs give an enum (22 of 25). llms.txt for the product and Markdown for every page (10). The providers page says which provider suits which job, such as Ceramic.ai for agents that run many searches and Exa for short query-relevant excerpts. Nothing says when not to use the endpoint, and the OpenAPI description is one line (12 of 20). `query` 1 to 1,024 characters, `limit` 1 to 10, `provider` enum in the docs, `byokAlias` with a pattern (14 of 15). curl and Worker examples, a response example, and a typed error body with category, code and `retryable`. No catalogue of error codes or messages found (11 of 15). Dated launch entry in the AI Gateway changelog, still the only web search entry on 2 November 2026. The API path carries v4 for the whole Cloudflare API, nothing specific to web search (12 of 15). The OpenAPI operation, re-read from a clone on 2 November, is unchanged.
- 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.

### Security & auth: Hyperresearch +5

- Cloudflare Web Search API (74): Cloudflare API tokens are scoped by permission and revocable, and web search needs only Workers AI Read and AI Gateway Read. Permission is per account, not per gateway or provider. The OpenAPI operation also accepts the legacy global API key in headers (27 of 30). Every call reads. Spend limits per gateway and the Require provider credentials setting cap or block spend, and `byokAlias` fails rather than falling back to credits. Read permission is enough to spend credits (14 of 20). Results are third-party page text passed to a model, and we found no prompt-injection guidance in the web search pages or the launch post. AI Gateway Guardrails aren't documented for web search (0 of 15). Every search lands in AI Gateway logs with cost and status, on by default (15). security.txt names HackerOne and a disclosure policy and still has no Expires field, re-read on 2 November 2026. Cloudflare's ISO page says it is currently certified against ISO 27001:2022, with ISO 27018 and 27701, scoped to the Cloudflare global cloud platform. 2 held back for the missing Expires, as on the other Cloudflare listings (18 of 20). 27 + 14 + 0 + 15 + 18 = 74.
- 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.

## Score by category

| Category | Weight | Cloudflare Web Search API | Hyperresearch | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 77 | 35 | Cloudflare Web Search API +42 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 76 | Cloudflare Web Search API +5 |
| Agent ergonomics | 13% | 63 | 83 | Hyperresearch +20 |
| Security & auth | 14% | 74 | 79 | Hyperresearch +5 |
| Payments & pricing | 10% | 30 | 60 | Hyperresearch +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 71 | 88 | Hyperresearch +17 |
| Transparency & trust | 7% | 73 | 71 | Cloudflare Web Search API +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **68.1 · B** | **68.1 · B** | |

## Facts side by side

| Fact | Cloudflare Web Search API | Hyperresearch |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Cloudflare | Hyperresearch |
| Hosted endpoint | no (local only) | `https://answers.hyperresearch.ai/mcp` |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for web search | $0.25 per 1,000 requests | $0.05 per call |
| x402 | no | no |
| Licence | Proprietary service under Cloudflare's terms. Each search provider's own terms are linked from the providers page | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `ai.hyperresearch/answers` |
| Last release | 2026-10-02 | 2026-11-16 |
| Terms last updated | 2025-09-12 | 2026-11-17 |
| Privacy policy last updated | no date given | 2026-11-17 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | 3/5 (2) | none |

## How the scores have moved

### Cloudflare Web Search API

- +1.2 on 13 November 2026: checklist
- +5.0 on 2 November 2026 (C to B): new evidence
- -0.2 on 8 October 2026 (B to C): checklist

### Hyperresearch

No score change since it was listed.

## Verdicts

**Cloudflare Web Search API.** One endpoint that sends a search to Ceramic.ai, Exa or Linkup and returns results in one format, logged and billed through AI Gateway, whose status shows no incidents in 90 days. Ceramic.ai costs $0.25 per 1,000 searches. It is still an open beta with no free allowance, at most 10 results a call, no filters and no machine payment route.

**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

### Cloudflare Web Search API

1. Set `options.gateway.id`. Every account has a gateway named `default`
2. Pass `provider` explicitly. It defaults to Ceramic.ai, whose descriptions can run to 8,000 characters a result
3. Set `limit` to the results you'll read, between 1 and 10
4. Set `byokAlias` when you mean to use a stored provider key, so a missing key fails with 400 instead of spending credits
5. Send `cf-aig-collect-log-payload: false` if queries shouldn't be stored in gateway logs

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

## Questions

### Which is better for AI agents, Cloudflare Web Search API or Hyperresearch?

Cloudflare Web Search API and Hyperresearch score within a point of each other on agent readiness, 68.1 (B) and 68.1 (B). Hyperresearch leads on agent ergonomics, security & auth, payments & pricing and maintenance & community.

### Do Cloudflare Web Search API and Hyperresearch need an API key?

Cloudflare Web Search API needs an API key. Hyperresearch takes an API key or an OAuth sign-in.

### Can an agent call Cloudflare Web Search API and Hyperresearch without installing anything?

No hosted endpoint is listed for Cloudflare Web Search API. Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp.


## For agents

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

## Other comparisons with Cloudflare Web Search API or Hyperresearch

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

---

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