Head to head · Web search · October 2026 research run
Hyperresearch vs Mojeek Web Search API
Hyperresearch scores 68.1 (B) on agent readiness against Mojeek Web Search API's 37.6 (F), and leads in 6 of 7 scored categories. Mojeek Web Search API leads on reliability. Both do web 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
- Schema & documentation, 76 against 29
- Agent ergonomics, 83 against 66
- Security & auth, 79 against 15
- Payments & pricing, 60 against 30
- Maintenance & community, 88 against 10
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
Best for Agents and products that want a second, independent index beside Google-derived results, or European data handling with no sub-processors.
Ahead on
- Reliability, 45 against 35
Watch for
The API key is documented only as a URL query parameter, and rotating a key means emailing the API team
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.
Maintenance & community Hyperresearch +78
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.
Mojeek Web Search API 10
Read for a closed service. No API changelog, release notes or dated API change were found, and the blog's posts since 2024 are about search in general, so the last change can't be dated (0). No dated changes in the 90 days from 8 August (0). A staff member answered API questions on the community forum within a day in December 2025 and October 2026, and support is by email; no public changelog (10 of 15). No official SDKs or MCP server (0). No public packages or CI to measure (0). 0 + 0 + 10 + 0 + 0 = 10.
Security & auth Hyperresearch +64
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.
Mojeek Web Search API 15
One key per account, documented only as the api_key query parameter, and rotation or revocation is by email to the API team (a staff reply of 22 October 2026 on the community forum asks for the key's last 8 digits). One all-powerful key (10) less 10 for the key in the URL (0). Search is read-only and there is nothing to write, but no scoped or restricted key (10 of 20). Results are third-party titles and snippets, with no prompt-injection guidance found (0). No audit log or per-call usage view was found in the docs; the FAQ mentions budget alerts on the account (0 of 15). security.txt names security@mojeek.com, with no Expires field. No bug bounty, disclosure policy, SOC 2 or ISO 27001 found; the API page claims compliance with European rules such as the EU Data Act without a certification (5 of 20). 0 + 10 + 0 + 0 + 5 = 15.
Schema & documentation Hyperresearch +47
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.
Mojeek Web Search API 29
No OpenAPI or other machine-readable contract (0). No llms.txt (404) and no Markdown pages for agents (0). The parameters page states what each parameter does, with notes on when not to use reg and clufmt, but nothing on when another endpoint fits better (12 of 20). Every parameter has a type, defaults and valid ranges (tlen 0 to 127, dlen 0 to 511, rbb and lbb 1 to 100, up to 25 domains), though reg is called an enum without listing its values (11 of 15). One curl example and annotated JSON and XML response formats; errors appear only as a status string with one example (6 of 15). No API version, changelog or dated release notes, and the quickstart and the parameters page give different hosts (0). 0 + 0 + 12 + 11 + 6 + 0 = 29.
Payments & pricing Hyperresearch +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.
Mojeek Web Search API 30
No x402, MPP or L402 (0). Per-request prices published without login, £2 and £3 per 1,000 requests (20). The FAQ says a free credit comes with the Startup plan, but a bank card is required to open an account (0). A person signs up in a browser and adds a card (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.
Agent ergonomics Hyperresearch +17
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.
Mojeek Web Search API 66
Responses can be sized with t (up to 10, 40 or 100 results by plan), tlen, dlen and opt-in date and size fields (22 of 25). s for paging, since and before, site, included and excluded domains, region and language boosting and safe search (20). Errors are a free-text status with no documented codes, which an agent can't branch on reliably (5 of 20). Searches only read, so a retry is safe, but no page says whether failed or empty requests are billed (12 of 20). Only q and api_key are required, with recommended values for the boosts. No official SDK in any language (7 of 15). 22 + 20 + 5 + 12 + 7 = 66.
Reliability Mojeek Web Search API +10
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.
Mojeek Web Search API 45
Read with the hosted lines. status.mojeek.com is a Site24x7 StatusIQ page with Search, Website, Blog and Community components. It is drawn by script, so only its RSS feed could be read, which shows each component's current state (Search operational since 7 September 2026) and no incident entries (15 of 20). No readable incident history (5). Rate limits are published per plan, 5 a second and 100,000 a day on Startup, 10 a second and 400,000 a day on Business (15). Over the daily limit the JSON status reads 'ERROR: Daily Limit Reached'; no HTTP 429, Retry-After or backoff guidance was found (0). No SLA, and the API terms say the service is provided as is and may be interrupted without notice (0). Generally available, with only the lr parameter marked beta (10). 15 + 5 + 15 + 0 + 0 + 10 = 45.
Score by category
| Category | Weight | Hyperresearch | Mojeek Web Search API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 45 | Mojeek Web Search API +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 29 | Hyperresearch +47 |
| Agent ergonomics | 13% | 83 | 66 | Hyperresearch +17 |
| Security & auth | 14% | 79 | 15 | Hyperresearch +64 |
| Payments & pricing | 10% | 60 | 30 | Hyperresearch +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 10 | Hyperresearch +78 |
| Transparency & trust | 7% | 71 | 68 | Hyperresearch +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.1/100 | F 37.6/100 |
Facts side by side
| Fact | Hyperresearch | Mojeek Web Search API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Hyperresearch | Mojeek Limited |
| Hosted endpoint | https://answers.hyperresearch.ai/mcp | no (local only) |
| Transports | Streamable HTTP | |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| Price for web search | $0.05 per call | $2.68 per 1,000 requests |
| x402 | no | no |
| Tools exposed | none | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | ai.hyperresearch/answers | not listed |
| Last release | 2026-11-16 | none |
| Terms last updated | 2026-11-17 | no date given |
| Privacy policy last updated | 2026-11-17 | 2022-02-02 |
| 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 | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
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.
Mojeek Web Search API
Mojeek sells search over its own independent index at published per-request prices, with region, language, date and domain controls and storage rights on the Business plan. The key travels only in the URL, rotation is by email, a card is needed to start, and there is no OpenAPI, changelog, 429 handling or SLA.
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
Mojeek Web Search API
- Send
fmt=json, since the default response is XML - Read
response.statuson every call; a daily limit shows as 'ERROR: Daily Limit Reached' rather than an HTTP error - Set
lb,lbb,rbandrbbas the quickstart recommends, or results lean to no language or region - Keep the key out of logs and shared URLs, since it travels in the query string
- On the Startup plan, don't keep results for more than an hour
Questions
Which is better for AI agents, Hyperresearch or Mojeek Web Search API?
Hyperresearch scores 68.1 (B) on agent readiness against Mojeek Web Search API's 37.6 (F), and leads in 6 of 7 scored categories. Mojeek Web Search API leads on reliability.
Do Hyperresearch and Mojeek Web Search API need an API key?
Hyperresearch takes an API key or an OAuth sign-in. Mojeek Web Search API needs an API key.
Can an agent call Hyperresearch and Mojeek Web Search API without installing anything?
Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp. No hosted endpoint is listed for Mojeek Web Search API.
Other comparisons with Hyperresearch or Mojeek Web Search API
- Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch
- Web Search Tool on Amazon Bedrock AgentCore vs Mojeek Web Search API
- Arcmira vs Mojeek Web Search API
- Grounding with Bing Search vs Hyperresearch
- Grounding with Bing Search vs Mojeek Web Search API
- Brave Search API + MCP vs Hyperresearch
- Brave Search API + MCP vs Mojeek Web Search API
- Cloudflare Web Search API vs Hyperresearch
- Cloudflare Web Search API vs Mojeek Web Search API
- DeepSeek Search and Fetch API vs Hyperresearch
- DeepSeek Search and Fetch API vs Mojeek Web Search API
- Exa API + MCP vs Hyperresearch
- Exa API + MCP vs Mojeek Web Search API
- Firecrawl MCP vs Hyperresearch
- Firecrawl MCP vs Mojeek Web Search API
- Grep AI vs Mojeek Web Search API
- Hyperresearch vs Kagi Search API
- Hyperresearch vs SearchAPI.io
- Hyperresearch vs SerpApi
- Hyperresearch vs Serper
- Hyperresearch vs SERPHouse
- Hyperresearch vs SerpKite
- Kagi Search API vs Mojeek Web Search API
- Linkup vs Mojeek Web Search API
- Mojeek Web Search API vs NewsCatcher
- Mojeek Web Search API vs Parallel Search and Task APIs
- Mojeek Web Search API vs Perplexity Search API
- Mojeek Web Search API vs SearchAPI.io
- Mojeek Web Search API vs SerpApi
- Mojeek Web Search API vs Serper
- Mojeek Web Search API vs SERPHouse
- Mojeek Web Search API vs SerpKite
- Mojeek Web Search API vs SpecStream
- Mojeek Web Search API vs Tavily API + MCP
- Mojeek Web Search API vs TinyFish Search
- Mojeek Web Search API vs Valyu
- Mojeek Web Search API vs You.com APIs
- Arcmira vs Hyperresearch
- Grep AI vs Hyperresearch
- Hyperresearch vs Liner Search MCP
- Hyperresearch vs Linkup
- 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
- Fetch (MCP reference server) vs Hyperresearch
Machine-readable
- This page as Markdown
/compare/hyperresearch-vs-mojeek.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hyperresearch.json·/api/v1/tools/mojeek.json - From a terminal
anchor compare hyperresearch mojeek(the CLI) - Over MCP
compare_tools {"a": "hyperresearch", "b": "mojeek"}at/mcp, no key