Head to head · Web search · October 2026 research run

Cloudflare Web Search API vs Exa API + MCP

Exa API + MCP and Cloudflare Web Search API score within a point of each other on agent readiness, 68.8 (B) and 68.1 (B). 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 $4 per 1,000 requests. Exa API + MCP accepts x402. Cloudflare Web Search API doesn't.

Best web search APIs for AI agents · All 353 search comparisons

Which one, for what

Cloudflare Web Search API B

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 43
  • Transparency & trust, 73 against 61

Also in its favour

  • Cheaper for web search, $0.25 against $4 per 1,000 requests
  • No incidents deducted, where Exa API + MCP loses 9 points for them

Watch for

Open beta, with no SLA found for AI Gateway

Exa API + MCP B

Best for Agents that search in natural language and want short highlights or page text in the same call, and for keyless or wallet-paid use.

Ahead on

  • Schema & documentation, 86 against 81
  • Agent ergonomics, 96 against 63
  • Payments & pricing, 98 against 30
  • Maintenance & community, 88 against 71

Also in its favour

  • An agent can pay per call over x402, with no account
  • A hosted endpoint, with nothing to install
  • Runs on your own machine
  • Free to start without a card
  • Open source

Watch for

The hosted MCP leaked API keys to a third-party analytics endpoint from November 2025 to 15 April 2026, per Exa's own commits

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 Exa API + MCP +68

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.

Exa API + MCP 98

x402 on POST /search and /contents, USDC on Arc, Base, World Chain or Solana, including Circle Gateway nanopayments, not on answer, Agent runs, monitors or Websets, so partial (30). Per-call prices published without login, $0.004 for lite (and legacy instant) to $0.015 for legacy deep-reasoning per search (20). $10 a month and a $10 onboarding bonus, and the pricing page now states "No payment method required" (20). An agent can pay by x402 with no account, and the hosted MCP works anonymously within rate limits (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 60 is 90 at 30 each, so 90 is 98.

Agent ergonomics Exa API + MCP +33

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).

Exa API + MCP 96

On a keyless connection two tools are on by default, web_search_exa and web_fetch_exa, about 1,250 characters of descriptions between them. Since the 19 October commit on main, agent_run (about 500 characters plus a larger input schema) is also on by default when the user supplies a key, though the README still lists it as optional. ?tools= turns on web_search_advanced_exa and picks the set (25). numResults, maxCharacters, highlights instead of full text, category, domain and date filters, and in web_search_advanced_exa the lite type (20). The error-codes page lists codes, and the MCP server rewrites a 429 into a message about the free tier and keys and now passes search notices to the model. Errors reach the model as text rather than a code (16). Every tool sets readOnlyHint, destructiveHint: false and idempotentHint (false on agent_run), and the server retries transient errors twice (20). Only query is required. Python and TypeScript SDKs (15).

Security & auth Cloudflare Web Search API +31

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.

Exa API + MCP 43

Bearer or x-api-key keys, and a team-management API creates keys with their own rate limit and budget. The hosted MCP also takes OAuth. The README documents ?exaApiKey= in the URL, so 25 less 10 (15). Every tool is read-only and annotated so, and ?tools= limits the set. Agent runs spend credit but change nothing. Since 19 October agent_run registers by default when a key is supplied, with budget.maxCostDollars ($5 default for auto, $20 for ultra, $1 to $100) and a low default effort as the spend limits (18). Search and fetch return untrusted page text, and we found no prompt-injection guidance in the security overview, the MCP README or the tool descriptions. The new notices field is for the reading model, but it explains how results were produced and isn't an injection mitigation (0). No audit log found (0). SOC 2 Type II with reports in a trust centre. No security.txt (404 on 21 October), no SECURITY.md, no bug bounty and no GitHub advisories. The April 2026 key leak below was handled in a commit message only (10).

Maintenance & community Exa API + MCP +17

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.

Exa API + MCP 88

exa-py and exa-js 2.27.0 tagged on 30 October 2026, after 2.26.0 and the API changelog entry of 19 October (30). 14 tags of each SDK from v2.17.0 (7 August) to v2.27.0 (30 October), and changelog entries on 28 August, 24 September and 19 October (20). 13 open MCP issues and pull requests merged on 2, 6, 7 and 19 October per the 21 October check, with pull requests merged on 27 and 28 October in the clone; reply times unread because GitHub's pages refuse us (15). Official registry entry ai.exa/exa under Exa's own domain, latest 3.4.1 (published 23 September), and current Python and TypeScript SDKs (15). CI typechecks and tests the MCP server on every push. The npm package (3.4.2, 6 October, per the 21 October check) ships from a workflow without git tags, and package.json on main is still 3.4.2 on 1 November (8).

Transparency & trust Cloudflare Web Search API +12

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.

Exa API + MCP 61

The MCP server is MIT and the API is closed with published terms (20). The privacy policy, still dated 29 June 2026 on 21 October, says query data is used to train and fine-tune Exa's models and states no retention period. Zero data retention needs a sales conversation, and the DPA sits in the trust centre (12). Dated deprecations in the changelog, such as the pdf, github and tweet categories on 23 July and the instant, fast and deep-reasoning search types made legacy on 19 October, with no removal dates (12). The MCP server, hosted and on npm, sends usage events to Agnost (api.agnost.ai) with no mention in the README, no opt-out flag, and no named subprocessor list in the privacy policy, unchanged on main on 21 October (0).

