# Grounding with Bing Search vs SearchAPI.io

> Grounding with Bing Search scores 63.7 (B) to SearchAPI.io's 50.1 (D) for web search. SearchAPI.io is cheaper for web search, $4 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-searchapi-io
- Markdown: https://www.anchorterminal.com/compare/bing-grounding-vs-searchapi-io.md (~6,050 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

Grounding with Bing Search scores 63.7 (B) on agent readiness against SearchAPI.io's 50.1 (D), and leads in 5 of 7 scored categories. SearchAPI.io leads on reliability and payments & pricing. Both do web search. SearchAPI.io is cheaper for web search, $4 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
- SearchAPI.io: grade D, 50.1/100, rank #1065 of 1486. Markdown https://www.anchorterminal.com/tools/searchapi-io.md · JSON https://www.anchorterminal.com/api/v1/tools/searchapi-io.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:
- Schema & documentation, 68 against 59
- Agent ergonomics, 61 against 52
- Security & auth, 79 against 28
- Maintenance & community, 80 against 0

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

### SearchAPI.io (D)

Good for: Agents that need parsed results from many engines, especially shopping, ads, travel and social sources, at a low price per search.

Ahead on:
- Reliability, 90 against 68
- Payments & pricing, 30 against 20

Also in its favour:
- Cheaper for web search, $4 against $14 per 1,000 requests
- Free to start without a card

Watch for: MCP loads one tool per engine with no toolsets


## Why the edge

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

- 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.
- SearchAPI.io (0): No changelog (/changelog answered 404 on 4 November 2026) and no dated API change found, so the last release can't be dated (0). No releases to count (0). No public issue tracker or changelog to judge replies by. A Discord server is linked from the footer and wasn't tested (0). The 15 for io.searchapi/mcp in the official MCP registry rested on a reading of the registry's JSON API, which this run doesn't use, and no ordinary registry page shows the entry, so the line falls to 0, as graphiti, linear-mcp and copilot-studio-mcp read it. No official SDKs were found; the footer links a GitHub organisation whose pages answered 403 (0, 15 before). No public packages or CI (0). 0 + 0 + 0 + 0 + 0 = 0.

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

- 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.
- SearchAPI.io (28): API keys with a documented `api_key` query-string option, and OAuth with expiring, rotating tokens for the MCP. The MCP page, re-read on 4 November 2026, now tells clients to send the token in the `X-MCP-Token` header and not in a URL. The registry's `?token=` reading came from a JSON API this run doesn't use and is struck. The `api_key` query option stays documented in the API reference. 20 less 10 (10). Every action is a read, and there are no tool subsets (15). Results are third-party snippets and scraped AI answers, with no injection guidance (0). No per-call audit log found. The privacy policy says account logins are logged by IP (0). The trust centre at security.searchapi.io answers robots.txt with an app page, so it was left unread on 4 November 2026. No certifications, bounty or security.txt (404 on 4 November 2026) found. The partial 3 is kept pending the founder's rule on in-between values (3).

### Reliability: SearchAPI.io +22

- 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.
- SearchAPI.io (90): Honeybadger status page at status.searchapi.io with Landing Page and API components and monthly history (20). Re-read on 4 November 2026, it shows no incidents in September, October or November 2026, and its incident feed's newest entry is the 11 February 2026 partial outage, so the window from 6 August is clean (30). The hourly cap is published, 20 per cent of the plan's monthly searches in any hour (15). The OpenAPI file lists a 429 response with an error string, but no `Retry-After` or backoff guidance was found. The partial 5 is kept pending the founder's rule on in-between values (5). The terms of 11 April 2026 give a 99.9% SLA for all plans with a credit of 100% of the monthly price, and the pricing page lists it on every plan (10). GA (10). 20 + 30 + 15 + 5 + 10 + 10 = 90.

### Payments & pricing: SearchAPI.io +10

- Grounding with Bing Search (20): No x402, MPP or L402 (0). $14 per 1,000 transactions for Grounding with Bing Search and Custom Search, published on microsoft.com without a login (20). No free tier for Grounding with Bing, and an Azure subscription needs a card, as on the Azure Translator listing (0). A person signs up for Azure, creates a Foundry project and, for bing_grounding, a Bing resource (0).
- SearchAPI.io (30): No x402, MPP or L402 (0). Monthly plans only, priced in public, from $40 for 10,000 searches to $5,000 for 5 million (10). 100 free requests with no card (20). A person has to sign up in a browser (0).

### Schema & documentation: Grounding with Bing Search +9

- 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.
- SearchAPI.io (59): OpenAPI 3.0 for the Google engine at /openapi/google.yaml with 25 typed parameters. We found no index of specs for the other engines, so 20 of 25. No llms.txt (404 on 4 November 2026) and no Markdown docs for agents (0). The API reference explains each parameter, and the MCP tool definitions aren't public (10). Enums for device, country, language, safe search and time period (14). Examples and a Postman collection, and the spec documents 400, 401, 403, 429 and 500 (12). /api/v1 in the path and no changelog anywhere we looked (3).

