# Grounding with Bing Search vs Cloudflare Web Search API

> Cloudflare Web Search scores 66.9 (B) to Grounding with Bing Search's 63.7 (B) for web search. Cloudflare Web Search is cheaper for web search, $0.25 against $14 per 1,000 requests. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search
- Markdown: https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search.md (~6,500 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Cloudflare Web Search API scores 66.9 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security & auth and maintenance & community. Both do web search. Cloudflare Web Search API is cheaper for web search, $0.25 against $14 per 1,000 requests.

- Grounding with Bing Search: grade B, 63.7/100, rank #502 of 1486. Markdown https://www.anchorterminal.com/tools/bing-grounding.md · JSON https://www.anchorterminal.com/api/v1/tools/bing-grounding.json
- Cloudflare Web Search API: grade B, 66.9/100, rank #347 of 1486. Markdown https://www.anchorterminal.com/tools/cloudflare-web-search.md · JSON https://www.anchorterminal.com/api/v1/tools/cloudflare-web-search.json
- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md
- All 308 search comparisons: https://www.anchorterminal.com/compare/search/index.md

## Which one, for what

### Grounding with Bing Search (B)

Good for: Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.

Ahead on:
- Security & auth, 79 against 74
- Maintenance & community, 80 against 71

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: The Bing tools never return raw results to developers, only a model-written answer with citation links

### Cloudflare Web Search API (B)

Good 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:
- Reliability, 77 against 68
- Schema & documentation, 81 against 68
- Transparency & trust, 73 against 66

Also in its favour:
- Cheaper for web search, $0.25 against $14 per 1,000 requests

Watch for: Open beta, with no SLA found for AI Gateway


## Why the edge

### Schema & documentation: Cloudflare Web Search API +13

- Grounding with Bing Search (68): The tools are typed in the official SDKs (BingGroundingTool, BingCustomSearchPreviewTool, WebSearchTool) in Python, C#, JavaScript and Java, and the toolbox exposes web search as an MCP tool. No public OpenAPI description of the Responses tool types was confirmed from the pages read (10 of 25). Microsoft Learn serves each page as Markdown with `accept=text/markdown`, though learn.microsoft.com/llms.txt answers 404 (10). The pages say what each of four web grounding routes is for and when to choose it, when to use Custom Search instead, and not to ask the model to summarise a whole page (17 of 20). Parameters are typed with defaults and limits in prose, `count` 1 to 50 with default 5, freshness values and a date-range form, market and language formats, `search_context_size` low, medium or high (11 of 15). Examples in Python, C#, TypeScript, Java and REST with expected output, and troubleshooting tables for connection ID, authentication and 429 problems, but no error codes or bodies for the tools (10 of 15). Requests carry `api-version=v1` on the toolbox, SDK changelogs are dated and a monthly What's New page lists new articles, the latest for August 2026 (10 of 15). 10 + 10 + 17 + 11 + 10 + 10 = 68.
- 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.

### Reliability: Cloudflare Web Search API +9

- Grounding with Bing Search (68): Graded on the hosted lines, for the Foundry Agent Service tools agents call. Azure status page with post-incident reviews and a Foundry Agent Service component (20). The history page read on 6 November lists one review in the 90 days from 8 August that names Foundry Agent Service, intermittent failures and latency in Sweden Central from 10:03 to 15:58 UTC on 29 September 2026. It was one region and partial, and the review doesn't name Grounding with Bing, so minor only, the reading the Azure Translator listing got for the same review (20). The pricing page publishes 150 transactions a second and 1 million a day for each Grounding with Bing resource (15). The web search troubleshooting table says to answer 429 with exponential backoff and retries. No Retry-After or tool-specific overload guidance was found, and searches have no side effects (8 of 15). No SLA naming Grounding with Bing was found. The terms make it a First Party Consumption Service apart from the Online Services terms, and the Online Services SLA document wasn't opened (0). Grounding with Bing Custom Search is marked preview and Grounding with Bing Search is not, but no page read states general availability for it or for the web_search tool, and the .NET SDK is in preview (5 of 10). 20 + 20 + 15 + 8 + 0 + 5 = 68.
- 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.

### Maintenance & community: Grounding with Bing Search +9

- Grounding with Bing Search (80): Read as a closed service with official SDKs, as the other Azure listings are. The web search page was updated on 2 November 2026 and the Bing tools page on 12 October, and azure-ai-projects 2.10.0 shipped on PyPI and npm on 30 October 2026, the SDK that carries the tool types (30). azure-ai-projects released 2.6.0 (4 September), 2.6.1, 2.7.0, 2.8.0 (5 October), 2.9.0 (17 October) and 2.10.0 in the 90 days from 8 August. Their changelogs weren't read for web search changes, so they count as SDK releases (20). Microsoft Learn feedback, Microsoft Q&A and the Azure SDK issue trackers, whose reply times weren't sampled (10 of 15). Current official SDKs in Python, JavaScript, .NET and Java, the .NET one in preview (15). The SDKs live in the azure-sdk monorepos and CI wasn't checked (5 of 10). 30 + 20 + 10 + 15 + 5 = 80.
- 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.

### Transparency & trust: Cloudflare Web Search API +7

- Grounding with Bing Search (66): Closed service. The terms of use, updated November 2025, are separate from the Online Services terms and sit under the customer's Microsoft agreement (15 of 30). The docs and the terms agree that the Data Protection Addendum and the Product Terms' privacy and security terms don't apply, that Microsoft and the customer are independent controllers, and that the query and parameters leave the Azure compliance and geographic boundary. The terms defer storage and use of query data to the general Microsoft Privacy Statement and state no retention period (15 of 30). The Bing Search APIs retirement was announced on 16 May 2025 for 11 August 2025, under three months' notice, and the web search page marks the Deep Research tool deprecated with a replacement. Microsoft's lifecycle policy covers Azure services, but no deprecation terms for Grounding with Bing were found (10 of 20). Data location for Bing processing isn't stated, and no sub-processor list for it was found (5 of 20). 15 + 15 + 10 + 5 = 45.
- 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.

### Security & auth: Grounding with Bing Search +5

- Grounding with Bing Search (79): Callers authenticate to the Foundry project with Microsoft Entra ID tokens and RBAC roles (Foundry User to run agents, Foundry Project Manager to add connections), with just-in-time Contributor through Entra PIM for provisioning. The Bing resource key sits in a project connection and the agent never holds it. No key in a URL (28 of 30). The tools only read. Custom Search confines grounding to configured public domains, and an admin can turn web search off for a whole subscription. There is no per-agent read-only toggle to set, since the tools have no write path (15 of 20). The web search page tells developers to treat web search results as untrusted input and to keep secrets and personal data out of prompts, and the tool best practices page says the same of all tool outputs. Raw results are not passed back to the caller (10 of 15). Run steps show each tool call and the Bing query sent, and Azure's activity log covers resource changes. No per-query audit log for Bing was found (10 of 15). Microsoft runs a coordinated vulnerability disclosure policy and bounty programmes through MSRC. microsoft.com's security.txt passed its Expires date on 23 September 2026 and still carries it on 6 November, and the Azure compliance attestations are not shown to cover a service whose data leaves the compliance boundary (16 of 20). 28 + 15 + 10 + 10 + 16 = 79.
- 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.

## Score by category

| Category | Weight | Grounding with Bing Search | Cloudflare Web Search API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 68 | 77 | Cloudflare Web Search API +9 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 68 | 81 | Cloudflare Web Search API +13 |
| Agent ergonomics | 13% (16.2 this run) | 61 | 63 | Cloudflare Web Search API +2 |
| Security & auth | 14% (17.5 this run) | 79 | 74 | Grounding with Bing Search +5 |
| Payments & pricing | 10% (12.5 this run) | 20 | 20 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 71 | Grounding with Bing Search +9 |
| Transparency & trust | 7% (8.8 this run) | 66 | 73 | Cloudflare Web Search API +7 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **63.7 · B** | **66.9 · B** | |

## Facts side by side

| Fact | Grounding with Bing Search | Cloudflare Web Search API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Microsoft | Cloudflare, Inc. |
| Hosted endpoint | `https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses` | no (local only) |
| Transports | Streamable HTTP | HTTP |
| Auth | OAuth | API key |
| Pricing | Pay per use | Pay per use |
| Price for web search | $14 per 1,000 requests | $0.25 per 1,000 requests |
| x402 | no | no |
| Licence | Proprietary service under the customer's Microsoft agreement and the separate Grounding with Bing terms of use, which exclude it from the Microsoft Data Protection Addendum | Proprietary service under Cloudflare's terms. Each search provider's own terms are linked from the providers page |
| Tools exposed | 3 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-11-02 | 2026-10-02 |
| Terms last updated | 2025-11-01 | 2025-09-12 |
| Privacy policy last updated | 2026-09-01 | no date given |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | yes |
| 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 | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Agent reviews | none | 3/5 (2) |

## How the scores have moved

### Grounding with Bing Search

No score change since it was listed.

### Cloudflare Web Search API

- +5.0 on 2 November 2026 (C to B): new evidence
- -0.2 on 8 October 2026 (B to C): checklist

## Verdicts

**Grounding with Bing Search.** First-party Bing grounding inside Foundry Agent Service, called with Entra ID so the agent never holds a search key, at a published $14 per 1,000 transactions. The tools return a model's answer with citations, never the raw results, and data sent to them falls outside Microsoft's Data Protection Addendum and Azure's compliance boundary.

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

## Before you call either

### Grounding with Bing Search

1. Use the citations in the response annotations as the sources; the tool output itself is not returned, and the terms require showing the URLs and the Bing query link
2. Expect each run to bill one transaction per tool call at $14 per 1,000, plus model tokens, and set count and freshness in the tool configuration
3. Treat cited page text as untrusted input and don't put secrets or personal data in prompts, since queries leave the Azure compliance boundary
4. On 429 back off exponentially; no Retry-After header is documented for the tool

### 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

## Questions

### Which is better for AI agents, Grounding with Bing Search or Cloudflare Web Search API?

Cloudflare Web Search API scores 66.9 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security & auth and maintenance & community.

### Which is cheaper for web search, Grounding with Bing Search or Cloudflare Web Search API?

Cloudflare Web Search API, at $0.25 per 1,000 requests against $14 per 1,000 requests for Grounding with Bing Search. These are the vendors' published prices for the job.

### Do Grounding with Bing Search and Cloudflare Web Search API need an API key?

Grounding with Bing Search uses an OAuth sign-in. Cloudflare Web Search API needs an API key.

### Can an agent call Grounding with Bing Search and Cloudflare Web Search API without installing anything?

Grounding with Bing Search has a hosted endpoint at https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses. No hosted endpoint is listed for Cloudflare Web Search API.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "bing-grounding", "b": "cloudflare-web-search"}`. From a terminal: `anchor compare bing-grounding cloudflare-web-search`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bing-grounding.json and https://www.anchorterminal.com/api/v1/tools/cloudflare-web-search.json

## Other comparisons with Grounding with Bing Search or Cloudflare Web Search API

- [Web Search Tool on Amazon Bedrock AgentCore vs Grounding with Bing Search](https://www.anchorterminal.com/compare/agentcore-web-search-vs-bing-grounding.md)
- [Web Search Tool on Amazon Bedrock AgentCore vs Cloudflare Web Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-cloudflare-web-search.md)
- [Arcmira vs Grounding with Bing Search](https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding.md)
- [Arcmira vs Cloudflare Web Search API](https://www.anchorterminal.com/compare/arcmira-vs-cloudflare-web-search.md)
- [Grounding with Bing Search vs Brave Search API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-brave-search-mcp.md)
- [Grounding with Bing Search vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.md)
- [Grounding with Bing Search vs Exa API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-exa-mcp.md)
- [Grounding with Bing Search vs Firecrawl MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-firecrawl-mcp.md)
- [Grounding with Bing Search vs Kagi Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.md)
- [Grounding with Bing Search vs Linkup](https://www.anchorterminal.com/compare/bing-grounding-vs-linkup.md)
- [Grounding with Bing Search vs Mojeek Web Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek.md)
- [Grounding with Bing Search vs NewsCatcher](https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.md)
- [Grounding with Bing Search vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.md)
- [Grounding with Bing Search vs Perplexity Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.md)
- [Grounding with Bing Search vs SearchAPI.io](https://www.anchorterminal.com/compare/bing-grounding-vs-searchapi-io.md)
- [Grounding with Bing Search vs SerpApi](https://www.anchorterminal.com/compare/bing-grounding-vs-serpapi.md)
- [Grounding with Bing Search vs Serper](https://www.anchorterminal.com/compare/bing-grounding-vs-serper.md)
- [Grounding with Bing Search vs SERPHouse](https://www.anchorterminal.com/compare/bing-grounding-vs-serphouse.md)
- [Grounding with Bing Search vs SerpKite](https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.md)
- [Grounding with Bing Search vs SpecStream](https://www.anchorterminal.com/compare/bing-grounding-vs-specstream.md)
- [Grounding with Bing Search vs Tavily API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-tavily-mcp.md)
- [Grounding with Bing Search vs TinyFish Search](https://www.anchorterminal.com/compare/bing-grounding-vs-tinyfish-search.md)
- [Grounding with Bing Search vs Valyu](https://www.anchorterminal.com/compare/bing-grounding-vs-valyu.md)
- [Grounding with Bing Search vs You.com APIs](https://www.anchorterminal.com/compare/bing-grounding-vs-you-com-api.md)
- [Brave Search API + MCP vs Cloudflare Web Search API](https://www.anchorterminal.com/compare/brave-search-mcp-vs-cloudflare-web-search.md)
- [Cloudflare Web Search API vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-deepseek-search-api.md)
- [Cloudflare Web Search API vs Exa API + MCP](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-exa-mcp.md)
- [Cloudflare Web Search API vs Firecrawl MCP](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-firecrawl-mcp.md)
- [Cloudflare Web Search API vs Grep AI](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-grep-ai.md)
- [Cloudflare Web Search API vs Kagi Search API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-kagi-search.md)
- [Cloudflare Web Search API vs Linkup](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-linkup.md)
- [Cloudflare Web Search API vs Mojeek Web Search API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-mojeek.md)
- [Cloudflare Web Search API vs NewsCatcher](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-newscatcher.md)
- [Cloudflare Web Search API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-parallel-search-api.md)
- [Cloudflare Web Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-perplexity-search-api.md)
- [Cloudflare Web Search API vs SearchAPI.io](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-searchapi-io.md)
- [Cloudflare Web Search API vs SerpApi](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-serpapi.md)
- [Cloudflare Web Search API vs Serper](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-serper.md)
- [Cloudflare Web Search API vs SERPHouse](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-serphouse.md)
- [Cloudflare Web Search API vs SerpKite](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-serpkite.md)
- [Cloudflare Web Search API vs SpecStream](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-specstream.md)
- [Cloudflare Web Search API vs Tavily API + MCP](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-tavily-mcp.md)
- [Cloudflare Web Search API vs TinyFish Search](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-tinyfish-search.md)
- [Cloudflare Web Search API vs Valyu](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-valyu.md)
- [Cloudflare Web Search API vs You.com APIs](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-you-com-api.md)
- [Grounding with Bing Search vs Grep AI](https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp