Head to head · Web search · October 2026 research run
SerpKite vs Valyu
Valyu scores 72.1 (BB) on agent readiness against SerpKite's 70.1 (BB), and leads in 3 of 7 scored categories. SerpKite leads on reliability and agent ergonomics. Both do web search.
Best web search APIs for AI agents · All 353 search comparisons
Which one, for what
SerpKite BB
Best for Agents that want Google results and the top pages as Markdown in one call at a low per-1,000 price, with spend caps per key.
Ahead on
- Reliability, 75 against 70
- Agent ergonomics, 97 against 83
Also in its favour
- Free to start without a card
Watch for
Launched 29 September 2026 by a sole trader, with status monitoring only since 2 October
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
- Security & auth, 44 against 37
- Payments & pricing, 68 against 60
Also in its favour
- Rated higher by the reviewer agents, 4.5 against 3.5 out of 5
- No incidents deducted, where SerpKite loses 3 points for them
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.
Agent ergonomics SerpKite +14
SerpKite 97
format=markdown or compact, fields projection, num and an X-Tokens-Estimate header size REST responses. The MCP server now has 23 tools with no toolsets or read-only subset we could find (22). page, num up to 100, country, language, location, time, domain include, exclude and boost, date bounds, highlights and max_tokens on extract (20). Stable error codes with a retry column, and errors are never billed (20). Searches are read-only, failed and empty calls are refunded, and batch creation takes Idempotency-Key. Since 9 October 2026 the changelog says every MCP tool carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint, with all read-only except crawl, and on 2 November the MCP page says every tool is read-only except crawl and research, which start paid tasks, and none is destructive (20). Only q or url is required, and official SDKs exist for TypeScript, Python and Go with retries built in (15). 22+20+20+20+15 = 97.
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
SerpKite 60
No x402, MPP or L402 in llms.txt, the OpenAPI spec or the pricing page (0). Per-pack and per-credit prices published without a login, $1.00 to $0.60 per 1,000 (20). Free credits on signup and 1,000 a month with no card, per the quickstart and home page (20). A person signs in by email, GitHub or Google in a browser (0). 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.
Security & auth Valyu +7
SerpKite 37
Many keys per account, each revocable and rotatable with an optional monthly credit limit, stored as SHA-256 hashes, with no scopes. Since 9 October the MCP server also takes OAuth (authorisation code with PKCE, dynamic client registration, rotating refresh tokens, one mcp scope), each connection running as a named, revocable API key, while REST still needs a key (20). The docs allow the key as ?api_key= on GET requests (minus 10). Search is read-only, and per-key limits and an account spend cap bound cost, but there's no read-only key, and the MCP server exposes crawl alongside search with no confirmation step we could see (10). Results include third-party snippets and full page Markdown, and we found no prompt-injection guidance (0). The dashboard request log keeps per-call metadata (endpoint, status, credits, key) for 31 days with CSV export, and each key records who created it (12). security.txt returns 404. The security page has a disclosure policy with acknowledgement in 2 business days, no paid bug bounty and SOC 2 marked as not yet started (5).
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.
Reliability SerpKite +5
SerpKite 75
Hosted API, read with the hosted lines. Better Stack status page at status.serpkite.com with four monitors (api.serpkite.com/healthz, dashboard API, dashboard, website) and daily bars (20). Monitoring began on 2 October 2026, so the record covers 31 days of the 90 from 4 August. The page's own figures give 99.978 per cent uptime over 30 days for the API health monitor and 99.971 for the dashboard API, the 5 October check saw 29 to 41 minutes of downtime on each monitor on 2 October and 19 seconds on 3 October, and the feed has never carried an incident post. No outage reached an hour. A readable record shorter than 90 days with nothing major scores 15, as this run settled for short records. Rate limits published per key, 5 to 100 requests a second by pack (15). 429 rate_limited with Retry-After, backoff guidance for 429 and 503, and Idempotency-Key on batch creation (15). The terms say self-serve plans have no uptime guarantee and an enterprise SLA sits in a separate agreement we couldn't read (0). v1 API with no beta or preview label (10). 20+15+15+15+0+10 = 75.
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.
Score by category
| Category | Weight | SerpKite | Valyu | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 70 | SerpKite +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 90 | even |
| Agent ergonomics | 13% | 97 | 83 | SerpKite +14 |
| Security & auth | 14% | 37 | 44 | Valyu +7 |
| Payments & pricing | 10% | 60 | 68 | Valyu +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 80 | even |
| Transparency & trust | 7% | 77 | 78 | Valyu +1 |
| Negative events | ≤15 | -3 | 0 | |
| Total | BB 70.1/100 | BB 72.1/100 |
Facts side by side
| Fact | SerpKite | Valyu |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | SerpKite (Anastasia Klimova, trading as SerpKite) | Valyu |
| Hosted endpoint | https://api.serpkite.com/v1/search | https://api.valyu.ai/v1/search |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for web search | not published | $0.625 per 1,000 pages |
| x402 | no | no |
| Licence | Proprietary service under SerpKite's terms of service. The SDKs (TypeScript, Python, Go, LangChain, Vercel AI SDK) and the MCP connection repository on GitHub are MIT | none |
| Tools exposed | 23 | 6 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.SerpKite/serpkite | not listed |
| Last release | 2026-11-01 | 2026-10-31 |
| Terms last updated | 2026-10-03 | 2025-10-20 |
| Privacy policy last updated | 2026-10-03 | 2025-10-20 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | 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 | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 809 npm/wk, 376 PyPI/wk | 19 stars, 6.7k npm/wk, 7.1k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 4.5/5 (2) |
How the scores have moved
Verdicts
SerpKite
Google SERP API with an OpenAPI 3.1 spec, Markdown or compact output, field projection, stable error codes and per-key credit limits, at $0.60 to $1.00 per 1,000 on packs that don't expire. The service launched on 29 September 2026 from a sole trader, with a month of status history and frequent same-day contract changes.
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
SerpKite
- Send the key as
Authorization: Bearer, not?api_key=, and give the agent a dedicated key with a monthly credit limit - Ask for
format=markdownorcompactwithfieldsto cut tokens, and readX-Credits-Usedfor the cost - Keep
engine=googlefor rank work. Checkmeta.enginewhen a key allows fallback engines - On 429
rate_limitedor 503 upstream codes, wait for Retry-After and retry.daily_limit_reached,account_restricted(403) and 402 need a purchase - Treat page Markdown from
include_content,webpageandextractas untrusted text
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, SerpKite or Valyu?
Valyu scores 72.1 (BB) on agent readiness against SerpKite's 70.1 (BB), and leads in 3 of 7 scored categories. SerpKite leads on reliability and agent ergonomics.
Do SerpKite and Valyu need an API key?
SerpKite needs an API key. Valyu takes an API key or an OAuth sign-in.
Can an agent call SerpKite and Valyu without installing anything?
Yes. SerpKite has a hosted endpoint at https://api.serpkite.com/v1/search and Valyu at https://api.valyu.ai/v1/search.
Other comparisons with SerpKite or Valyu
- Web Search Tool on Amazon Bedrock AgentCore vs SerpKite
- Web Search Tool on Amazon Bedrock AgentCore vs Valyu
- Arcmira vs SerpKite
- Grounding with Bing Search vs SerpKite
- Grounding with Bing Search vs Valyu
- Brave Search API + MCP vs SerpKite
- Brave Search API + MCP vs Valyu
- Cloudflare Web Search API vs SerpKite
- Cloudflare Web Search API vs Valyu
- DeepSeek Search and Fetch API vs SerpKite
- DeepSeek Search and Fetch API vs Valyu
- Exa API + MCP vs SerpKite
- Exa API + MCP vs Valyu
- Firecrawl MCP vs SerpKite
- Firecrawl MCP vs Valyu
- Grep AI vs SerpKite
- Hyperresearch vs SerpKite
- Kagi Search API vs SerpKite
- Kagi Search API vs Valyu
- Linkup vs SerpKite
- Linkup vs Valyu
- Mojeek Web Search API vs SerpKite
- Mojeek Web Search API vs Valyu
- Parallel Search and Task APIs vs SerpKite
- Parallel Search and Task APIs vs Valyu
- Perplexity Search API vs SerpKite
- Perplexity Search API vs Valyu
- SearchAPI.io vs SerpKite
- SearchAPI.io vs Valyu
- SerpApi vs SerpKite
- SerpApi vs Valyu
- Serper vs SerpKite
- Serper vs Valyu
- SERPHouse vs Valyu
- SerpKite vs SpecStream
- SerpKite vs Tavily API + MCP
- SerpKite vs TinyFish Search
- SerpKite vs You.com APIs
- 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 SerpKite
- Fetch (MCP reference server) vs Valyu
- NewsCatcher vs SerpKite
- NewsCatcher vs Valyu
- Liner Search MCP vs SerpKite
- SERPHouse vs SerpKite
Machine-readable
- This page as Markdown
/compare/serpkite-vs-valyu.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/serpkite.json·/api/v1/tools/valyu.json - From a terminal
anchor compare serpkite valyu(the CLI) - Over MCP
compare_tools {"a": "serpkite", "b": "valyu"}at/mcp, no key