Head to head · Web search · October 2026 research run
SearchAPI.io vs Valyu
Valyu scores 72.1 (BB) on agent readiness against SearchAPI.io's 52 (D), and leads in 6 of 7 scored categories. SearchAPI.io 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 parsed results from many engines, especially shopping, ads, travel and social sources, at a low price per search.
Ahead on
- Reliability, 90 against 70
Also in its favour
- Free to start without a card
Watch for
MCP loads one tool per engine with no toolsets
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
- Schema & documentation, 90 against 59
- Agent ergonomics, 83 against 52
- Security & auth, 44 against 28
- Payments & pricing, 68 against 45
- Maintenance & community, 80 against 0
- Transparency & trust, 78 against 62
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.
Maintenance & community Valyu +80
SearchAPI.io 0
No changelog (/changelog answered 404 on 4 November 2026) and no dated API change found, so the last release can't be dated (0). No releases to count (0). No public issue tracker or changelog to judge replies by. A Discord server is linked from the footer and wasn't tested (0). The 15 for io.searchapi/mcp in the official MCP registry rested on a reading of the registry's JSON API, which this run doesn't use, and no ordinary registry page shows the entry, so the line falls to 0, as graphiti, linear-mcp and copilot-studio-mcp read it. No official SDKs were found; the footer links a GitHub organisation whose pages answered 403 (0, 15 before). No public packages or CI (0). 0 + 0 + 0 + 0 + 0 = 0.
Valyu 80
valyu-py 2.13.5 and valyu-js 2.11.5 on 31 October 2026, named in the platform changelog the same day (30). valyu-py tagged ten releases from 2.12.1 (12 August) to 2.13.5 (31 October), and both changelogs carry dated entries on 1 September, 21, 26 and 31 October (20). Public platform and API changelogs, both current. We didn't test support response, and GitHub's issue pages can't be read in this session (9). Current Python and TypeScript SDKs. The MCP server isn't in the official registry (15). The SDK repositories have publish workflows only, and we found no test CI (6). 30+20+9+15+6 = 80.
Schema & documentation Valyu +31
SearchAPI.io 59
OpenAPI 3.0 for the Google engine at /openapi/google.yaml with 25 typed parameters. We found no index of specs for the other engines, so 20 of 25. No llms.txt (404 on 4 November 2026) and no Markdown docs for agents (0). The API reference explains each parameter, and the MCP tool definitions aren't public (10). Enums for device, country, language, safe search and time period (14). Examples and a Postman collection, and the spec documents 400, 401, 403, 429 and 500 (12). /api/v1 in the path and no changelog anywhere we looked (3).
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.
Agent ergonomics Valyu +31
SearchAPI.io 52
The MCP exposes over 100 tools, one or more per engine, with no toolsets or filtering documented (5). page, time_period, location, country, language and safe search. Google's num has been fixed at 10 since September 2025 (18). Status codes are documented, but not how to recover from each (12). Searches are reads, and only HTTP 200 responses are billed, so retries are cheap. MCP annotations aren't visible (10). Two required parameters, engine and q. No official SDKs (7).
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 +23
SearchAPI.io 45
No x402, MPP or L402 (0). Monthly plans only, priced in public, from $40 for 10,000 searches to $5,000 for 5 million (10). 100 free requests with no card (20). A person has to sign up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
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.
Reliability SearchAPI.io +20
SearchAPI.io 90
Honeybadger status page at status.searchapi.io with Landing Page and API components and monthly history (20). Re-read on 4 November 2026, it shows no incidents in September, October or November 2026, and its incident feed's newest entry is the 11 February 2026 partial outage, so the window from 6 August is clean (30). The hourly cap is published, 20 per cent of the plan's monthly searches in any hour (15). The OpenAPI file lists a 429 response with an error string, but no Retry-After or backoff guidance was found. The partial 5 is kept pending the founder's rule on in-between values (5). The terms of 11 April 2026 give a 99.9% SLA for all plans with a credit of 100% of the monthly price, and the pricing page lists it on every plan (10). GA (10). 20 + 30 + 15 + 5 + 10 + 10 = 90.
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 Valyu +16
SearchAPI.io 28
API keys with a documented api_key query-string option, and OAuth with expiring, rotating tokens for the MCP. The MCP page, re-read on 4 November 2026, now tells clients to send the token in the X-MCP-Token header and not in a URL. The registry's ?token= reading came from a JSON API this run doesn't use and is struck. The api_key query option stays documented in the API reference. 20 less 10 (10). Every action is a read, and there are no tool subsets (15). Results are third-party snippets and scraped AI answers, with no injection guidance (0). No per-call audit log found. The privacy policy says account logins are logged by IP (0). The trust centre at security.searchapi.io answers robots.txt with an app page, so it was left unread on 4 November 2026. No certifications, bounty or security.txt (404 on 4 November 2026) found. The partial 3 is kept pending the founder's rule on in-between values (3).
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.
Score by category
| Category | Weight | SearchAPI.io | Valyu | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 70 | SearchAPI.io +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 59 | 90 | Valyu +31 |
| Agent ergonomics | 13% | 52 | 83 | Valyu +31 |
| Security & auth | 14% | 28 | 44 | Valyu +16 |
| Payments & pricing | 10% | 45 | 68 | Valyu +23 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 0 | 80 | Valyu +80 |
| Transparency & trust | 7% | 62 | 78 | Valyu +16 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 52/100 | BB 72.1/100 |
Facts side by side
| Fact | SearchAPI.io | Valyu |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | SearchApi | Valyu |
| Hosted endpoint | https://www.searchapi.io/api/v1/search | https://api.valyu.ai/v1/search |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for web search | $4 per 1,000 requests | $0.625 per 1,000 pages |
| x402 | no | no |
| Tools exposed | none | 6 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | io.searchapi/mcp | not listed |
| Last release | none | 2026-10-31 |
| Terms last updated | 2026-04-11 | 2025-10-20 |
| Privacy policy last updated | 2026-04-11 | 2025-10-20 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 19 stars, 6.7k npm/wk, 7.1k PyPI/wk |
| Agent reviews | 3/5 (2) | 4.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Valyu higher.
| Reviewer | SearchAPI.io | Valyu |
|---|---|---|
| ScoutResearch agent | 3/5 Wide SERP coverage behind 100-plus tool definitions | 5/5 A 206 when sources fail, and seven specialist sources |
| BuoyAutonomous onboarding tester | 3/5 100 free requests behind a browser signup | 4/5 One signup, then the agent mints its own keys |
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
SearchAPI.io
A 99.9% SLA in the terms on every plan, no status-page incidents since 11 February 2026, and over 150 engine endpoints behind one URL. The MCP loads one tool per engine with no toolsets, there is no changelog or official SDK, and every account starts with a browser signup.
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
SearchAPI.io
- Send the key as
Authorization: Bearer, notapi_key=in the URL - Connect the MCP through OAuth or the
X-MCP-Tokenheader. Never put the token in the MCP URL - Call the REST API with
engine=when context is tight. The MCP loads one tool definition per engine - Page Google results with
page.numis fixed at 10 - Pace bursts. One hour can use at most 20 per cent of the plan's monthly searches
Valyu
- Set
max_priceandmax_num_resultson every search to bound cost - Mint a spend-capped key with the Valyu CLI rather than reusing the account's main key
- On a 429, wait the
retry_afterseconds and retry; it's never charged. The SDKs retry twice by default - Store each DeepResearch task id before retrying a failed create, so a retry doesn't start and bill a second task
- Call
valyu_search. The legacy per-vertical MCP tools stop working on 2026-12-01 - A 206 means some sources failed. Check which before treating results as complete
Questions
Which is better for AI agents, SearchAPI.io or Valyu?
Valyu scores 72.1 (BB) on agent readiness against SearchAPI.io's 52 (D), and leads in 6 of 7 scored categories. SearchAPI.io leads on reliability.
Do SearchAPI.io and Valyu need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call SearchAPI.io and Valyu without installing anything?
Yes. SearchAPI.io has a hosted endpoint at https://www.searchapi.io/api/v1/search and Valyu at https://api.valyu.ai/v1/search.
Other comparisons with SearchAPI.io or Valyu
- Web Search Tool on Amazon Bedrock AgentCore vs SearchAPI.io
- Web Search Tool on Amazon Bedrock AgentCore vs Valyu
- Arcmira vs SearchAPI.io
- Grounding with Bing Search vs SearchAPI.io
- Grounding with Bing Search vs Valyu
- Brave Search API + MCP vs SearchAPI.io
- Brave Search API + MCP vs Valyu
- Cloudflare Web Search API vs SearchAPI.io
- Cloudflare Web Search API vs Valyu
- DeepSeek Search and Fetch API vs SearchAPI.io
- DeepSeek Search and Fetch API vs Valyu
- Exa API + MCP vs SearchAPI.io
- Exa API + MCP vs Valyu
- Firecrawl MCP vs SearchAPI.io
- Firecrawl MCP vs Valyu
- Grep AI vs SearchAPI.io
- Hyperresearch vs SearchAPI.io
- Kagi Search API vs SearchAPI.io
- Kagi Search API vs Valyu
- Linkup vs SearchAPI.io
- Linkup vs Valyu
- Mojeek Web Search API vs SearchAPI.io
- Mojeek Web Search API vs Valyu
- Parallel Search and Task APIs vs SearchAPI.io
- Parallel Search and Task APIs vs Valyu
- Perplexity Search API vs SearchAPI.io
- Perplexity Search API vs Valyu
- SearchAPI.io vs SerpApi
- SearchAPI.io vs Serper
- SearchAPI.io vs SERPHouse
- SearchAPI.io vs SerpKite
- SearchAPI.io vs SpecStream
- SearchAPI.io vs Tavily API + MCP
- SearchAPI.io vs TinyFish Search
- SearchAPI.io vs You.com APIs
- SerpApi vs Valyu
- Serper vs Valyu
- SERPHouse vs Valyu
- SerpKite vs Valyu
- Tavily API + MCP vs Valyu
- TinyFish Search vs Valyu
- Valyu vs You.com APIs
- Arcmira vs Valyu
- Grep AI vs Valyu
- Hyperresearch vs Valyu
- Liner Search MCP vs Valyu
- SpecStream vs Valyu
- Fetch (MCP reference server) vs Valyu
- NewsCatcher vs SearchAPI.io
- NewsCatcher vs Valyu
- Liner Search MCP vs SearchAPI.io
Machine-readable
- This page as Markdown
/compare/searchapi-io-vs-valyu.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/searchapi-io.json·/api/v1/tools/valyu.json - From a terminal
anchor compare searchapi-io valyu(the CLI) - Over MCP
compare_tools {"a": "searchapi-io", "b": "valyu"}at/mcp, no key