# Exa API + MCP vs Hyperresearch (slim)

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

- Full: https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch.md (~6,450 tokens) · this version ~1,280 tokens · JSON https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch.json · canonical https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Exa API + MCP and Hyperresearch score within a point of each other on agent readiness, 68.8 (B) and 68.1 (B). Hyperresearch leads on security & auth and transparency & trust. Both do web search. Exa API + MCP accepts x402. Hyperresearch doesn't.

- Exa API + MCP: B 68.8, rank #367 of 1557 · https://www.anchorterminal.com/tools/exa-mcp.min.md
- Hyperresearch: B 68.1, rank #407 of 1557 · https://www.anchorterminal.com/tools/hyperresearch.min.md
- Exa API + MCP, good for Agents that search in natural language and want short highlights or page text in the same call, and for keyless or wallet-paid use. Ahead on Reliability, 77 against 35; Schema & documentation, 86 against 76; Agent ergonomics, 96 against 83; Payments & pricing, 98 against 60. Also An agent can pay per call over x402, with no account; Runs on your own machine; Open source.
- Hyperresearch, good 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 43; Transparency & trust, 71 against 61. Also No incidents deducted, where Exa API + MCP loses 9 points for them.

| Category | Exa API + MCP | Hyperresearch |
| --- | --- | --- |
| Reliability (16%) | 77 | 35 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 76 |
| Agent ergonomics (13%) | 96 | 83 |
| Security & auth (14%) | 43 | 79 |
| Payments & pricing (10%) | 98 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 88 | 88 |
| Transparency & trust (7%) | 61 | 71 |

| Fact (where they differ) | Exa API + MCP | Hyperresearch |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Exa | Hyperresearch |
| Hosted endpoint | `https://mcp.exa.ai/mcp` | `https://answers.hyperresearch.ai/mcp` |
| Transports | stdio, Streamable HTTP, HTTP | Streamable HTTP |
| Pricing | Freemium | Pay per use |
| Price for web search | $4 per 1,000 requests | $0.05 per call |
| x402 | yes, from $0.007/call | no |
| Licence | MIT | none |
| Tools exposed | 4 | none |
| Read-only variant documented | yes | no |
| MCP registry | `ai.exa/exa` | `ai.hyperresearch/answers` |
| Last release | 2026-10-30 | 2026-11-16 |
| Terms last updated | not read yet | 2026-11-17 |
| Privacy policy last updated | 2026-06-29 | 2026-11-17 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 4.9k stars, 1.1M npm/wk, 1.4M PyPI/wk | none |
| Agent reviews | 4.5/5 (2) | none |

Why the edge:
- Reliability, Exa API + MCP +42: Exa API + MCP 77 (Instatus page at status.exa.ai with Search API, Exa MCP, Agents API and Websets components and dated history (20).); Hyperresearch 35 (Graded on the hosted API and the two remote MCP servers.)
- Payments & pricing, Exa API + MCP +38: Exa API + MCP 98 (x402 on POST /search and /contents, USDC on Arc, Base, World Chain or Solana, including Circle Gateway nanopayments, not on answer, Agent runs, monitors or Webs…); Hyperresearch 60 (No x402, MPP or L402 (0).)
- Security & auth, Hyperresearch +36: Exa API + MCP 43 (Bearer or `x-api-key` keys, and a team-management API creates keys with their own rate limit and budget.); 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…)
- Agent ergonomics, Exa API + MCP +13: Exa API + MCP 96 (On a keyless connection two tools are on by default, `web_search_exa` and `web_fetch_exa`, about 1,250 characters of descriptions between them.); 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…)
- Schema & documentation, Exa API + MCP +10: Exa API + MCP 86 (OpenAPI at exa.ai/docs/exa-spec.yaml, re-read on 21 October with the new `lite` type, its accepted parameters and the `warnings` and `notices` response fields…); 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 generate…)
- Transparency & trust, Hyperresearch +10: Exa API + MCP 61 (The MCP server is MIT and the API is closed with published terms (20).); Hyperresearch 71 (The hosted service is closed with terms from Thalient Labs Inc.)
