Head to head · Research search · October 2026 research run
Hyperresearch vs NewsCatcher
NewsCatcher scores 69.4 (B) on agent readiness against Hyperresearch's 68.1 (B), and leads in 4 of 7 scored categories. Hyperresearch leads on security & auth, payments & pricing and maintenance & community. Both do research search. NewsCatcher is cheaper for research search, $1 against $9 per transaction.
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
- Payments & pricing, 60 against 45
- Maintenance & community, 88 against 76
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
Best for Agents that need current news across languages, grouped into stories, or tables of events and company news on a schedule.
Ahead on
- Reliability, 67 against 35
- Schema & documentation, 94 against 76
- Transparency & trust, 79 against 71
Also in its favour
- Cheaper for research search, $1 against $9 per transaction
Watch for
The current News API and agent launched on 30 October 2026 and the MCP repository went public on 6 November 2026
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.
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.
NewsCatcher 45
API keys in the x-api-key header, several per account, revocable in the platform, with advice to keep one per application. A 403 for 'a key that may not use this API' suggests per-key API access, but no scopes are documented (20). The MCP server documents ?apiKey= on the server URL for Claude.ai custom connectors, with a warning, so less 10 (10 of 30). The MCP repository's SECURITY.md says URL keys are rejected unless the operator enables them, which the hosted server does per the docs. Toolsets let an operator load only the read-only news tools, write tools carry destructiveHint, and the server tells the assistant to confirm large or hourly agent jobs (14 of 20). Results are third-party article text and summaries, and no prompt-injection guidance was found in the docs or the MCP server's instructions (0 of 15). Every response carries a Correlation-ID, GET /subscription shows usage and balance, and runs are listed in the platform. No per-call audit log for the customer was found (7 of 15). The security page and footer claim SOC 2 Type II and link a trust centre on Oneleet, which wasn't read. A vulnerability disclosure policy covers the MCP server. No security.txt (404) and no bug bounty found (14 of 20). 10 + 14 + 0 + 7 + 14 = 45.
Reliability NewsCatcher +32
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.
NewsCatcher 67
Read with the hosted lines, for the News API, the agent and the hosted MCP server. status.newscatcherapi.com (Hyperping) shows one News API component with 99.820% uptime from August to November 2026 and an incident history. The agent and the MCP server have no component of their own (20). In the 90 days from 8 August, one incident, on 1 September 2026, when the vendor wrote that for about four hours a higher-than-usual number of requests to the production News API timed out because of one client's queries. Read as one major (10). Rate limits published per plan, 1 request a second free and up to 10 on pay as you go, with exact limits from the free GET /subscription (15). 429 carries Retry-After with instructions to retry the same request, 503 carries Retry-After, and failed or refused requests are not charged. Agent runs and monitor creation have no idempotency keys (12 of 15). An uptime SLA exists only in signed Enterprise agreements; none is published (0). Generally available since 30 October 2026, with OAuth for the MCP server announced as coming soon (10). 20 + 10 + 15 + 12 + 0 + 10 = 67.
Schema & documentation NewsCatcher +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.
NewsCatcher 94
OpenAPI 3.1 for the News API (version 1.3.9, 4 paths) and the agent (version 1.5.1, 33 paths), linked from llms.txt, and typed JSON Schema on every MCP tool through Pydantic (25). llms.txt, a Markdown copy of every page and a docs MCP server (10). MCP tool descriptions say when to use each and which tool to use instead, such as list_articles for older news; the REST reference explains each endpoint and the 'Choose an API' page compares them (17 of 20). Inputs are typed with enums for effort, mode and dimensions, length and range limits such as a 500-character query and limit 1 to 100, and required fields marked (13 of 15). Runnable examples in curl, Python and JavaScript, and an error table with retry advice for every status. The agent spec carries no response examples (14 of 15). Versioned APIs with a dated changelog, the latest entries on 4 November 2026, and separate changelogs for the v3 News API and CatchAll (15). 25 + 10 + 17 + 13 + 14 + 15 = 94.
Payments & pricing Hyperresearch +15
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.
NewsCatcher 45
No x402, MPP or L402 (0). Credit prices per call published without login, and credits cost $1 per 1,000 through top-ups from $25 (20). 10,000 free credits every 30 days on a $0 plan, and the first top-up moves an account to pay as you go. No page says whether a card is needed to open the free plan, so half (10). A person signs up in the platform in a browser to get a key (0). NewsMCP's keyless tier belongs to a separate product and isn't counted. 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Maintenance & community Hyperresearch +12
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.
NewsCatcher 76
Read for a closed service, with the MCP repository read as code. News API 1.1.0 and Agent 1.5.0 on 4 November 2026, MCP server 0.1.0 on 6 November and v3 News API 3.25.0 on 6 November (30). In the 90 days from 8 August, the 30 October launch, News API 1.1.0, Agent 1.5.0, MCP 0.1.0 and v3 releases 3.19.0 to 3.25.0 (20). Public dated changelogs, support by email and Pylon, and a security policy with a 3-business-day target. The MCP repository is a day old, so there are no issues to judge (10 of 15). The CatchAll MCP server is in the official registry under the verified namespace com.newscatcherapi, but the new server isn't, and no official SDK for the current API was found; the Enterprise APIs list libraries (8 of 15). The MCP repository runs its test suite in CI with a read-only token; pass state not read (8 of 10). 30 + 20 + 10 + 8 + 8 = 76.
Transparency & trust NewsCatcher +8
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.
NewsCatcher 79
The API is closed under terms of 2 November 2026 naming NewsCatcher, Inc., and the MCP server is MIT, so between the two bands (20 of 30). The terms say inputs and generated data are not used to train models, a DPA applies automatically, and the privacy policy gives retention periods (server logs 7 days, API logs with query text 90 days, then archived indefinitely, billing records about seven years). They agree with each other, but indefinite archives of query logs hold it back (22 of 30). The terms promise 30 days' email notice before a paid product or API version is discontinued, with refunds of unused credits, and the v3 News API has a migration guide (15 of 20). A sub-processor list dated 2 November 2026 with each provider's location and the data it handles. The MCP repository deploys to Vercel and can send pseudonymised analytics to PostHog, and neither appears on the list (16 of 20). 20 + 22 + 15 + 16 = 73.
Score by category
| Category | Weight | Hyperresearch | NewsCatcher | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 67 | NewsCatcher +32 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 94 | NewsCatcher +18 |
| Agent ergonomics | 13% | 83 | 84 | NewsCatcher +1 |
| Security & auth | 14% | 79 | 45 | Hyperresearch +34 |
| Payments & pricing | 10% | 60 | 45 | Hyperresearch +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 76 | Hyperresearch +12 |
| Transparency & trust | 7% | 71 | 79 | NewsCatcher +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.1/100 | B 69.4/100 |
Facts side by side
| Fact | Hyperresearch | NewsCatcher |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Hyperresearch | NewsCatcher, Inc. |
| Hosted endpoint | https://answers.hyperresearch.ai/mcp | https://mcp.newscatcherapi.com/mcp |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| Price for research search | $9 per transaction | $1 per transaction |
| x402 | no | no |
| Tools exposed | none | 15 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | ai.hyperresearch/answers | not listed |
| Last release | 2026-11-16 | 2026-11-06 |
| Terms last updated | 2026-11-17 | 2026-11-02 |
| Privacy policy last updated | 2026-11-17 | 2026-11-02 |
| 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 | yes |
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.
NewsCatcher
One key and one credit balance cover a ranked news search, a background research agent and a hosted MCP server with toolsets and annotated tools, under OpenAPI 3.1 specs and a dated changelog. The current API launched on 30 October 2026, the MCP server accepts the key in its URL, and no SLA is published below Enterprise.
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
NewsCatcher
- Send the key in the
x-api-keyheader, and use a separate key for the MCP server so it can be revoked alone - Call
start_researchwithdry_runfirst, since agent runs cost 1,000 to 6,000 credits - Use
effort=lowfor quick lookups; the defaultmediumcosts five times as much - Use
/articlesorlist_articlesfor news older than 30 days or exact counts;/searchcovers 30 days only - On 429 or 503 wait for Retry-After, and quote the Correlation-ID header to support
Questions
Which is better for AI agents, Hyperresearch or NewsCatcher?
NewsCatcher scores 69.4 (B) on agent readiness against Hyperresearch's 68.1 (B), and leads in 4 of 7 scored categories. Hyperresearch leads on security & auth, payments & pricing and maintenance & community.
Which is cheaper for research search, Hyperresearch or NewsCatcher?
NewsCatcher, at $1 per transaction against $9 per transaction for Hyperresearch. These are the vendors' published prices for the job.
Do Hyperresearch and NewsCatcher need an API key?
Hyperresearch takes an API key or an OAuth sign-in. NewsCatcher needs an API key.
Can an agent call Hyperresearch and NewsCatcher without installing anything?
Yes. Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp and NewsCatcher at https://mcp.newscatcherapi.com/mcp.
Other comparisons with Hyperresearch or NewsCatcher
- Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch
- Web Search Tool on Amazon Bedrock AgentCore vs NewsCatcher
- Grounding with Bing Search vs Hyperresearch
- Grounding with Bing Search vs NewsCatcher
- Brave Search API + MCP vs Hyperresearch
- Brave Search API + MCP vs NewsCatcher
- Cloudflare Web Search API vs Hyperresearch
- Cloudflare Web Search API vs NewsCatcher
- DeepSeek Search and Fetch API vs Hyperresearch
- DeepSeek Search and Fetch API vs NewsCatcher
- Exa API + MCP vs Hyperresearch
- Exa API + MCP vs NewsCatcher
- 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
- Kagi Search API vs NewsCatcher
- Linkup vs NewsCatcher
- Mojeek Web Search API vs NewsCatcher
- NewsCatcher vs Parallel Search and Task APIs
- NewsCatcher vs Perplexity Search API
- NewsCatcher vs TinyFish Search
- Arcmira vs Hyperresearch
- Arcmira vs NewsCatcher
- Grep AI vs Hyperresearch
- Grep AI vs NewsCatcher
- Hyperresearch vs Liner Search MCP
- Hyperresearch vs Linkup
- 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
- Liner Search MCP vs NewsCatcher
- NewsCatcher vs SpecStream
- Fetch (MCP reference server) vs Hyperresearch
- NewsCatcher vs SearchAPI.io
- NewsCatcher vs SerpApi
- NewsCatcher vs Serper
- NewsCatcher vs SERPHouse
- NewsCatcher vs SerpKite
- NewsCatcher vs Tavily API + MCP
- NewsCatcher vs Valyu
- NewsCatcher vs You.com APIs
Machine-readable
- This page as Markdown
/compare/hyperresearch-vs-newscatcher.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hyperresearch.json·/api/v1/tools/newscatcher.json - From a terminal
anchor compare hyperresearch newscatcher(the CLI) - Over MCP
compare_tools {"a": "hyperresearch", "b": "newscatcher"}at/mcp, no key