### Agent ergonomics: Grounding with Bing Search +9

- Grounding with Bing Search (61): Read as a server-side search tool inside an agent run. The tools return a model's answer with citations rather than raw results, and `search_context_size` sets how much context web search uses. A caller can't size or inspect the result set itself, since the Bing tools never return their output. Custom Search confines grounding to chosen domains without code (18 of 25). `count`, freshness, market and language filters, and domain restriction through Custom Search. No pagination or offset (13 of 20). Troubleshooting tables give causes and fixes for connection ID, RBAC and 429 problems, but the tools document no error codes (8 of 20). Searches only read, so a retry is safe apart from the per-transaction charge. No MCP annotations are documented for the toolbox's web search tool (10 of 20). The web_search route needs only a project, a model deployment and the Foundry User role. bing_grounding also needs a paid Bing resource and a project connection. SDKs in Python, C#, JavaScript and Java (12 of 15). Prompt caching gets no hits with the Bing tools, because they add a timestamp to every request. 18 + 13 + 8 + 10 + 12 = 61.
- SearchAPI.io (52): The MCP exposes over 100 tools, one or more per engine, with no toolsets or filtering documented (5). `page`, `time_period`, location, country, language and safe search. Google's `num` has been fixed at 10 since September 2025 (18). Status codes are documented, but not how to recover from each (12). Searches are reads, and only HTTP 200 responses are billed, so retries are cheap. MCP annotations aren't visible (10). Two required parameters, `engine` and `q`. No official SDKs (7).

## Score by category

| Category | Weight | Grounding with Bing Search | SearchAPI.io | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 68 | 90 | SearchAPI.io +22 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 68 | 59 | Grounding with Bing Search +9 |
| Agent ergonomics | 13% (16.2 this run) | 61 | 52 | Grounding with Bing Search +9 |
| Security & auth | 14% (17.5 this run) | 79 | 28 | Grounding with Bing Search +51 |
| Payments & pricing | 10% (12.5 this run) | 20 | 30 | SearchAPI.io +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 0 | Grounding with Bing Search +80 |
| Transparency & trust | 7% (8.8 this run) | 66 | 62 | Grounding with Bing Search +4 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **63.7 · B** | **50.1 · D** | |

## Facts side by side

| Fact | Grounding with Bing Search | SearchAPI.io |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Microsoft | SearchApi |
| Hosted endpoint | `https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses` | `https://www.searchapi.io/api/v1/search` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for web search | $14 per 1,000 requests | $4 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 | none |
| Tools exposed | 3 | none |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| MCP registry | not listed | `io.searchapi/mcp` |
| Last release | 2026-11-02 | none |
| Terms last updated | 2025-11-01 | 2026-04-11 |
| Privacy policy last updated | 2026-09-01 | 2026-04-11 |
| 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 | not found in the text |
| Agent reviews | none | 3/5 (2) |

## How the scores have moved

### Grounding with Bing Search

No score change since it was listed.

### SearchAPI.io

- -1.3 on 4 November 2026: correction
- +0.2 on 27 October 2026: checklist
- -0.2 on 8 October 2026: 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.

**SearchAPI.io.** A 99.9% SLA in the terms on every plan, no status-page incidents since 11 February 2026, and over 150 engine endpoints behind one URL. The MCP loads one tool per engine with no toolsets, there is no changelog or official SDK, and every account starts with a browser signup.

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

### SearchAPI.io

1. Send the key as `Authorization: Bearer`, not `api_key=` in the URL
2. Connect the MCP through OAuth or the `X-MCP-Token` header. Never put the token in the MCP URL
3. Call the REST API with `engine=` when context is tight. The MCP loads one tool definition per engine
4. Page Google results with `page`. `num` is fixed at 10
5. Pace bursts. One hour can use at most 20 per cent of the plan's monthly searches

## Questions

### Which is better for AI agents, Grounding with Bing Search or SearchAPI.io?

Grounding with Bing Search scores 63.7 (B) on agent readiness against SearchAPI.io's 50.1 (D), and leads in 5 of 7 scored categories. SearchAPI.io leads on reliability and payments & pricing.

### Which is cheaper for web search, Grounding with Bing Search or SearchAPI.io?

SearchAPI.io, at $4 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 SearchAPI.io need an API key?

Grounding with Bing Search uses an OAuth sign-in. SearchAPI.io takes an API key or an OAuth sign-in.

### Can an agent call Grounding with Bing Search and SearchAPI.io without installing anything?

Yes. Grounding with Bing Search has a hosted endpoint at https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses and SearchAPI.io at https://www.searchapi.io/api/v1/search.


## For agents

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

## Other comparisons with Grounding with Bing Search or SearchAPI.io

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