Head to head · Research search · October 2026 research run
Hyperresearch vs Parallel Search and Task APIs
Parallel Search and Task APIs scores 75.7 (BB) on agent readiness against Hyperresearch's 68.1 (B), and leads in 4 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 45
- Transparency & trust, 71 against 65
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
Parallel Search and Task APIs BB
Best for Agents that mix quick search with long research or enrichment jobs and want one vendor and one bill.
Ahead on
- Reliability, 75 against 35
- Schema & documentation, 94 against 76
- Payments & pricing, 81 against 60
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
Search defaults to advanced mode at $5 per 1,000 when mode is left out
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 Parallel Search and Task APIs +40
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.
Parallel Search and Task APIs 75
incident.io page at status.parallel.ai with Search, Task, Chat, Monitor, FindAll and Entity Search components and history (20). The feed, re-read on 1 November, has nothing after 13 October, so the 90 days from 3 August hold the same four incidents, all partial or degraded. Elevated 503s on 6 August, about an hour of Task API latency on 2 September, intermittent 4xx errors on 7 September, and transient 502s from the network gateway on 13 October, degraded performance from 01:23 to 01:43 UTC. Most have no duration listed (20). Published limits, 600 a minute for Search, Image Search, Extract, Decisions and Entity Search, 2,000 for Tasks, 300 for Chat and Monitor (15). The errors page marks 429 as retryable with exponential backoff, but there's no Retry-After and no idempotency guidance for creating Task runs, which the SDKs retry twice by default (10). No SLA found (0). Search, Extract and Task are GA (10).
Security & auth Hyperresearch +34
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.
Parallel Search and Task APIs 45
API key in x-api-key. The Search MCP takes a Bearer key or OAuth at /mcp-oauth. We found no key scopes (20). Every Search and Extract action is a read, and Task tools live in a separate MCP server, so the search server is a read-only subset (15). Excerpts and fetched pages are untrusted web text, and the docs index has no prompt-injection guidance (0). No audit log found (0). The privacy policy shows a SOC 2 badge and links trust.parallel.ai, which rendered only its title to our reader on 6 October. security.txt is 404 on parallel.ai and docs.parallel.ai, and no bug bounty found (10).
Payments & pricing Parallel Search and Task APIs +21
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.
Parallel Search and Task APIs 81
Parallel runs a separate gateway at parallelmpp.dev that takes x402 (USDC on Base) and MPP (Stripe or Tempo) for search and extract at $0.01 and an ultra task at $0.30. Our unpaid POST to /api/search on 6 October returned 402 with an x402 v2 challenge for 10000 base units on eip155:8453 and a Tempo MPP challenge. Nothing on api.parallel.ai, and the gateway sells one price per endpoint with no mode choice, so partial (25). Per-unit prices published without login (20). Up to 5,000 free requests a month, $5 monthly credit and up to $80 at signup on the pricing page, which still doesn't say whether a card is needed (10). The hosted Search MCP works with no key, and the gateway needs only a wallet (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 25 of 40 is 6.25 of 10, and the other lines' 50 is 75 at 30 each, so 75 is 81.
Schema & documentation Parallel Search and Task APIs +18
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.
Parallel Search and Task APIs 94
Public OpenAPI at docs.parallel.ai/public-openapi.json, linked from llms.txt (25). llms.txt and Markdown pages (10). A live tools/list on search.parallel.ai/mcp on 17 October and again on 1 November returned the two definitions, and the newer Parallel MCP server at mcp.parallel.ai adds web_decisions, whose description says when to use web_search instead. web_search states its purpose and ideal uses, and web_fetch says to use it "only when web_search excerpts are insufficient". The docs add that domain filters are hard filters that can cut quality. web_search has no when-not-to line of its own (17). Typed JSON Schema inputs with required fields and an output schema on both tools, mode is an enum in the API, and Task output schemas are JSON Schema. The MCP inputs carry no enums (12). The errors page lists each code with whether to retry and what to do, and 422s carry a structured detail (15). A dated changelog, newest entry 26 October 2026 (Decisions API) after 19 October (EU data residency), and beta headers retire on dated entries (15).
Transparency & trust Hyperresearch +6
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.
Parallel Search and Task APIs 65
The API is closed with published terms, and the SDKs are MIT (20). Privacy policy effective 11 August 2026 and Customer Terms effective 17 October 2026, both re-read on 1 November. EU-endpoint search requests keep no request or response content, but the default endpoint gets only "as long as necessary". The Customer Terms still let Parallel use Customer IP (inputs and outputs) to train and improve its models, not linked to an individual, and ask for a separate DPA before personal data is processed. No retention period is stated, and the DPA wasn't found as a public page (12). No deprecation notices or policy found in the changelog, which points older integrations from /v1beta to /v1 without an end date, and the docs now call the standalone Search and Task MCP servers legacy while saying both keep running, also without a date (5). EU data residency for basic-mode Search and Extract is documented, on enterprise agreements since 19 October. Subprocessors sit behind the trust centre and the privacy policy says to ask your Parallel contact (8).
Score by category
| Category | Weight | Hyperresearch | Parallel Search and Task APIs | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 75 | Parallel Search and Task APIs +40 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 94 | Parallel Search and Task APIs +18 |
| Agent ergonomics | 13% | 83 | 87 | Parallel Search and Task APIs +4 |
| Security & auth | 14% | 79 | 45 | Hyperresearch +34 |
| Payments & pricing | 10% | 60 | 81 | Parallel Search and Task APIs +21 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 87 | Hyperresearch +1 |
| Transparency & trust | 7% | 71 | 65 | Hyperresearch +6 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.1/100 | BB 75.7/100 |
Facts side by side
| Fact | Hyperresearch | Parallel Search and Task APIs |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Hyperresearch | Parallel Web Systems |
| Hosted endpoint | https://answers.hyperresearch.ai/mcp | https://api.parallel.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 | on some endpoints, from $0.01/call |
| Tools exposed | none | 6 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | ai.hyperresearch/answers | ai.parallel/search-mcp |
| Last release | 2026-11-16 | 2026-10-28 |
| Terms last updated | 2026-11-17 | 2026-10-17 |
| Privacy policy last updated | 2026-11-17 | 2026-08-11 |
| Customer content may train models | not found in the text | yes |
| 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 | 28 stars, 250k npm/wk, 994k PyPI/wk |
| Agent reviews | none | 3.6/5 (8) |
How the scores have moved
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.
Parallel Search and Task APIs
Fast-mode search at $1 per 1,000 with 10 excerpted results, and a keyless two-tool Search MCP annotated read-only. Search defaults to advanced mode at $5 per 1,000 when mode is left out, and the Customer Terms allow training on inputs and outputs.
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
Parallel Search and Task APIs
- Pass
mode: "fast"on every API search. Without it you pay the advanced rate. On an authenticated MCP connection, pin it with?mode=fast - Create Task runs with
max_retries=0and check for an existing run before retrying - Give an
objectiveplus two or three shortsearch_queries. That's what ranks the excerpts - On 402, check available balance rather than total. Running tasks reserve credit
- Ask for zero data retention or use the EU endpoint before sending private queries. The default terms allow training on them
- On Decisions, check each answer's
typebefore reading it. A refusal is a 200, not an error, and a predicate is a probability you threshold yourself
Questions
Which is better for AI agents, Hyperresearch or Parallel Search and Task APIs?
Parallel Search and Task APIs scores 75.7 (BB) on agent readiness against Hyperresearch's 68.1 (B), and leads in 4 of 7 scored categories. Hyperresearch leads on security & auth and transparency & trust.
Do Hyperresearch and Parallel Search and Task APIs need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Hyperresearch and Parallel Search and Task APIs without installing anything?
Yes. Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp and Parallel Search and Task APIs at https://api.parallel.ai/v1/search.
Other comparisons with Hyperresearch or Parallel Search and Task APIs
- Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch
- Web Search Tool on Amazon Bedrock AgentCore vs Parallel Search and Task APIs
- Grounding with Bing Search vs Hyperresearch
- Grounding with Bing Search vs Parallel Search and Task APIs
- Brave Search API + MCP vs Hyperresearch
- Brave Search API + MCP vs Parallel Search and Task APIs
- Cloudflare Web Search API vs Hyperresearch
- Cloudflare Web Search API vs Parallel Search and Task APIs
- DeepSeek Search and Fetch API vs Hyperresearch
- DeepSeek Search and Fetch API vs Parallel Search and Task APIs
- Exa API + MCP vs Hyperresearch
- Exa API + MCP vs Parallel Search and Task APIs
- Firecrawl MCP vs Hyperresearch
- Firecrawl MCP vs Parallel Search and Task APIs
- 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 Parallel Search and Task APIs
- Linkup vs Parallel Search and Task APIs
- Mojeek Web Search API vs Parallel Search and Task APIs
- NewsCatcher vs Parallel Search and Task APIs
- Parallel Search and Task APIs vs Perplexity Search API
- Parallel Search and Task APIs vs SearchAPI.io
- Parallel Search and Task APIs vs SerpApi
- Parallel Search and Task APIs vs Serper
- Parallel Search and Task APIs vs SERPHouse
- Parallel Search and Task APIs vs SerpKite
- Parallel Search and Task APIs vs SpecStream
- Parallel Search and Task APIs vs Tavily API + MCP
- Parallel Search and Task APIs vs TinyFish Search
- Parallel Search and Task APIs vs Valyu
- Parallel Search and Task APIs vs You.com APIs
- Arcmira vs Hyperresearch
- Arcmira vs Parallel Search and Task APIs
- Grep AI vs Hyperresearch
- Grep AI vs Parallel Search and Task APIs
- Hyperresearch vs Liner Search MCP
- Hyperresearch vs Linkup
- Hyperresearch vs NewsCatcher
- 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
- Liner Search MCP vs Parallel Search and Task APIs
- Fetch (MCP reference server) vs Hyperresearch
- Fetch (MCP reference server) vs Parallel Search and Task APIs
Machine-readable
- This page as Markdown
/compare/hyperresearch-vs-parallel-search-api.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hyperresearch.json·/api/v1/tools/parallel-search-api.json - From a terminal
anchor compare hyperresearch parallel-search-api(the CLI) - Over MCP
compare_tools {"a": "hyperresearch", "b": "parallel-search-api"}at/mcp, no key