# Grounding with Bing Search vs Parallel Search and Task APIs (slim)

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

- Full: https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.md (~6,800 tokens) · this version ~3,830 tokens · JSON https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.json · canonical https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Parallel Search and Task APIs scores 75 (BB) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on security & auth. Both do web search. Parallel Search and Task APIs is cheaper for web search, $1 against $14 per 1,000 requests.

- Grounding with Bing Search: B 63.7, rank #502 of 1486 · https://www.anchorterminal.com/tools/bing-grounding.min.md
- Parallel Search and Task APIs: BB 75, rank #73 of 1486 · https://www.anchorterminal.com/tools/parallel-search-api.min.md
- Grounding with Bing Search, 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 45.
- Parallel Search and Task APIs, good for Agents that mix quick search with long research or enrichment jobs and want one vendor and one bill. Ahead on Reliability, 75 against 68; Schema & documentation, 94 against 68; Agent ergonomics, 87 against 61; Payments & pricing, 75 against 20; Maintenance & community, 87 against 80. Also Cheaper for web search, $1 against $14 per 1,000 requests; Agent-ready, a grade of BB or better.

| Category | Grounding with Bing Search | Parallel Search and Task APIs |
| --- | --- | --- |
| Reliability (16%) | 68 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 68 | 94 |
| Agent ergonomics (13%) | 61 | 87 |
| Security & auth (14%) | 79 | 45 |
| Payments & pricing (10%) | 20 | 75 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 87 |
| Transparency & trust (7%) | 66 | 65 |

