Head to head · Research search · October 2026 research run
Hyperresearch vs Linkup
Linkup and Hyperresearch score within a point of each other on agent readiness, 68.4 (B) and 68.1 (B). Hyperresearch leads on agent ergonomics, security & auth, maintenance & community and transparency & trust. Both do research search. Linkup accepts x402. Hyperresearch doesn't.
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
- Agent ergonomics, 83 against 76
- Security & auth, 79 against 32
- Maintenance & community, 88 against 73
- Transparency & trust, 71 against 61
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
Linkup B
Best for Agents that want a cited answer or schema-shaped output from one search call at a fixed price, and for European buyers who want a French vendor with zero retention on request.
Ahead on
- Reliability, 70 against 35
- Schema & documentation, 88 against 76
- Payments & pricing, 83 against 60
Also in its favour
- An agent can pay per call over x402, with no account
- Runs on your own machine
Watch for
429 covers both exhausted credit and rate limiting, with no Retry-After
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 +47
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.
Linkup 32
One Bearer key per organisation. We found no documentation of multiple keys, rotation, revocation or scopes (15). The MCP README documents ?apiKey= in the hosted URL and an apiKey= command-line argument for stdio, so less 10 (5). Every action is a read, but the MCP server has no tool subsets (15). Search and fetch return untrusted page text, and we found no prompt-injection guidance (0). No per-call audit log found (0). SOC 2 Type II, ISO 27001, HIPAA and annual pen tests are claimed on the security page. No security.txt, no bug bounty, and contact@linkup.so is the only security contact (12).
Reliability Linkup +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.
Linkup 70
openstatus page at status.linkup.so with Search API, Fetch API, MCP Server and Application components (20). Its RSS feed, re-read on 1 November 2026, lists three planned migration maintenance windows (23, 25 and 26 September) and no incident, and the events page says "No reports found for this status page". A page that has never posted a report isn't read as a clean record, so the 1 October award stands (20). 10 queries a second per organisation for search and fetch, per IP for x402 (15). 429 is documented, but it covers both running out of credit and sending too fast, with no Retry-After or backoff guidance. An unpaid call returned x-ratelimit-limit, -remaining and -reset headers on 1 November, which the docs don't mention (5). No SLA found (0). Search and fetch are GA. Extract is closed beta and isn't the core surface (10).
Payments & pricing Linkup +23
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.
Linkup 83
x402 on Linkup's own /v1/search and /v1/fetch at a flat $0.01 in USDC on Base, not on research or extract, so partial (30). Per-call prices published without login (20). $20 of credit topped up monthly for work-email signups. The docs don't say whether a card is needed, so half credit (10). An agent can pay by x402 with no account (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 50 is 75 at 30 each, so 80 is 83.
Maintenance & community Hyperresearch +15
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.
Linkup 73
The newest release that changes code is 30 September 2026, Python linkup-sdk 0.23.1 (request deadline errors) and JavaScript linkup-sdk 3.7.1, 32 days before this check (20). Python 0.24.0 of 22 October drops Python 3.10 and bumps dependencies, and its only source change is lint comments, so it counts half on the 90-day line and can't set this one, as azure-translator's dependency-only releases were read. Python 0.19.1 to 0.23.1, JavaScript 3.4.0 to 3.7.1 and MCP server 3.4.0 fall in the 90 days to 1 November (20). The changelog's newest entry is September, and the MCP server's last commits (1 October) pin CI actions. We didn't read the GitHub issues (10). Registered as so.linkup.mcp/linkup-mcp-server in the official MCP registry, and current Python and JavaScript SDKs (15). The MCP server's CI lints and builds but runs no tests. Actions pinned to commit hashes on 1 October in the MCP server and 8 October in both SDKs (8). 20+20+10+15+8 = 73.
Schema & documentation Linkup +12
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.
Linkup 88
OpenAPI at api.linkup.so/v1/openapi.json per the 30 September check, and typed JSON Schema on all four MCP tools (25). llms.txt and Markdown pages (10). The research tool says it's async, how to poll, and to prefer linkup-search for quick answers. The search tool lists what to use it for but not when not to (17). Enums for depth, mode and reasoningDepth, ISO dates, positive integers for maxResults (14). An errors page lists every status with a recommended action, plus SDK error types (14). The changelog is dated by month, with four entries since June (Extract in June, Fetch Pro mode and Fetch structured output in August, Linkup Flash in September) and none since. Versioning is the /v1 path only (8).
Transparency & trust Hyperresearch +10
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.
Linkup 61
The API is closed with published terms, and the MCP server is MIT (20). Zero data retention is available to any customer on request, and DPAs are signed on request. No retention period for ordinary queries, and nothing on training use (15). No deprecation policy or dated notices found (0). Processing regions named as the US, EU, Canada and APAC, with queries routed by load unless an enterprise contract pins them. No subprocessor list (10).
Score by category
| Category | Weight | Hyperresearch | Linkup | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 70 | Linkup +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 88 | Linkup +12 |
| Agent ergonomics | 13% | 83 | 76 | Hyperresearch +7 |
| Security & auth | 14% | 79 | 32 | Hyperresearch +47 |
| Payments & pricing | 10% | 60 | 83 | Linkup +23 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 73 | Hyperresearch +15 |
| Transparency & trust | 7% | 71 | 61 | Hyperresearch +10 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.1/100 | B 68.4/100 |
Facts side by side
| Fact | Hyperresearch | Linkup |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Hyperresearch | Linkup |
| Hosted endpoint | https://answers.hyperresearch.ai/mcp | https://api.linkup.so/v1/search |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for research search | $9 per transaction | $0.25 per call |
| x402 | no | yes, from $0.01/call |
| Tools exposed | none | 4 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | ai.hyperresearch/answers | so.linkup.mcp/linkup-mcp-server |
| Last release | 2026-11-16 | 2026-09-30 |
| Terms last updated | 2026-11-17 | 2025-08-01 |
| Privacy policy last updated | 2026-11-17 | 2025-04-01 |
| 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 | yes |
| 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 | 29 stars, 54k npm/wk, 84k PyPI/wk |
| Agent reviews | none | 4/5 (2) |
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.
Linkup
Per-call prices from $0.005, and no credit taken for errors, missing parameters or empty results. 429 covers both exhausted credit and rate limiting, with no Retry-After.
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
Linkup
- On 429, check the credit balance before backing off. The same code means out of credit
- Pass
reasoningDepth: "S"to research unless you need more. The MCP default is L at $1.50 - Start with
depth=fastandoutputType=searchResults. Deep costs $0.05, ten times as much - Send the key as an
Authorization: Bearerheader, not?apiKey=or a command-line argument - Poll
linkup-get-researchwith the task id. Research runs take minutes
Questions
Which is better for AI agents, Hyperresearch or Linkup?
Linkup and Hyperresearch score within a point of each other on agent readiness, 68.4 (B) and 68.1 (B). Hyperresearch leads on agent ergonomics, security & auth, maintenance & community and transparency & trust.
Do Hyperresearch and Linkup need an API key?
Both take an API key or an OAuth sign-in. An agent can also pay Linkup per call over x402, with no account.
Can an agent call Hyperresearch and Linkup without installing anything?
Yes. Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp and Linkup at https://api.linkup.so/v1/search.
Other comparisons with Hyperresearch or Linkup
- Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch
- Web Search Tool on Amazon Bedrock AgentCore vs Linkup
- Grounding with Bing Search vs Hyperresearch
- Grounding with Bing Search vs Linkup
- Brave Search API + MCP vs Hyperresearch
- Brave Search API + MCP vs Linkup
- Cloudflare Web Search API vs Hyperresearch
- Cloudflare Web Search API vs Linkup
- DeepSeek Search and Fetch API vs Hyperresearch
- DeepSeek Search and Fetch API vs Linkup
- Exa API + MCP vs Hyperresearch
- Exa API + MCP vs Linkup
- Firecrawl MCP vs Hyperresearch
- Firecrawl MCP vs Linkup
- 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 Linkup
- Linkup vs Mojeek Web Search API
- Linkup vs NewsCatcher
- Linkup vs Parallel Search and Task APIs
- Linkup vs Perplexity Search API
- Linkup vs SearchAPI.io
- Linkup vs SerpApi
- Linkup vs Serper
- Linkup vs SERPHouse
- Linkup vs SerpKite
- Linkup vs SpecStream
- Linkup vs Tavily API + MCP
- Linkup vs TinyFish Search
- Linkup vs Valyu
- Linkup vs You.com APIs
- Arcmira vs Hyperresearch
- Arcmira vs Linkup
- Grep AI vs Hyperresearch
- Grep AI vs Linkup
- Hyperresearch vs Liner Search MCP
- Hyperresearch vs NewsCatcher
- 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 Linkup
- Fetch (MCP reference server) vs Hyperresearch
- Fetch (MCP reference server) vs Linkup
Machine-readable
- This page as Markdown
/compare/hyperresearch-vs-linkup.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hyperresearch.json·/api/v1/tools/linkup.json - From a terminal
anchor compare hyperresearch linkup(the CLI) - Over MCP
compare_tools {"a": "hyperresearch", "b": "linkup"}at/mcp, no key