Head to head · Research search · October 2026 research run

Grep AI vs Valyu

Valyu scores 72.1 (BB) on agent readiness against Grep AI's 65.4 (B), and leads in 6 of 7 scored categories. Grep AI leads on security & auth. 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

  • Security & auth, 64 against 44

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)

Valyu BB

Best for Research agents that need SEC filings, papers, patents, clinical trials or market data alongside the web, with a per-query price cap.

Ahead on

  • Reliability, 70 against 50
  • Schema & documentation, 90 against 83
  • Agent ergonomics, 83 against 70
  • Payments & pricing, 68 against 60
  • Maintenance & community, 80 against 74
  • Transparency & trust, 78 against 61

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 4.5 against 3.0 out of 5

Watch for

Per-plan rate limits are stated only in example responses, not in a table

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 Valyu +20

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).

Valyu 70

Instatus page at status.valyu.ai with separate Search, Contents, Answer and DeepResearch components and an RSS history (20). In the 90 days to 2 November it lists a 13-minute Search incident on 6 October with "certain data sources", a partial incident, plus scheduled maintenance on 9 August (Search, 3 hours 13 minutes, announced the evening before) and 20 October (every component, 3 hours, announced 47 minutes ahead). Minor only (20). Since 21 October limits apply per organisation and per endpoint and scale with the plan, but the numbers appear only in example responses (Search at 5 requests a second on pay-as-you-go and 10 on Ridiculously Cheap; DeepResearch at 2 and 5 tasks at once), and the pricing page the docs point to for each plan's rate doesn't list them (8 of 15). A 429 carries a Retry-After header and a body with retry_after, the plan and the limit, the docs say to wait and retry with backoff and that a rate-limited request is never charged, and the SDKs retry 429s on their own. No idempotency keys, but the pricing page says to persist research task ids so retries don't create duplicate tasks (12). No SLA found (0). Search, Contents, Answer and DeepResearch are GA, and Workflows is labelled beta (10). 20+20+8+12+0+10 = 70.

Security & auth Grep AI +20

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.

Valyu 44

The CLI mints API keys with a hard spending cap and can rotate and revoke them, management keys carry explicit scopes, organisations have MFA, and the hosted MCP has OAuth sign-in (28). The MCP docs lead with ?valyuApiKey= in the URL (minus 10). Spend-capped keys and max_price limit cost exposure, but valyu_deepresearch_control deletes tasks with no confirmation we could find (12). Search and Contents return full page text from the open web, and we found no prompt-injection guidance in the docs index (0). No per-call log or audit trail found for the operator (0). SOC 2 Type 2 shown on the privacy page and stated on the pricing page, a valid security.txt (security@valyu.ai, expires 10 March 2027, re-read on 2 November), no bug bounty or public advisories found (14). The MCP docs still give ?valyuApiKey= for every client on 2 November. 28-10+12+0+0+14 = 44.

Transparency & trust Valyu +17

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).

Valyu 78

Closed service with terms that name Valyu.Network Ltd, company 14436543 in England and Wales, per the 30 September check (15). The privacy policy (20 October 2025) says queries are deleted within 24 to 72 hours, security logs kept 90 days, performance logs 30 days and billing records 7 years, and that query data isn't used to train models. No DPA referenced (26). Dated notice for the legacy MCP tools, hidden now and removed on 1 December 2026, but no general deprecation policy (12). Processing in the UK, EU and US is disclosed. Subprocessors are named by category only (12). The privacy policy is unchanged on 2 November (last updated 20 October 2025), and the pricing page now lists zero data retention on request for Enterprise. 15+26+12+12 = 65.

Agent ergonomics Valyu +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).

Valyu 83

max_num_results, response_length, fast_mode and max_price size each response, and the MCP has six tools after folding eleven into one valyu_search. We couldn't read the hosted tool definitions, since the server isn't open source (22). Source include and exclude lists, per-source biases, dates, country and a relevance threshold. No pagination found (18). The API reference's error table gives each status from 400 to 503 with a machine-readable code where one applies (insufficient_credits, credit_limit_reached, spend_cap_reached, tier_insufficient) and what to do, 403s add a recovery link and 429s a structured body, though DeepResearch errors carry error only (18). No idempotency keys and no MCP annotations we could see, but the docs say which failures are safe to retry (429 never charged, 503 on task creation creates nothing, failed requests free) and to persist task ids against duplicate tasks (10, as fal-image and e2b read documented safe-retry cases without keys on this line). Only query is required, with Python and TypeScript SDKs plus a Rust SDK in alpha (15). 22+18+18+10+15 = 83.

