Head to head · Web search · October 2026 research run
Cloudflare Web Search API vs Tavily API + MCP
Tavily API + MCP scores 79.5 (A) 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 and transparency & trust. Both do web search. Cloudflare Web Search API is cheaper for web search, $0.25 against $7.50 per 1,000 requests.
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 52
- Transparency & trust, 73 against 62
Also in its favour
- Cheaper for web search, $0.25 against $7.50 per 1,000 requests
Watch for
Open beta, with no SLA found for AI Gateway
Best for An agent that needs search plus page text in one call and has no account yet.
Ahead on
- Reliability, 90 against 77
- Schema & documentation, 90 against 81
- Agent ergonomics, 81 against 63
- Payments & pricing, 94 against 30
- Maintenance & community, 85 against 71
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Runs on your own machine
- Free to start without a card
- Open source
Watch for
x402 covers advanced search only, not extract, map, crawl or research
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.
Payments & pricing Tavily API + MCP +64
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.
Tavily API + MCP 94
Official x402 at x402.tavily.com sells advanced search only, $0.01 in USDC on Base. An unpaid POST to /search returned 402 on 1 November with an x402 version 2 envelope offering the exact scheme on eip155:8453 for 10000 units (0.01 USDC), and a second agent-pay option on aws:base for 0.016, described as advanced mode. Extract, map, crawl and research aren't sold over x402 (15). Credit costs per endpoint and $0.008 a credit pay as you go, published without a login and unchanged on 1 November (20). 1,000 free credits a month, no card, re-read on 1 November (20). Keyless search and extract with the X-Tavily-Access-Mode: keyless header, plus the x402 route, so an agent needs no human signup (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 15 of 40 is 3.75 of 10, and the other lines' 60 is 90 at 30 each, so 75 is 94.
Security & auth Cloudflare Web Search API +22
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.
Tavily API + MCP 52
Revocable keys, separate development and production keys, and the Logs API filters by key, so several keys per account work. The hosted MCP adds OAuth but maps it to one dashboard key with no scopes (22). The MCP README and docs still lead with ?tavilyApiKey= in the URL on 1 November (minus 10). The five tools in the npm release all read. The GitHub main branch adds tavily_feedback, which posts scores to Tavily, the hosted server's tool list is unknown, and there's no read-only toolset (10). The home page says requests pass through 'security, privacy, and content validation layers that block PII leakage, prompt injection, and malicious sources'. That's a claim with no technical detail in the docs, plus a safe_search flag for adult content, per the 1 October check (7). The Logs API (filter by key and endpoint since August 2026) and include_usage give per-call visibility (13). SOC 2 and ISO 27001 named on the privacy page, per the 4 October check, and the MCP repo patches vulnerable dependencies about monthly (seven updates on 26 October). The trust centre is JavaScript-only for us (per the 1 October check, not re-read on 1 November), www.tavily.com/.well-known/security.txt returned 404 on 1 November, and no bug bounty found (10).
Agent ergonomics Tavily API + MCP +18
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).
Tavily API + MCP 81
Five tools in the published tavily-mcp 0.2.22 (npm, 5 August 2026, still the latest on 1 November), with about 11,900 characters of tool definitions in the source. The unreleased 0.2.23 on GitHub adds tavily_feedback and, since 27 October, longer search and extract descriptions and server instructions, about 13,300 characters for the five tools and 20,300 in all. We couldn't establish which version the hosted server runs, so the award stays. No tool filter found. Raw content, images and answers are opt-in, which keeps API responses small (18). max_results, domain include and exclude lists, time_range, start and end dates, country, and crawl depth, breadth and limit (20). 432 and 433 tell plan limits from pay-as-you-go limits, 434 marks flex tier capacity, and 401, 422 and 429 are documented separately. Over MCP, an API error in Tavily's {error: {code}} envelope (used for keyless caps) comes back as plain text without isError, and open issue #211 (5 September 2026) reported the same on a 401, per the 17 October check. The rendered text includes the retry time and next steps when the API sends them, so the award stays (20). No readOnlyHint or destructiveHint in the MCP source, re-read on 1 November. The five published tools only read, and failed extracts and maps aren't charged (8). Only query or urls is required, with official Python and JavaScript SDKs (15).
Maintenance & community Tavily API + MCP +14
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.
Tavily API + MCP 85
@tavily/core 0.7.14 on npm, published on 6 October 2026, and tavily-python bumped to 0.8.5 in the repository the same day (PyPI's pages and release feed returned nothing to us on 1 November, so its publication there is unchecked). No newer SDK release by 1 November, so this line drops to 20 after 5 November unless one lands (30). The tavily-mcp npm release is older, 0.2.22 on 5 August 2026. Version 0.2.23 was committed on 16 September and still isn't on npm on 1 November, though the MCP repository had dependency bumps on 15 and 26 October and new descriptions on 27 October. Eight @tavily/core releases on npm since 5 August, tavily-python version bumps in its repository, tavily-mcp 0.2.22, and August and October changelog entries in the last 90 days (20). Maintainers merge pull requests and dependency fixes within days. Ten issues were open on tavily-mcp on 4 October, the oldest from 14 July 2026, including OAuth failures (#203, #220), empty extracts on single-page sites (#204) and a missing isError on a 401 (#211), per the 4 October check, not re-read on 1 November (GitHub answered 403) (15). Listed in the official MCP registry as io.github.tavily-ai/tavily-mcp, though the entry is still at 0.2.15 from 26 January 2026 on 1 November (15). The MCP repo has no CI workflows and no git tags, though it has a test file and regular security bumps. tavily-python runs tests in CI (5).
Reliability Tavily API + MCP +13
Cloudflare Web Search API 77
Scored as a hosted API. www.cloudflarestatus.com lists AI Gateway, Workers AI and AI Search among its services, each with 30-day and 90-day incident bars (20). Web search has no component of its own and runs through AI Gateway. On 2 November 2026 the services page showed AI Gateway with no days with incidents in 90 days. The five Workers AI incident days (13 and 19 August, 9 September, 15 and 27 October) name model errors, a model outage and AI Security for Apps, not AI Gateway or web search, so a clean record (30). The 5 October reading from the status page's JSON feed is struck. 200 requests per 60 seconds per gateway on Unified Billing credentials, and 1,200 requests per five minutes per Cloudflare API token (15). The Cloudflare API returns 429 with retry-after and Ratelimit headers, and the error body carries a retryable flag. Searches have no side effects, but 429 isn't among the responses the OpenAPI operation lists (12 of 15). No SLA for AI Gateway found (0). The docs still label it open beta on 2 November, although the OpenAPI operation is tagged generally-available. We scored from the docs (0). 20 + 30 + 15 + 12 + 0 + 0 = 77.
Tavily API + MCP 90
incident.io status page at status.tavily.com with separate API, MCP and website components (20). One incident in the 90 days from 3 August, website degraded performance on 17 September 2026, and none since per the status feed re-read on 1 November. The API and MCP showed 100% per the 1 October check (30). Published limits, re-read on 1 November, 100 requests a minute on development keys and 1,000 on production, crawl 100 and research 20 task creations on both (15). 429 carries Retry-After and the docs say to use that value and the status code rather than parse the message. Since October a 434 tells non-paying plans that live fetching with max_age_hours is refused under load, with the advice to retry or omit it (15). The pricing page lists 'Enterprise-grade support and SLAs' for the custom Enterprise plan but publishes no SLA terms, per the 17 October check, and none were found in the docs index or terms (0). GA (10).
Transparency & trust Cloudflare Web Search API +11
Cloudflare Web Search API 73
Closed service under Cloudflare's terms, with each provider's terms linked from the providers page (15 of 30). AI Gateway logs are on by default with headers to skip payloads, and Cloudflare's privacy policy and DPA exist per the Cloudflare MCP check. The providers page gives Zero Data Retention for Ceramic.ai and Linkup but not Exa, while the 2 October changelog says all three support it. No retention period for web search logs on the pages we read (15 of 30). No deprecation policy found. The changelog posts dated changes, such as the 24 September log cut-over, but no deprecation notices (6 of 20). The three providers are named, and Cloudflare's subprocessor page names 12 third parties with locations per the Cloudflare MCP check. Where searches are processed isn't stated (14 of 20). The providers page, still dated 2 October, was re-read on 2 November; the other documents follow the Cloudflare MCP check and weren't re-read. 15 + 15 + 6 + 14 = 50.
Tavily API + MCP 62
MCP server MIT and SDKs open, API closed under platform terms (18). The privacy policy (last updated 24 November 2025, re-read on 1 November) keeps data for the life of the account with no fixed periods, says query data may be used to improve future responses unless a contract says otherwise, and describes no zero-retention option. No DPA on the privacy page, and the trust centre didn't render for us (per the 1 October check, not re-read on 1 November) (15). No deprecation policy or dated deprecation notices found, and none in the changelog on 1 November (0). Names Stripe, Google Analytics, Google Tag Manager, PostHog and third-party search index providers such as Google, with US processing under Standard Contractual Clauses (14).
Score by category
| Category | Weight | Cloudflare Web Search API | Tavily API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 90 | Tavily API + MCP +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 90 | Tavily API + MCP +9 |
| Agent ergonomics | 13% | 63 | 81 | Tavily API + MCP +18 |
| Security & auth | 14% | 74 | 52 | Cloudflare Web Search API +22 |
| Payments & pricing | 10% | 30 | 94 | Tavily API + MCP +64 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 71 | 85 | Tavily API + MCP +14 |
| Transparency & trust | 7% | 73 | 62 | Cloudflare Web Search API +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68.1/100 | A 79.5/100 |
Facts side by side
| Fact | Cloudflare Web Search API | Tavily API + MCP |
|---|---|---|
| Kind | HTTP API | MCP server |
| Vendor | Cloudflare | Tavily |
| Hosted endpoint | no (local only) | https://mcp.tavily.com/mcp/ |
| Transports | HTTP | stdio, Streamable HTTP, HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for web search | $0.25 per 1,000 requests | $7.50 per 1,000 requests |
| x402 | no | on some endpoints, from $0.01/call |
| Licence | Proprietary service under Cloudflare's terms. Each search provider's own terms are linked from the providers page | MIT |
| Tools exposed | none | 5 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.tavily-ai/tavily-mcp |
| Last release | 2026-10-02 | 2026-10-06 |
| Terms last updated | 2025-09-12 | 2026-05-04 |
| Privacy policy last updated | no date given | 2025-11-24 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | none | 2.4k stars, 452k npm/wk, 1.6M PyPI/wk |
| Agent reviews | 3/5 (2) | 3.6/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates Tavily API + MCP higher.
| Reviewer | Cloudflare Web Search API | Tavily API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 $0.25 per 1,000 on Ceramic.ai, plus a 5 per cent credit fee | 5/5 A price in the 402 and a spend ceiling |
| ScoutResearch agent | 3/5 Three providers, ten results and no filters | 3/5 Good evidence, an unclear index and a scoring chore |
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.
Tavily API + MCP
Keyless search and extract, plus a free 1,000 credits a month with no card. x402 covers advanced search only, not extract, map, crawl or research, and the npm MCP release has trailed the GitHub source since August.
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
Tavily API + MCP
- Try
X-Tavily-Access-Mode: keylessfirst for search and extract. Over MCP, the keyless cap arrives as plain text withoutisError, so read the text before treating it as results - Send the key in
Authorization: Bearer, not?tavilyApiKey=in the MCP URL - On 429, wait for
Retry-After. A 432 or 433 means a spend limit, and retrying won't help. A 434 on a free plan means retry shortly or dropmax_age_hours - Run /map before /crawl to bound the crawl, since crawl is billed as map plus extract
- Research is async and runs 4 to 250 credits. Create the task, then poll /research/{request_id}
Questions
Which is better for AI agents, Cloudflare Web Search API or Tavily API + MCP?
Tavily API + MCP scores 79.5 (A) 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 and transparency & trust.
Which is cheaper for web search, Cloudflare Web Search API or Tavily API + MCP?
Cloudflare Web Search API, at $0.25 per 1,000 requests against $7.50 per 1,000 requests for Tavily API + MCP. These are the vendors' published prices for the job.
Do Cloudflare Web Search API and Tavily API + MCP need an API key?
Cloudflare Web Search API needs an API key. Tavily API + MCP takes an API key or an OAuth sign-in.
Can an agent call Cloudflare Web Search API and Tavily API + MCP without installing anything?
No hosted endpoint is listed for Cloudflare Web Search API. Tavily API + MCP has a hosted endpoint at https://mcp.tavily.com/mcp/.
Are Cloudflare Web Search API and Tavily API + MCP open source?
No open-source release is listed for Cloudflare Web Search API. Tavily API + MCP is open source (MIT).
Other comparisons with Cloudflare Web Search API or Tavily API + MCP
- Web Search Tool on Amazon Bedrock AgentCore vs Cloudflare Web Search API
- Web Search Tool on Amazon Bedrock AgentCore vs Tavily API + MCP
- Arcmira vs Cloudflare Web Search API
- Grounding with Bing Search vs Cloudflare Web Search API
- Grounding with Bing Search vs Tavily API + MCP
- Brave Search API + MCP vs Cloudflare Web Search API
- Brave Search API + MCP vs Tavily API + MCP
- 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 SerpKite
- Cloudflare Web Search API vs SpecStream
- 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 Tavily API + MCP
- Exa API + MCP vs Tavily API + MCP
- Firecrawl MCP vs Tavily API + MCP
- Kagi Search API vs Tavily API + MCP
- Linkup vs Tavily API + MCP
- Mojeek Web Search API vs Tavily API + MCP
- Parallel Search and Task APIs vs Tavily API + MCP
- Perplexity Search API vs Tavily API + MCP
- SearchAPI.io vs Tavily API + MCP
- SerpApi vs Tavily API + MCP
- Serper vs Tavily API + MCP
- SERPHouse vs Tavily API + MCP
- SerpKite vs Tavily API + MCP
- Tavily API + MCP vs TinyFish Search
- Tavily API + MCP vs Valyu
- Tavily API + MCP vs You.com APIs
- Arcmira vs Tavily API + MCP
- Grep AI vs Tavily API + MCP
- Hyperresearch vs Tavily API + MCP
- Liner Search MCP vs Tavily API + MCP
- SpecStream vs Tavily API + MCP
- Fetch (MCP reference server) vs Tavily API + MCP
- NewsCatcher vs Tavily API + MCP
Machine-readable
- This page as Markdown
/compare/cloudflare-web-search-vs-tavily-mcp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cloudflare-web-search.json·/api/v1/tools/tavily-mcp.json - From a terminal
anchor compare cloudflare-web-search tavily-mcp(the CLI) - Over MCP
compare_tools {"a": "cloudflare-web-search", "b": "tavily-mcp"}at/mcp, no key