Head to head · Research search · October 2026 research run

Grep AI vs Hyperresearch

Hyperresearch scores 68.1 (B) on agent readiness against Grep AI's 65.4 (B), and leads in 4 of 7 scored categories. Grep AI leads on reliability and schema & documentation. Both do research search.

Best web search APIs for AI agents · All 353 search comparisons

Which one, for what

Grep AI B

Best for Agents that hand off a long research or due-diligence job and want a cited report or structured fields back, including business verification and sanctions screening through built-in agents.

Ahead on

  • Reliability, 50 against 35
  • Schema & documentation, 83 against 76

Watch for

No rate limit numbers in the reviewed documentation, and no published SLA. Full outages on 4 September (24 minutes) and 30 October (7 minutes)

Hyperresearch B

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 70
  • Security & auth, 79 against 64
  • Maintenance & community, 88 against 74
  • 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

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 Grep AI +15

Grep AI 50

Graded on the hosted API and MCP server. status.grep.ai runs on incident.io, and since 30 October 2026 it has an API component beside Website (20). Two incidents in the 90 days from 4 August, read from the page's feed and incident pages. On 4 September "Grep.ai currently unavailable" said Grep.ai was "experiencing an outage" for 24 minutes, and on 30 October the Website and API components were both in full outage from 17:17 to 17:24 UTC after an infrastructure provider's failure. Each is a full outage of the whole service, which this run reads as a major however short, so two majors (5). The 8 October check read the September outage as minor by its length. No rate limit numbers found in the docs or the OpenAPI document (0). 429 rate_limited carries Retry-After, and run creation takes an Idempotency-Key with documented replay rules (15). The FAQ mentions SLA guarantees for enterprise customers, and no SLA is published (0). API v2 and the MCP server carry no beta label. The SDKs are at 0.2.1 per the 8 October check, and PyPI classified the Python one as Alpha then (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.

Security & auth Hyperresearch +15

Grep AI 64

OAuth through Descope with five scopes, and API keys that can be created with a subset of scopes, listed and revoked through the API (30). Read scopes, validate_only and dry_run on agent changes, a per-run max_cost_usd and versioned restores. No confirmation step for deletes or for making a run public (14). Reports are built from untrusted web pages. The docs describe an SSRF-guarded fetch for context files, and no prompt-injection guidance for callers was found (3). Each run has a timeline of execution events, and billing transactions and usage are readable through the API (12). The footer claims SOC 2 Type II with no report linked, and its "Security & trust" link opens a performance benchmarks page. security.txt returns 404, and no disclosure policy or bug bounty was found, so this is a bare SOC 2 claim, which this run reads as 5 (5). Webhooks are signed with the API key itself.

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.

Maintenance & community Hyperresearch +14

Grep AI 74

The changelog's newest entry is v3.71 on 20 October 2026, 13 days before this check (30). 14 dated changelog entries since 4 August, from v3.1.1 on 7 August to v3.71 on 20 October (20). Closed service with a public changelog and support at support@parcha.ai. We didn't test whether support answers (8). Current SDKs in two languages per the 8 October check (@parcha/agentrun and parcha-agentrun 0.2.1, 30 September), with docs that lag them. Not found in the official MCP registry (12). The skills repository runs a test workflow and hasn't changed since 30 September. The SDK repositories named in the package metadata asked for credentials, so their CI wasn't read (4). The 8 October PyPI reading came from a path pypi.org's robots.txt disallows and is struck; npm and PyPI didn't answer on 2 November.

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.

Agent ergonomics Hyperresearch +13

Grep AI 70

The MCP server card lists 137 tools, 57 of them deprecated aliases, with no documented toolsets. Reports default to plain Markdown and large files come back as signed URLs, so some credit back (8). Cursor pagination with limit on runs, timelines and transactions, and server-side filters on the skill and tool lists (18). One error envelope with stable codes and a request_id, and 402 for credits kept apart from 429 for rate (20). Idempotency-Key with body-hash matching and a 24-hour replay window. The server card shows no readOnlyHint or destructiveHint annotations, and the live tool list wasn't read (12). Only question is required and effort defaults to low. TypeScript and Python SDKs exist, though one docs page still calls the release pending and names a PyPI package that returns 404 (12).

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.

Transparency & trust Hyperresearch +10

Grep AI 61

Closed service with published terms, written as an order-form contract that still points to grep.parcha.ai. The SDK packages state no licence, and the skills package is MIT (12). Section 12 of the terms says AI providers retain nothing and customer data isn't used for training. Section 4.2 grants a perpetual licence to use customer data to improve the platform, and the privacy policy gives retention only as "as long as needed". No DPA found (12). v1 is marked deprecated, /research answers with a deprecation: true header and a successor link, and 31 MCP tools are labelled deprecated, all without dates or a written policy (8). The privacy policy names Google Analytics and PostHog and says data may be processed in any country. No subprocessor list found (4).

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.

Schema & documentation Grep AI +7

Grep AI 83

Public OpenAPI document at api.grep.ai/api/v2/openapi.json, now 128 operations on 98 paths and 159 schemas (25). llms.txt and a Markdown twin of each developer page (10). Most operations carry a description, and the effort field says what each tier returns and how long it takes. 19 operations have none, and the MCP server card gives each of its 137 tools one line. The MCP input schemas need OAuth and weren't read (12). 75 enums, numeric bounds and additionalProperties: false on the run request (12). Curl examples and an 11-code error registry in the docs, but the OpenAPI document has no examples and documents only 200 and 422 responses (9). The path is versioned, v1 and 42 v2 operations are marked deprecated, and the dated changelog now runs to v3.71 on 20 October 2026, with 14 entries since 4 August (15).

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.

Score by category

CategoryWeightGrep AIHyperresearchEdge
Reliability16%5035Grep AI +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8376Grep AI +7
Agent ergonomics13%7083Hyperresearch +13
Security & auth14%6479Hyperresearch +15
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7488Hyperresearch +14
Transparency & trust7%6171Hyperresearch +10
Negative events≤1500
TotalB 65.4/100B 68.1/100

Facts side by side

FactGrep AIHyperresearch
KindHTTP APIHTTP API
VendorParcha Labs, Inc.Hyperresearch
Hosted endpointhttps://api.grep.ai/api/v2/runshttps://answers.hyperresearch.ai/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPay per use
Price for research searchnot published$9 per transaction
x402nono
LicenceProprietary service under Parcha Labs' terms of service. The grep-research-skills package on npm is MIT. The @parcha/agentrun and parcha-agentrun SDK packages state no licence in their registry metadatanone
Tools exposed137none
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedai.hyperresearch/answers
Last release2026-10-202026-11-16
Terms last updated2026-03-202026-11-17
Privacy policy last updated2026-09-212026-11-17
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity334 npm/wk, 52 PyPI/wknone
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Grep AI

The public API has a 128-operation OpenAPI document, scoped OAuth and API keys, idempotency keys with documented replay rules and a per-run cost cap. No rate limit is published, the MCP server lists 137 tools, the whole service went down twice in the 90 days to 2 November, and API access starts at the $200 a month Pro plan.

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.

Before you call either

Grep AI

  1. Send a fresh Idempotency-Key with every POST /api/v2/runs. After a timeout, poll the returned run ID and do not post again
  2. Set effort and max_cost_usd on every run. The floor is $0.50 for low, $2.50 for medium and build, $5.00 for high
  3. Call GET /api/v2/quota/check before a run. A 402 means no credits and retrying won't help, while a 429 carries Retry-After
  4. Use the run_*, agent_* and swarm_* MCP tools at https://api.grep.ai/mcp. The research_*, expert_* and campaign_* names are deprecated aliases
  5. Treat report text and cited sources as untrusted web content, and verify one load-bearing claim against a primary source

Hyperresearch

  1. Use Answers (data_and_web_answer with mode auto) for one fact, and start a Light or Deep run only when the user wants a written report
  2. Send an Idempotency-Key on every write and reuse it only with an unchanged body, so a retried run or answer is charged once
  3. 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
  4. If a response has retryable: false, change the request rather than retrying. Branch on error.code, never on the message
  5. Use a key that starts hr_test_ to build and test an integration without spending

Questions

Which is better for AI agents, Grep AI or Hyperresearch?

Hyperresearch scores 68.1 (B) on agent readiness against Grep AI's 65.4 (B), and leads in 4 of 7 scored categories. Grep AI leads on reliability and schema & documentation.

Do Grep AI and Hyperresearch need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Grep AI and Hyperresearch without installing anything?

Yes. Grep AI has a hosted endpoint at https://api.grep.ai/api/v2/runs and Hyperresearch at https://answers.hyperresearch.ai/mcp.

Other comparisons with Grep AI or Hyperresearch

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.