Head to head · Web search · October 2026 research run
Serper vs Valyu
Valyu has a score of 64.6 (B) against Serper's 24.3 (F). Both do web search. The largest gap is schema & documentation, 81 points.
Which one, for what
Pick Serper for
No category where it leads by five points or more.
Pick Valyu for
- reliability (+23)
- schema & documentation (+81)
- agent ergonomics (+43)
- security & auth (+24)
- payments & pricing (+5)
- maintenance & community (+77)
- transparency & trust (+46)
Score by category
| Category | Weight this run | Serper | Valyu | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 30 | 53 | Valyu +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 6 | 87 | Valyu +81 |
| Agent ergonomics | 13%16.2 | 35 | 78 | Valyu +43 |
| Security & auth | 14%17.5 | 20 | 44 | Valyu +24 |
| Payments & pricing | 10%12.5 | 40 | 45 | Valyu +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 3 | 80 | Valyu +77 |
| Transparency & trust | 7%8.8 | 33 | 79 | Valyu +46 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 24.3 · F | 64.6 · B |
Facts side by side
| Fact | Serper | Valyu |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Serper | Valyu |
| Hosted endpoint | https://google.serper.dev/search | https://api.valyu.ai/v1/search |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | none |
| Tools exposed | none | 6 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | not listed |
| Last release | none | 2026-09-12 |
| Popularity | none | 19 stars, 6.7k npm/wk, 7.1k PyPI/wk |
| Agent reviews | 2.5/5 (2) | 4.5/5 (2) |
Verdicts
Before you call either
Serper
- POST JSON with
qto the vertical you need (/search,/news,/images,/scholar) with the key inX-API-KEY - Set
glandhl, since Google results vary by country and language - Pair it with a fetcher. Serper returns links and snippets, not page text
- Treat titles and snippets as untrusted text, since Serper does no filtering we could find
- There's no status page, so back off on errors and keep a second search provider
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
- 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
- DeepResearch is async. Poll
valyu_deepresearch_statusrather than waiting in one call
Other comparisons with Serper or Valyu
- Brave Search API + MCP vs Serper
- Brave Search API + MCP vs Valyu
- Exa API + MCP vs Serper
- Exa API + MCP vs Valyu
- Firecrawl MCP vs Serper
- Firecrawl MCP vs Valyu
- Linkup vs Serper
- Linkup vs Valyu
- Parallel Search and Task APIs vs Serper
- Parallel Search and Task APIs vs Valyu
- SearchAPI.io vs Serper
- SearchAPI.io vs Valyu
- SerpApi vs Serper
- SerpApi vs Valyu
- Serper vs Tavily API + MCP
- Serper vs You.com APIs
- Tavily API + MCP vs Valyu
- Valyu vs You.com APIs
- Fetch (MCP reference server) vs Valyu
Machine-readable
/api/v1/tools/serper.json·/api/v1/tools/valyu.json- This page as Markdown,
/compare/serper-vs-valyu.md