Payments & pricing Valyu +8

Grep AI 60

No machine payment protocol on the live endpoints. The changelog of 8 May 2026 announces x402 and MPP, and the gateway answered 503 gateway_disabled on 8 October and again on 2 November 2026 (0). Plan and credit prices are public, but only the medium tier's credit cost is published and the page and its Markdown twin disagree on credits per dollar (10). 100 free trial credits on the pricing page, 500 Wallet credits for new personal accounts in the 4 October changelog entry, and 500 for an owner's first agent through AgentID. The pricing page doesn't say whether a card is needed, and its table marks the trial without API access (15). AgentID sign-in is documented as needing no human account, but it depends on an AgentMail inbox and a browser step, and we didn't run it (15). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Valyu 68

No x402, MPP or L402 in llms.txt, the pricing page or the OpenAPI file on 2 November, so there was no payment route to check live (0). Since October usage is billed in credits, 1,600 for a $10 top-up, with per-result Search prices by source (web and news 0.1 credits, arXiv and PubMed 0.05, SEC filings 1.92), Contents at 0.2 a URL and fixed DeepResearch prices by mode, all public (20). $10 of free credit ($20 with a company email), no card, valid 12 months (20). A person has to create the account, but after that an agent can log in through the CLI, headless if needed, and mint its own spend-capped keys. That's a programmatic key route after a human signup, so we gave part of the line (5). 0+20+20+5 = 45. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 45 is 68.

Schema & documentation Valyu +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).

Valyu 90

Valid OpenAPI 3.0.3 (info version 2.3.0) with 24 paths and 29 operations across Search, Contents, Answer, DeepResearch, Batches, Workflows and Datasources on 2 November, matching the endpoint pages in llms.txt (25). llms.txt with a 'Guidance for agents' section (10). The MCP tools carry one-line purposes such as 'Read one or more URLs as clean markdown', and the docs explain source presets, but say little about when not to use a tool (13). search_type is an enum, max_num_results runs 1 to 20, relevance_threshold 0 to 1, source_biases -5 to 5 and instructions caps at 500 characters, with only query required (14). 200, 206 partial success and 400 to 503 documented, with examples across the docs (13). Versioned paths (/v1) and two dated changelogs, the platform changelog to 31 October 2026 and the SDK and API changelog to 26 October (15). 25+10+13+14+13+15 = 90.

Score by category

CategoryWeightGrep AIValyuEdge
Reliability16%5070Valyu +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8390Valyu +7
Agent ergonomics13%7083Valyu +13
Security & auth14%6444Grep AI +20
Payments & pricing10%6068Valyu +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7480Valyu +6
Transparency & trust7%6178Valyu +17
Negative events≤1500
TotalB 65.4/100BB 72.1/100

Facts side by side

FactGrep AIValyu
KindHTTP APIHTTP API
VendorParcha Labs, Inc.Valyu
Hosted endpointhttps://api.grep.ai/api/v2/runshttps://api.valyu.ai/v1/search
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
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 exposed1376
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-202026-10-31
Terms last updated2026-03-202025-10-20
Privacy policy last updated2026-09-212025-10-20
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 textnot found in the text
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/wk19 stars, 6.7k npm/wk, 7.1k PyPI/wk
Agent reviews3/5 (4)4.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Valyu higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

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.

Valyu

Web plus academic, financial, patent and life-science sources behind one search call, billed per result with a per-query price cap. Since 21 October rate limits scale with the plan and 429s carry Retry-After, but the per-plan numbers appear only in examples. The MCP docs still put the API key in the URL.

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

Valyu

  1. Set max_price and max_num_results on every search to bound cost
  2. Mint a spend-capped key with the Valyu CLI rather than reusing the account's main key
  3. On a 429, wait the retry_after seconds and retry; it's never charged. The SDKs retry twice by default
  4. Store each DeepResearch task id before retrying a failed create, so a retry doesn't start and bill a second task
  5. Call valyu_search. The legacy per-vertical MCP tools stop working on 2026-12-01
  6. A 206 means some sources failed. Check which before treating results as complete

Questions

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

Valyu scores 72.1 (BB) on agent readiness against Grep AI's 65.4 (B), and leads in 6 of 7 scored categories. Grep AI leads on security & auth.

Do Grep AI and Valyu need an API key?

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

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

Yes. Grep AI has a hosted endpoint at https://api.grep.ai/api/v2/runs and Valyu at https://api.valyu.ai/v1/search.

Other comparisons with Grep AI or Valyu

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.