Head to head · Web search · October 2026 research run
Cloudflare Web Search API vs SerpKite
SerpKite scores 70.1 (BB) on agent readiness against Cloudflare Web Search API's 68.1 (B), and leads in 5 of 7 scored categories. Cloudflare Web Search API leads on security & auth. Both do web search.
Best web search APIs for AI agents · All 353 search comparisons
Which one, for what
Best for Agents and apps already on Cloudflare Workers or AI Gateway that want cheap snippet search ($0.25 per 1,000 with Ceramic.ai) on the same bill and logs as their inference.
Ahead on
- Security & auth, 74 against 37
Also in its favour
- No incidents deducted, where SerpKite loses 3 points for them
Watch for
Open beta, with no SLA found for AI Gateway
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
- Schema & documentation, 90 against 81
- Agent ergonomics, 97 against 63
- Payments & pricing, 60 against 30
- Maintenance & community, 80 against 71
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Free to start without a card
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Launched 29 September 2026 by a sole trader, with status monitoring only since 2 October
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.
Security & auth Cloudflare Web Search API +37
Cloudflare Web Search API 74
Cloudflare API tokens are scoped by permission and revocable, and web search needs only Workers AI Read and AI Gateway Read. Permission is per account, not per gateway or provider. The OpenAPI operation also accepts the legacy global API key in headers (27 of 30). Every call reads. Spend limits per gateway and the Require provider credentials setting cap or block spend, and byokAlias fails rather than falling back to credits. Read permission is enough to spend credits (14 of 20). Results are third-party page text passed to a model, and we found no prompt-injection guidance in the web search pages or the launch post. AI Gateway Guardrails aren't documented for web search (0 of 15). Every search lands in AI Gateway logs with cost and status, on by default (15). security.txt names HackerOne and a disclosure policy and still has no Expires field, re-read on 2 November 2026. Cloudflare's ISO page says it is currently certified against ISO 27001:2022, with ISO 27018 and 27701, scoped to the Cloudflare global cloud platform. 2 held back for the missing Expires, as on the other Cloudflare listings (18 of 20). 27 + 14 + 0 + 15 + 18 = 74.
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).
Agent ergonomics SerpKite +34
Cloudflare Web Search API 63
Results are small by default (URL, title, description), and limit caps them at 1 to 10. The default provider, Ceramic.ai, returns descriptions of up to 8,000 characters a result with no parameter to shorten them (15 of 25). limit is the only control. No pagination, offset, domain, date, country or freshness filters (6 of 20). Errors come back with category (gateway, credential, provider, internal), code, status, retryable and gatewayRequestId. The codes themselves aren't listed (16 of 20). Searches only read, the error body says whether a retry helps, and gateways can retry upstream failures up to five times. No idempotency keys, which a read doesn't need (16 of 20). Only query and the gateway ID are required. The Workers binding is TypeScript, and the Cloudflare TypeScript SDK 7.3.0 of 3 October has no web search method. We didn't check the Python or Go SDKs (10 of 15).
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.
Payments & pricing SerpKite +30
Cloudflare Web Search API 30
No x402, MPP or L402 on /ai/websearch. AI Gateway Machine Payments covers only /ai/run for four open models (0, Machine Payments page unchanged since 30 September and still limited to /ai/run). Per-search prices published without a login, $0.25, $5.00 and $7.00 per 1,000 by provider. The 5 per cent fee on credit purchases sits on the Unified Billing page, not the providers page (20). No free allowance found. Credits need a payment method, and the BYOK route needs an account with the provider (0). A person signs up for Cloudflare in a browser and buys credits or stores a provider key (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
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.
Schema & documentation SerpKite +9
Cloudflare Web Search API 81
Cloudflare's public OpenAPI has /accounts/{account_id}/ai/websearch with a typed body, additionalProperties: false and typed 200, 400, 403 and 502 responses. provider is a free string there where the docs give an enum (22 of 25). llms.txt for the product and Markdown for every page (10). The providers page says which provider suits which job, such as Ceramic.ai for agents that run many searches and Exa for short query-relevant excerpts. Nothing says when not to use the endpoint, and the OpenAPI description is one line (12 of 20). query 1 to 1,024 characters, limit 1 to 10, provider enum in the docs, byokAlias with a pattern (14 of 15). curl and Worker examples, a response example, and a typed error body with category, code and retryable. No catalogue of error codes or messages found (11 of 15). Dated launch entry in the AI Gateway changelog, still the only web search entry on 2 November 2026. The API path carries v4 for the whole Cloudflare API, nothing specific to web search (12 of 15). The OpenAPI operation, re-read from a clone on 2 November, is unchanged.
SerpKite 90
Public OpenAPI 3.1 spec (version 1.12.7 on 2 November 2026, 41 paths and 47 operations) at serpkite.com/openapi/serp-api.yaml (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Endpoint descriptions state purpose and when to use them, and the guides cover which tool to pick. The MCP tool definitions aren't public and tools/list needs a key, so we read the MCP docs table and the matching descriptions in the MIT AI SDK package, which state purpose and some when-to-use lines but not when not to (12). Typed parameters with 64 enums in the spec, documented ranges and strict validation that rejects unknown parameters with a 400 naming the replacement. We couldn't confirm the MCP JSON Schemas (13). curl, TypeScript, Python and Go examples on each page, and an errors page with 14 codes and what to do about each (15). Versioned /v1 paths and a dated API changelog (15).
Maintenance & community SerpKite +9
Cloudflare Web Search API 71
Read for a closed service. The web search launch entry is dated 2 October 2026, 31 days ago. The AI Gateway changelog entry of 8 October 2026 changed the log and request IDs every AI Gateway request returns, searches included, so recency stays at 30 until 7 November. Thirteen dated AI Gateway changelog entries from 5 August to 21 October (20). A public changelog with RSS and a developer Discord. We didn't check support response times (8 of 15). The Workers binding has the method. The Cloudflare TypeScript SDK's newest tag is still 7.3.0 of 2 October, with no web search method, though the OpenAPI names an SDK method websearch (8 of 15). The OpenAPI spec carries the path. Nothing else to measure for a hosted endpoint (5 of 10). 30 + 20 + 8 + 8 + 5 = 71.
SerpKite 80
Closed service read with the API lines. The newest API changelog entries are dated 1 November 2026 (API 1.12.7) (30). 31 dated changelog entries from 9 October to 1 November, among them API 1.6.0 to 1.12.7 and SDKs 0.8.0 and 0.8.1 (20). Public changelog, support@serpkite.com and a Discord link. The SDK repositories are mirrors of a private monorepo and we couldn't see issues or replies (8). In the official MCP registry under the GitHub-verified namespace io.github.SerpKite, per the 5 October check, with current official SDKs in three languages (15). The SDK repositories run typecheck, tests and build in CI, but we couldn't see run results (7). 30+20+8+15+7 = 80.
Score by category
| Category | Weight | Cloudflare Web Search API | SerpKite | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 75 | Cloudflare Web Search API +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 90 | SerpKite +9 |
| Agent ergonomics | 13% | 63 | 97 | SerpKite +34 |
| Security & auth | 14% | 74 | 37 | Cloudflare Web Search API +37 |
| Payments & pricing | 10% | 30 | 60 | SerpKite +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 71 | 80 | SerpKite +9 |
| Transparency & trust | 7% | 73 | 77 | SerpKite +4 |
| Negative events | ≤15 | 0 | -3 | |
| Total | B 68.1/100 | BB 70.1/100 |
Facts side by side
| Fact | Cloudflare Web Search API | SerpKite |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Cloudflare | SerpKite (Anastasia Klimova, trading as SerpKite) |
| Hosted endpoint | no (local only) | https://api.serpkite.com/v1/search |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| Price for web search | $0.25 per 1,000 requests | not published |
| x402 | no | no |
| Licence | Proprietary service under Cloudflare's terms. Each search provider's own terms are linked from the providers page | 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 |
| Tools exposed | none | 23 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.SerpKite/serpkite |
| Last release | 2026-10-02 | 2026-11-01 |
| Terms last updated | 2025-09-12 | 2026-10-03 |
| Privacy policy last updated | no date given | 2026-10-03 |
| 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 | yes | not found in the text |
| Popularity | none | 809 npm/wk, 376 PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
The one reviewer who reviewed both, Ledger, rates SerpKite higher.
| Reviewer | Cloudflare Web Search API | SerpKite |
|---|---|---|
| LedgerCost analyst | 3/5 $0.25 per 1,000 on Ceramic.ai, plus a 5 per cent credit fee | 4/5 Credits that never expire, held by a vendor launched on 29 September |
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
Cloudflare Web Search API
One endpoint that sends a search to Ceramic.ai, Exa or Linkup and returns results in one format, logged and billed through AI Gateway, whose status shows no incidents in 90 days. Ceramic.ai costs $0.25 per 1,000 searches. It is still an open beta with no free allowance, at most 10 results a call, no filters and no machine payment route.
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.
Before you call either
Cloudflare Web Search API
- Set
options.gateway.id. Every account has a gateway nameddefault - Pass
providerexplicitly. It defaults to Ceramic.ai, whose descriptions can run to 8,000 characters a result - Set
limitto the results you'll read, between 1 and 10 - Set
byokAliaswhen you mean to use a stored provider key, so a missing key fails with 400 instead of spending credits - Send
cf-aig-collect-log-payload: falseif queries shouldn't be stored in gateway logs
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
Questions
Which is better for AI agents, Cloudflare Web Search API or SerpKite?
SerpKite scores 70.1 (BB) on agent readiness against Cloudflare Web Search API's 68.1 (B), and leads in 5 of 7 scored categories. Cloudflare Web Search API leads on security & auth.
Do Cloudflare Web Search API and SerpKite need an API key?
Both need an API key.
Can an agent call Cloudflare Web Search API and SerpKite without installing anything?
No hosted endpoint is listed for Cloudflare Web Search API. SerpKite has a hosted endpoint at https://api.serpkite.com/v1/search.
Other comparisons with Cloudflare Web Search API or SerpKite
- Web Search Tool on Amazon Bedrock AgentCore vs Cloudflare Web Search API
- Web Search Tool on Amazon Bedrock AgentCore vs SerpKite
- Arcmira vs Cloudflare Web Search API
- Arcmira vs SerpKite
- Grounding with Bing Search vs Cloudflare Web Search API
- Grounding with Bing Search vs SerpKite
- Brave Search API + MCP vs Cloudflare Web Search API
- Brave Search API + MCP vs SerpKite
- Cloudflare Web Search API vs DeepSeek Search and Fetch API
- Cloudflare Web Search API vs Exa API + MCP
- Cloudflare Web Search API vs Firecrawl MCP
- Cloudflare Web Search API vs Grep AI
- Cloudflare Web Search API vs Hyperresearch
- Cloudflare Web Search API vs Kagi Search API
- Cloudflare Web Search API vs Linkup
- Cloudflare Web Search API vs Mojeek Web Search API
- Cloudflare Web Search API vs NewsCatcher
- Cloudflare Web Search API vs Parallel Search and Task APIs
- Cloudflare Web Search API vs Perplexity Search API
- Cloudflare Web Search API vs SearchAPI.io
- Cloudflare Web Search API vs SerpApi
- Cloudflare Web Search API vs Serper
- Cloudflare Web Search API vs SERPHouse
- Cloudflare Web Search API vs SpecStream
- Cloudflare Web Search API vs Tavily API + MCP
- Cloudflare Web Search API vs TinyFish Search
- Cloudflare Web Search API vs Valyu
- Cloudflare Web Search API vs You.com APIs
- DeepSeek Search and Fetch API vs SerpKite
- Exa API + MCP vs SerpKite
- Firecrawl MCP vs SerpKite
- Grep AI vs SerpKite
- Hyperresearch vs SerpKite
- Kagi Search API vs SerpKite
- Linkup vs SerpKite
- Mojeek Web Search API vs SerpKite
- Parallel Search and Task APIs vs SerpKite
- Perplexity Search API vs SerpKite
- SearchAPI.io vs SerpKite
- SerpApi vs SerpKite
- Serper vs SerpKite
- SerpKite vs SpecStream
- SerpKite vs Tavily API + MCP
- SerpKite vs TinyFish Search
- SerpKite vs Valyu
- SerpKite vs You.com APIs
- Fetch (MCP reference server) vs SerpKite
- NewsCatcher vs SerpKite
- Liner Search MCP vs SerpKite
- SERPHouse vs SerpKite
Machine-readable
- This page as Markdown
/compare/cloudflare-web-search-vs-serpkite.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cloudflare-web-search.json·/api/v1/tools/serpkite.json - From a terminal
anchor compare cloudflare-web-search serpkite(the CLI) - Over MCP
compare_tools {"a": "cloudflare-web-search", "b": "serpkite"}at/mcp, no key