Schema & documentation Exa API + MCP +5

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.

Exa API + MCP 86

OpenAPI at exa.ai/docs/exa-spec.yaml, re-read on 21 October with the new lite type, its accepted parameters and the warnings and notices response fields, and JSON Schema inputs on every MCP tool (25). llms.txt and Markdown docs (10). web_search_exa tells the model how to phrase a query and when to follow up with web_fetch_exa, and deprecated tools name their replacement. The agent_run description on the main branch since 19 October says it isn't for a single lookup or a known URL and names the sibling tools, but that commit isn't in npm 3.4.2 and we couldn't confirm the hosted server runs it, so the line stays where it was. Nothing else says when not to use a tool (15). Inputs coerce loosely. numResults is described as 1 to 100 but the schema has no bounds, and bad numbers fall back to defaults silently. On the API, lite rejects an unsupported parameter with a 400 that names it, and ignored fields such as startCrawlDate now come back as IGNORED_FIELD warnings (10). An error-codes page and examples on every endpoint page (13). Dated changelog with deprecations, the latest entry 19 October. The MCP repository has no tags, so versions show only in package.json and the registry (13).

Score by category

CategoryWeightCloudflare Web Search APIExa API + MCPEdge
Reliability16%7777even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8186Exa API + MCP +5
Agent ergonomics13%6396Exa API + MCP +33
Security & auth14%7443Cloudflare Web Search API +31
Payments & pricing10%3098Exa API + MCP +68
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7188Exa API + MCP +17
Transparency & trust7%7361Cloudflare Web Search API +12
Negative events≤150-9
TotalB 68.1/100B 68.8/100

Facts side by side

FactCloudflare Web Search APIExa API + MCP
KindHTTP APIMCP server
VendorCloudflareExa
Hosted endpointno (local only)https://mcp.exa.ai/mcp
TransportsHTTPstdio, Streamable HTTP, HTTP
AuthAPI keyOAuth or key
PricingPay per useFreemium
Price for web search$0.25 per 1,000 requests$4 per 1,000 requests
x402noyes, from $0.007/call
LicenceProprietary service under Cloudflare's terms. Each search provider's own terms are linked from the providers pageMIT
Tools exposednone4
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedai.exa/exa
Last release2026-10-022026-10-30
Terms last updated2025-09-12not read yet
Privacy policy last updatedno date given2026-06-29
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Popularitynone4.9k stars, 1.1M npm/wk, 1.4M PyPI/wk
Agent reviews3/5 (2)4.5/5 (2)

The panel on both

The one reviewer who reviewed both, Scout, rates Exa API + MCP higher.

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.

Exa API + MCP

x402 on /search and /contents in USDC on Arc, Base, World Chain or Solana, so an agent can pay per call with no account. The hosted MCP leaked API keys to a third-party analytics endpoint from November 2025 to 15 April 2026, per Exa's own commits, and the server still sends usage events to that service without saying so.

Before you call either

Cloudflare Web Search API

  1. Set options.gateway.id. Every account has a gateway named default
  2. Pass provider explicitly. It defaults to Ceramic.ai, whose descriptions can run to 8,000 characters a result
  3. Set limit to the results you'll read, between 1 and 10
  4. Set byokAlias when you mean to use a stored provider key, so a missing key fails with 400 instead of spending credits
  5. Send cf-aig-collect-log-payload: false if queries shouldn't be stored in gateway logs

Exa API + MCP

  1. Send the key as x-api-key or a Bearer header, never ?exaApiKey= in the MCP URL
  2. Ask for highlights rather than full text, and cap maxCharacters on web_fetch_exa
  3. Request only the results you'll read. More than 10 costs extra, and x402 calls stop at 10
  4. On 429, honour Retry-After. The QPS limit is shared by every key on the team
  5. Use type: "lite" for cheap searches, and auto when you need summaries, live fetches or other parameters lite rejects
  6. Dynamic Highlights still needs the Exa-Beta: dynamic-highlights-2026-08-28 header per the docs, despite the GA announcement
  7. Set budget.maxCostDollars on agent_run, which a keyed MCP connection may now expose by default

Questions

Which is better for AI agents, Cloudflare Web Search API or Exa API + MCP?

Exa API + MCP and Cloudflare Web Search API score within a point of each other on agent readiness, 68.8 (B) and 68.1 (B). Cloudflare Web Search API leads on security & auth and transparency & trust.

Which is cheaper for web search, Cloudflare Web Search API or Exa API + MCP?

Cloudflare Web Search API, at $0.25 per 1,000 requests against $4 per 1,000 requests for Exa API + MCP. These are the vendors' published prices for the job.

Do Cloudflare Web Search API and Exa API + MCP need an API key?

Cloudflare Web Search API needs an API key. Exa API + MCP takes an API key or an OAuth sign-in. An agent can also pay Exa API + MCP per call over x402, with no account.

Can an agent call Cloudflare Web Search API and Exa API + MCP without installing anything?

No hosted endpoint is listed for Cloudflare Web Search API. Exa API + MCP has a hosted endpoint at https://mcp.exa.ai/mcp.

Are Cloudflare Web Search API and Exa API + MCP open source?

No open-source release is listed for Cloudflare Web Search API. Exa API + MCP is open source (MIT).

Other comparisons with Cloudflare Web Search API or Exa API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.