| Fact (where they differ) | Grounding with Bing Search | Parallel Search and Task APIs |
| --- | --- | --- |
| Vendor | Microsoft | Parallel Web Systems |
| Hosted endpoint | `https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses` | `https://api.parallel.ai/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 | $1 per 1,000 requests |
| x402 | no | payer tooling only |
| 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 | 6 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | not listed | `ai.parallel/search-mcp` |
| Last release | 2026-11-02 | 2026-10-28 |
| Terms last updated | 2025-11-01 | 2026-10-17 |
| Privacy policy last updated | 2026-09-01 | 2026-08-11 |
| Terms restrict automated access | yes | not found in the text |
| Popularity | none | 28 stars, 250k npm/wk, 994k PyPI/wk |
| Agent reviews | none | 3.6/5 (8) |

Why the edge:
- Payments & pricing, Parallel Search and Task APIs +55: 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).); Parallel Search and Task APIs 75 (Parallel runs a separate gateway at parallelmpp.dev that takes x402 (USDC on Base) and MPP (Stripe or Tempo) for search and extract at $0.01 and an ultra task at $0.30. Our unpaid POST to /api/search on 6 October returned 402 with an x402 v2 challenge for 10000 base units on eip155:8453 and a Tempo MPP challenge. Nothing on api.parallel.ai, and the gateway sells one price per endpoint with no mode choice, so partial (25). Per-unit prices published without login (20). Up to 5,000 free requests a month, $5 monthly credit and up to $80 at signup on the pricing page, which still doesn't say whether a card is needed (10). The hosted Search MCP works with no key, and the gateway needs only a wallet (20).)
- Security & auth, Grounding with Bing Search +34: 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.); Parallel Search and Task APIs 45 (API key in `x-api-key`. The Search MCP takes a Bearer key or OAuth at /mcp-oauth. We found no key scopes (20). Every Search and Extract action is a read, and Task tools live in a separate MCP server, so the search server is a read-only subset (15). Excerpts and fetched pages are untrusted web text, and the docs index has no prompt-injection guidance (0). No audit log found (0). The privacy policy shows a SOC 2 badge and links trust.parallel.ai, which rendered only its title to our reader on 6 October. security.txt is 404 on parallel.ai and docs.parallel.ai, and no bug bounty found (10).)
- Schema & documentation, Parallel Search and Task APIs +26: 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.); Parallel Search and Task APIs 94 (Public OpenAPI at docs.parallel.ai/public-openapi.json, linked from llms.txt (25). llms.txt and Markdown pages (10). A live `tools/list` on search.parallel.ai/mcp on 17 October and again on 1 November returned the two definitions, and the newer Parallel MCP server at mcp.parallel.ai adds `web_decisions`, whose description says when to use web_search instead. `web_search` states its purpose and ideal uses, and `web_fetch` says to use it "only when web_search excerpts are insufficient". The docs add that domain filters are hard filters that can cut quality. `web_search` has no when-not-to line of its own (17). Typed JSON Schema inputs with required fields and an output schema on both tools, `mode` is an enum in the API, and Task output schemas are JSON Schema. The MCP inputs carry no enums (12). The errors page lists each code with whether to retry and what to do, and 422s carry a structured `detail` (15). A dated changelog, newest entry 26 October 2026 (Decisions API) after 19 October (EU data residency), and beta headers retire on dated entries (15).)
- Agent ergonomics, Parallel Search and Task APIs +26: 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.); Parallel Search and Task APIs 87 (The Search MCP has two tools, about 5,700 characters of names, descriptions and input schemas on 1 November, and the Parallel MCP server lists three without a key (about 9,700 characters) and a fourth, `web_research`, after sign-in. `web_fetch` returns excerpts unless `full_content` is set, and the docs cap excerpts at roughly 25,000 characters a call and warn full pages can run to tens of thousands of tokens (25). Result counts, excerpt settings and source policies for domains and paths (18). The errors table gives each code a retry column and a resolution, with troubleshooting for 402 and 429 and a structured `detail` on 422 (20). Both Search MCP tools carry readOnlyHint true, destructiveHint false and idempotentHint true in the live `tools/list`, and searches are safe to repeat. There's still no idempotency key for Task creation, the SDKs retry creates on 429 and 5xx, and the Task MCP needs a key, so its annotations weren't read (14). Python and TypeScript SDKs, but `mode` defaults to advanced, the $5 per 1,000 tier, when you leave it out (10).)
- Reliability, Parallel Search and Task APIs +7: 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.); Parallel Search and Task APIs 75 (incident.io page at status.parallel.ai with Search, Task, Chat, Monitor, FindAll and Entity Search components and history (20). The feed, re-read on 1 November, has nothing after 13 October, so the 90 days from 3 August hold the same four incidents, all partial or degraded. Elevated 503s on 6 August, about an hour of Task API latency on 2 September, intermittent 4xx errors on 7 September, and transient 502s from the network gateway on 13 October, degraded performance from 01:23 to 01:43 UTC. Most have no duration listed (20). Published limits, 600 a minute for Search, Image Search, Extract, Decisions and Entity Search, 2,000 for Tasks, 300 for Chat and Monitor (15). The errors page marks 429 as retryable with exponential backoff, but there's no `Retry-After` and no idempotency guidance for creating Task runs, which the SDKs retry twice by default (10). No SLA found (0). Search, Extract and Task are GA (10).)
- Maintenance & community, Parallel Search and Task APIs +7: 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.); Parallel Search and Task APIs 87 (parallel-web 1.3.7 for Python on 2026-10-23 and for TypeScript on 2026-10-28, and changelog entries on 19 and 26 October, the second launching the Decisions API (30). Counted from the tags and the changelog, the 90 days from 3 August hold Python SDK releases 1.3.1 to 1.3.7, TypeScript 1.3.1 to 1.3.7 and ten changelog entries from 19 August to 26 October (20). The SDK releases since 1.3.5 are dependency bumps. Closed service with a changelog and support@parallel.ai. We didn't test whether support answers (12). Current Python and TypeScript SDKs, and ai.parallel/search-mcp and ai.parallel/task-mcp in the official registry (15). The Python SDK runs lint and build in CI on push, plus a workflow that detects breaking changes (10).)