{ "data": { "a": { "slug": "bing-grounding", "name": "Grounding with Bing Search", "vendor": "Microsoft", "vendorUrl": "https://www.microsoft.com/bing/apis", "kind": "http-api", "category": "search", "summary": "Grounding with Bing Search is Microsoft's web search tool for agents in Foundry Agent Service. A Foundry model searches Bing during a Responses API run and returns an answer with URL citations, through the bing_grounding and web_search tools.", "url": "https://www.anchorterminal.com/tools/bing-grounding", "markdownUrl": "https://www.anchorterminal.com/tools/bing-grounding.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bing-grounding.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bing-grounding.json", "dns": "bing-grounding.grade.anchorterminal.com", "license": "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", "transports": [ "streamable-http" ], "remoteUrl": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "packages": [ { "registry": "pypi", "name": "azure-ai-projects" }, { "registry": "npm", "name": "@azure/ai-projects" } ], "auth": "oauth", "authNotes": "Microsoft Entra ID bearer token for the Foundry project (scope https://ai.azure.com/.default, for example through DefaultAzureCredential), with the Foundry User role to create and run agents. The bing_grounding tool also needs a Grounding with Bing resource whose key is stored in a project connection, created by someone with Contributor and Foundry Project Manager. The agent never holds the Bing key. The web_search tool needs no Bing resource or connection.", "pricing": "usage", "pricingNotes": "$14 per 1,000 transactions for Grounding with Bing Search and for Grounding with Bing Custom Search, counted as tool calls per run, plus the model deployment's token charges. No free tier found. An Azure subscription and a person's signup are needed first.", "priceSummary": "$14 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Foundry web search and Bing tools pages, the Grounding with Bing pricing page or the terms of use (checked 2026-11-06). Billing runs through the Azure subscription.", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/tools/web-search", "capabilities": [ "web.search", "search.answer" ], "tags": [ "hosted", "usage-priced", "closed-source", "enterprise", "card-required", "status-page", "python", "typescript" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 63.7, "grade": "B", "agentReady": false, "rank": 502, "ranked": true, "rankOf": 1486, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 61, "maintenance": 80, "payments": 20, "reliability": 68, "schema": 68, "security": 79, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.", "strengths": [ "Callers authenticate with Microsoft Entra ID and Foundry RBAC roles, and the Bing resource key stays in a project connection", "Price and limits published without a login, $14 per 1,000 transactions, 150 a second and 1 million a day", "Count, freshness, market and language parameters, and a Custom Search variant that limits grounding to chosen domains", "Docs say to treat web search results as untrusted input, and admins can turn web search off for a whole subscription" ], "weaknesses": [ "The Bing tools never return raw results to developers, only a model-written answer with citation links", "The Data Protection Addendum does not apply and query data leaves the Azure compliance and geographic boundary", "No free tier, and a first call needs an Azure subscription, a Foundry project, a model deployment and, for bing_grounding, a paid Bing resource", "Terms forbid using Bing output to train or evaluate AI models and limit storing or caching it" ], "agentNotes": [ "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", "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", "Treat cited page text as untrusted input and don't put secrets or personal data in prompts, since queries leave the Azure compliance boundary", "On 429 back off exponentially; no Retry-After header is documented for the tool" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.7 } ], "editorialScores": { "ergonomics": 61, "maintenance": 80, "payments": 20, "reliability": 68, "schema": 68, "security": 79, "transparency": 45 }, "provenanceScore": 87, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install azure-ai-projects azure-identity", "http": "curl -X POST \"$FOUNDRY_PROJECT_ENDPOINT/openai/v1/responses\" \\\n -H \"Authorization: Bearer $AGENT_TOKEN\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"model\":\"'$FOUNDRY_MODEL_DEPLOYMENT_NAME'\",\"input\":\"How does Wikipedia explain Euler identity?\",\"tool_choice\":\"required\",\"tools\":[{\"type\":\"bing_grounding\",\"bing_grounding\":{\"search_configurations\":[{\"project_connection_id\":\"'$BING_PROJECT_CONNECTION_ID'\",\"count\":7,\"market\":\"en-US\",\"set_lang\":\"en\",\"freshness\":\"week\"}]}}]}'" }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/bing-grounding" }, "sameCompany": [ "azure-openai", "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-key-vault", "azure-document-intelligence", "azure-devops-mcp", "microsoft-learn-mcp", "tokeneconomizer", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "azure-blob-storage", "onedrive-sharepoint", "microsoft-teams", "dynamics-365-sales", "copilot-studio-mcp", "power-automate", "foundry-local", "microsoft-decision-1", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph", "microsoft-graph-people", "mage-vl-cowork" ], "area": "web-data", "unitPrices": [ { "item": "Grounding with Bing Search transaction", "unit": "1k-requests", "usd": 14, "note": "Counted as tool calls per run, plus the model deployment's token charges" }, { "item": "Grounding with Bing Custom Search transaction", "unit": "1k-requests", "usd": 14, "note": "Same limits, 150 a second and 1 million a day" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/bing/apis/grounding-legal-enterprise", "privacy": "https://privacy.microsoft.com/en-us/privacystatement", "statusPage": "https://azure.status.microsoft/en-us/status", "changelog": "https://learn.microsoft.com/en-us/azure/foundry/whats-new-foundry", "securityTxt": "expired", "checked": "2026-11-06", "notes": [ "The Foundry project endpoint is on services.ai.azure.com, a Microsoft domain. Domain registration date carried from the Azure listings' provenance.", "The Grounding with Bing terms of use (updated November 2025) are subject to the customer's Microsoft agreement (MCA, MBSA or MOSA) and name no separate contracting entity. They forbid using output on sites that block the customer's crawler, using links for crawling or scraping, and bypassing transaction limits.", "www.microsoft.com/.well-known/security.txt still carries Expires 2026-09-23T16:00:00.000Z on 6 November 2026.", "learn.microsoft.com/robots.txt allows the documentation paths read. The Azure status history page lists post-incident reviews for five years." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bing-grounding.json", "live": { "slug": "bing-grounding", "probe": { "target": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "method": "get", "lastAt": "2026-11-07T18:20:13.927615013Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "invalid character \"{\" in host name", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 0 }, { "date": "2026-11-07", "probes": 187, "ok": 0 } ], "outages": [ { "start": "2026-11-06T22:45:07.390416052Z", "end": "0001-01-01T00:00:00Z", "note": "invalid character \"{\" in host name" } ] }, "versions": [ { "registry": "npm", "name": "@azure/ai-projects", "version": "2.10.0", "seenAt": "2026-11-06T23:11:06.900508365Z" }, { "registry": "pypi", "name": "azure-ai-projects", "version": "2.10.0", "released": "2026-10-30", "seenAt": "2026-11-06T23:11:05.00335007Z" } ], "npmWeekly": 1368538, "pypiWeekly": 1896178, "securityTxt": { "url": "https://microsoft.com/.well-known/security.txt", "state": "valid", "expires": "2027-10-27T16:00:00.000Z", "checkedAt": "2026-11-07T16:02:01.196666056Z" }, "pages": [ { "url": "https://www.microsoft.com/bing/apis/grounding-legal-enterprise", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:31:40.128456318Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ddf25722851a" } ], "updatedAt": "2026-11-07T18:20:13.927615013Z" } }, "answer": "Grounding with Bing Search scores 63.7 (B) on agent readiness against DeepSeek Search and Fetch API's 55.5 (C), and leads in 4 of 7 scored categories. DeepSeek Search and Fetch API leads on agent ergonomics.", "b": { "slug": "deepseek-search-api", "name": "DeepSeek Search and Fetch API", "vendor": "DeepSeek", "vendorUrl": "https://www.deepseek.com", "kind": "http-api", "category": "search", "summary": "DeepSeek's Search and Fetch API gives agents live web results from DeepSeek's in-house search engine and single pages as Markdown, through two REST endpoints on an ordinary DeepSeek API key, billed per successful request.", "url": "https://www.anchorterminal.com/tools/deepseek-search-api", "markdownUrl": "https://www.anchorterminal.com/tools/deepseek-search-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/deepseek-search-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/deepseek-search-api.json", "dns": "deepseek-search-api.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://api.deepseek.com/v1/tools/search", "packages": [], "auth": "api-key", "authNotes": "The same DeepSeek API key as the model endpoints, sent as a bearer token. Keys carry no scopes, so a search key can also spend the balance on models. Rate limits are per account, whichever key is used.", "pricing": "usage", "pricingNotes": "$0.75 per 1,000 successful requests for Search and the same for Fetch, from a prepaid balance. Only an HTTP 200 with a result is billed, and `count` doesn't change the price. Server-side search through DeepSeek Harness, Claude Code or Codex was free until 31 October 2026 at 16:00 UTC (https://api-docs.deepseek.com/guides/search, checked 2026-10-17; DeepSeek's pages weren't re-read on 2026-11-04 because its Terms of Use bar automated copying).", "priceSummary": "$0.75 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Search and Fetch guide, the API reference or the pricing page (checked 2026-10-17).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-17" }, "docsUrl": "https://api-docs.deepseek.com/guides/search", "capabilities": [ "web.search", "web.fetch" ], "tags": [ "hosted", "prepaid", "usage-priced", "status-page" ], "lastRelease": "2026-10-17", "graded": true, "anchor": { "graded": true, "score": 55.5, "grade": "C", "agentReady": false, "rank": 861, "ranked": true, "rankOf": 1486, "categoryRank": 21, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 81, "maintenance": 42, "payments": 20, "reliability": 72, "schema": 55, "security": 43, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-04" }, "negative": 0, "verdict": "Search returns up to 50 results with a model-length summary, an authority tier and optional full text, and only successful non-empty calls are billed, at $0.75 per 1,000. It opened on 17 October 2026, with 5 requests a second per account, no OpenAPI file, no free tier, and data held in the PRC under a policy that permits training.", "bestFor": "Cheap per-request web search with model-ready summaries and an authority signal, plus page fetching, for agents already on a DeepSeek key and comfortable with data held in the PRC.", "strengths": [ "$0.75 per 1,000 successful requests for each endpoint, and failed calls, empty results and timeouts aren't billed", "Each result has a 100 to 200 character snippet, a 600 to 800 character summary for models, and full text on request", "Site, language, date and phrase operators in the query string, and up to 50 results a call", "Error table with ten status codes and when to retry, and both endpoints documented as read-only" ], "weaknesses": [ "Opened on 17 October 2026, with no service record of its own and no component for it on the status page", "5 requests a second per account for each endpoint, plus an unpublished per-domain limit on Fetch", "No OpenAPI file, no llms.txt, no official SDKs and no free tier for direct calls", "One unscoped key for search and models, no security.txt, and no prompt-injection guidance for returned page text", "Data stored in the PRC, used for training unless the customer opts out by email, and no retention period stated" ], "agentNotes": [ "Keep `query` to 128 characters and put filters in it as operators, such as `site:github.com lang:en after:2026-01-01`", "Leave `need_content` false and read `summary` first, then call Fetch on the URLs you keep", "Stay under 5 requests a second per account across all keys. On 408, 429 or 5xx wait and retry, since no Retry-After is documented", "Don't retry a Fetch 403 or 404 unchanged. The page is blocked by policy, unreachable or has no Markdown", "Don't send private queries or an end user's IP in `localization`. Data is stored in the PRC" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.5 } ], "editorialScores": { "ergonomics": 81, "maintenance": 42, "payments": 20, "reliability": 72, "schema": 55, "security": 43, "transparency": 35 }, "provenanceScore": 85, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.deepseek.com/v1/tools/search \\\n -H \"Authorization: Bearer $DEEPSEEK_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"query\":\"DeepSeek V4 release\",\"count\":5,\"need_content\":true}'" }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/deepseek-search-api" }, "sameCompany": [ "deepseek-api", "deepseek-v4-1-flash", "deepseek-v3-2", "deepseek-v4-flash-0731" ], "area": "web-data", "unitPrices": [ { "item": "Search", "unit": "1k-requests", "usd": 0.75, "note": "Successful non-empty results only. 1 to 50 results at the same price" }, { "item": "Fetch", "unit": "1k-pages", "usd": 0.75, "note": "One URL per request, billed only when page content comes back" } ], "provenance": { "legalEntity": "Hangzhou DeepSeek Artificial Intelligence Co., Ltd.", "domain": "deepseek.com", "domainRegistered": "2000-08-13", "endpointOnVendorDomain": true, "terms": "https://cdn.deepseek.com/policies/en-US/deepseek-open-platform-terms-of-service.html", "privacy": "https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html", "statusPage": "https://status.deepseek.com", "changelog": "https://api-docs.deepseek.com/updates", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "deepseek.com was registered in 2000, long before the company, so domain age flatters it (per the deepseek-api listing).", "The Open Platform terms (released 22 April, effective 29 April 2026) are a Specific Agreement under the DeepSeek Terms of Use (last update 27 March 2026), both re-read on 4 November 2026. They are governed by PRC law and assign Outputs to the customer. The Terms of Use §3.5(3) bar \"capturing, copying any content of the Services, including but not limited to using any robots, spiders, or other automatic setups, setting mirrors\". The privacy policy (10 February 2026) names Hangzhou DeepSeek Artificial Intelligence Co., Ltd.", "www.deepseek.com/.well-known/security.txt and deepseek.com/.well-known/security.txt returned 404 on 17 October 2026 (not re-read).", "cdn.deepseek.com answers robots.txt with a plain 404 (4 November 2026). Because of the Terms of Use clause, nothing else on DeepSeek's hosts (api-docs, status, www, platform) was requested on 4 November.", "The status page has a Search Service component, grouped under Chat Service, and no component named for the Search or Fetch API (17 October 2026)." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/deepseek-search-api.json", "live": { "slug": "deepseek-search-api", "probe": { "target": "https://api.deepseek.com/v1/tools/search", "method": "get", "lastAt": "2026-11-07T18:20:20.726689445Z", "lastOk": true, "lastStatus": 401, "lastMs": 333, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 288, "p95ms24h": 372, "samples24h": 239, "samples30d": 5145, "days": [ { "date": "2026-10-17", "probes": 21, "ok": 21 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.deepseek.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:37.96985213Z" }, "securityTxt": { "url": "https://deepseek.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:54.973930725Z" }, "domain": { "domain": "deepseek.com", "registered": "2000-08-13", "source": "https://rdap.verisign.com/com/v1/domain/deepseek.com", "checkedAt": "2026-11-01T14:07:48.239871757Z" }, "updatedAt": "2026-11-07T18:20:20.726689445Z" } }, "edges": [ { "by": 38, "category": "maintenance", "leads": "bing-grounding", "name": "Maintenance \u0026 community", "reasons": { "a": "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\u0026A 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.", "b": "Closed service, per the 17 October check, not re-read on 4 November (terms pause). Opened on 17 October 2026, 18 days before this check (30). The change log's 17 October entry is the only dated one about Search or Fetch in the 90 days from 6 August (0 of 20). Dated change log, api-service@deepseek.com and a Discord server, not tested for replies (12 of 15). No official SDK (0 of 15). No SDK or package to assess (0 of 10). 30 + 0 + 12 + 0 + 0 = 42." }, "scores": { "a": 80, "b": 42 } }, { "by": 36, "category": "security", "leads": "bing-grounding", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Per the 17 October check, not re-read on 4 November (terms pause). The ordinary DeepSeek bearer key, revocable, with no scopes, so a key used for search can also spend on models. No secret in a URL (20 of 30). Both endpoints only read, so there's nothing destructive to approve, but no search-only key (15 of 20). Results and fetched pages are untrusted web text. The change log says the engine filters 'SEO spam, GEO manipulation, and low-quality AIGC', with no technical detail and no prompt-injection guidance (3 of 15). No per-call log or audit log found in the docs. The platform console wasn't readable (0 of 15). Security programme 5 of 20 (was 0). The www.deepseek.com footer carries a Report Security Issue address, security@deepseek.com, per the 21 October reading used for DeepSeek's open-weight listings; no security.txt (404 on 17 October), disclosure policy, bug bounty or certification found. 20 + 15 + 3 + 0 + 5 = 43." }, "scores": { "a": 79, "b": 43 } }, { "by": 20, "category": "ergonomics", "leads": "deepseek-search-api", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "Per the 17 October check, not re-read on 4 November (terms pause). Responses can be sized with `count` and `need_content`, off by default, and each result carries both a short snippet and a 600 to 800 character summary. No field selection, and full content has no length cap stated (20 of 25). Site, language, date and phrase filters, up to 50 results, no pagination (15 of 20). Ten documented codes with what to do, 402 for an empty balance and 404 for an unfetchable page. `param` is always null and `code` repeats the type (17 of 20). Both endpoints are documented as read-only and safe to retry, and failed or empty calls aren't billed (20). Only `query` or `url` is required. No official SDKs, the docs use raw HTTP and Python requests (9 of 15). 20 + 15 + 17 + 20 + 9 = 81." }, "scores": { "a": 61, "b": 81 } }, { "by": 13, "category": "schema", "leads": "bing-grounding", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "Per the 17 October check, not re-read on 4 November (terms pause). No OpenAPI file found. The API reference is rendered from a schema, but no spec is linked, and /openapi.json and /openapi.yaml on the docs host serve the docs page (0). No llms.txt, since api-docs.deepseek.com answered /llms.txt with HTML (0). The guide says what each endpoint is for and which result field suits a UI or a model, and gives the score thresholds for quality and authority, but not when to use Search content against a Fetch (14 of 20). Types, required fields, defaults and limits on every field, such as `query` 1 to 128 characters and `count` 1 to 50. Filters live inside the free-text query (13 of 15). curl and Python examples, an error body and a table of ten status codes with retry guidance. The reference shows only the 200 response (13 of 15). Dated change log and a /v1 path (15). 0 + 0 + 14 + 13 + 13 + 15 = 55." }, "scores": { "a": 68, "b": 55 } }, { "by": 6, "category": "transparency", "leads": "bing-grounding", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "Per the 17 October check for the privacy policy, not re-read on 4 November (terms pause). Closed service with published terms under PRC law, which assign Outputs to the customer; the Open Platform terms (released 22 April, effective 29 April 2026) and the Terms of Use (last update 27 March 2026) were re-read on 4 November (15). The privacy policy of 10 February 2026 says personal data trains models unless you opt out by email and gives no retention period. It also says search runs on 'third-party APIs' that receive input keywords, which disagrees with the in-house engine described on 17 October, and nothing covers fetched URLs (5 of 30). No deprecation policy, and the only dated notice is the end of free server-side calls on 31 October (5 of 20). Data location disclosed as the PRC, third parties named only by category (10 of 20). 15 + 5 + 5 + 10 = 35." }, "scores": { "a": 66, "b": 60 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Microsoft", "b": "DeepSeek", "name": "Vendor" }, { "a": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "b": "https://api.deepseek.com/v1/tools/search", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$14 per 1,000 requests", "b": "$0.75 per 1,000 requests", "name": "Price for web search" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "none", "name": "Licence" }, { "a": "3", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-11-02", "b": "2026-10-17", "name": "Last release" }, { "a": "2025-11-01", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Grounding with Bing Search scores 63.7 (B) on agent readiness against DeepSeek Search and Fetch API's 55.5 (C), and leads in 4 of 7 scored categories. DeepSeek Search and Fetch API leads on agent ergonomics.", "question": "Which is better for AI agents, Grounding with Bing Search or DeepSeek Search and Fetch API?" }, { "answer": "DeepSeek Search and Fetch API, at $0.75 per 1,000 requests against $14 per 1,000 requests for Grounding with Bing Search. These are the vendors' published prices for the job.", "question": "Which is cheaper for web search, Grounding with Bing Search or DeepSeek Search and Fetch API?" }, { "answer": "Grounding with Bing Search uses an OAuth sign-in. DeepSeek Search and Fetch API needs an API key.", "question": "Do Grounding with Bing Search and DeepSeek Search and Fetch API need an API key?" }, { "answer": "Yes. Grounding with Bing Search has a hosted endpoint at https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses and DeepSeek Search and Fetch API at https://api.deepseek.com/v1/tools/search.", "question": "Can an agent call Grounding with Bing Search and DeepSeek Search and Fetch API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 68 against 55", "Security \u0026 auth, 79 against 43", "Maintenance \u0026 community, 80 against 42", "Transparency \u0026 trust, 66 against 60" ], "also": null, "goodFor": "Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.", "slug": "bing-grounding", "watchFor": "The Bing tools never return raw results to developers, only a model-written answer with citation links" }, { "aheadOn": [ "Agent ergonomics, 81 against 61" ], "also": [ "Cheaper for web search, $0.75 against $14 per 1,000 requests" ], "goodFor": "Cheap per-request web search with model-ready summaries and an authority signal, plus page fetching, for agents already on a DeepSeek key and comfortable with data held in the PRC.", "slug": "deepseek-search-api", "watchFor": "Opened on 17 October 2026, with no service record of its own and no component for it on the status page" } ], "history": { "bing-grounding": null, "deepseek-search-api": [ { "causes": [ "correction" ], "date": "2026-11-04", "delta": 2.3, "from": 53.2, "fromGrade": "D", "to": 55.5, "toGrade": "C" } ] }, "job": { "capability": "web.search", "name": "Web search" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-bing-grounding.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Grounding with Bing Search", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-bing-grounding" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding.json", "title": "Arcmira vs Grounding with Bing Search", "url": "https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-deepseek-search-api.json", "title": "Arcmira vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/arcmira-vs-deepseek-search-api" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-brave-search-mcp.json", "title": "Grounding with Bing Search vs Brave Search API + MCP", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-brave-search-mcp" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search.json", "title": "Grounding with Bing Search vs Cloudflare Web Search API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-exa-mcp.json", "title": "Grounding with Bing Search vs Exa API + MCP", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-exa-mcp" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-firecrawl-mcp.json", "title": "Grounding with Bing Search vs Firecrawl MCP", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-firecrawl-mcp" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.json", "title": "Grounding with Bing Search vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-linkup.json", "title": "Grounding with Bing Search vs Linkup", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek.json", "title": "Grounding with Bing Search vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.json", "title": "Grounding with Bing Search vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.json", "title": "Grounding with Bing Search vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.json", "title": "Grounding with Bing Search vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-searchapi-io.json", "title": "Grounding with Bing Search vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpapi.json", "title": "Grounding with Bing Search vs SerpApi", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serper.json", "title": "Grounding with Bing Search vs Serper", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serphouse.json", "title": "Grounding with Bing Search vs SERPHouse", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.json", "title": "Grounding with Bing Search vs SerpKite", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-specstream.json", "title": "Grounding with Bing Search vs SpecStream", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-tavily-mcp.json", "title": "Grounding with Bing Search vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-tinyfish-search.json", "title": "Grounding with Bing Search vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-valyu.json", "title": "Grounding with Bing Search vs Valyu", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-you-com-api.json", "title": "Grounding with Bing Search vs You.com APIs", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-deepseek-search-api.json", "title": "Brave Search API + MCP vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-deepseek-search-api" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-deepseek-search-api.json", "title": "Cloudflare Web Search API vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-deepseek-search-api" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-exa-mcp.json", "title": "DeepSeek Search and Fetch API vs Exa API + MCP", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-exa-mcp" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-firecrawl-mcp.json", "title": "DeepSeek Search and Fetch API vs Firecrawl MCP", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-firecrawl-mcp" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-grep-ai.json", "title": "DeepSeek Search and Fetch API vs Grep AI", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-grep-ai" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-kagi-search.json", "title": "DeepSeek Search and Fetch API vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-kagi-search" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-linkup.json", "title": "DeepSeek Search and Fetch API vs Linkup", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek.json", "title": "DeepSeek Search and Fetch API vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-newscatcher.json", "title": "DeepSeek Search and Fetch API vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-parallel-search-api.json", "title": "DeepSeek Search and Fetch API vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api.json", "title": "DeepSeek Search and Fetch API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-searchapi-io.json", "title": "DeepSeek Search and Fetch API vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpapi.json", "title": "DeepSeek Search and Fetch API vs SerpApi", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serper.json", "title": "DeepSeek Search and Fetch API vs Serper", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serphouse.json", "title": "DeepSeek Search and Fetch API vs SERPHouse", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpkite.json", "title": "DeepSeek Search and Fetch API vs SerpKite", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-specstream.json", "title": "DeepSeek Search and Fetch API vs SpecStream", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-tavily-mcp.json", "title": "DeepSeek Search and Fetch API vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-tinyfish-search.json", "title": "DeepSeek Search and Fetch API vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-valyu.json", "title": "DeepSeek Search and Fetch API vs Valyu", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-you-com-api.json", "title": "DeepSeek Search and Fetch API vs You.com APIs", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-fetch-reference-server.json", "title": "DeepSeek Search and Fetch API vs Fetch (MCP reference server)", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-fetch-reference-server" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai.json", "title": "Grounding with Bing Search vs Grep AI", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai" } ], "panel": null, "scores": [ { "bing-grounding": 68, "by": 4, "deepseek-search-api": 72, "edge": "deepseek-search-api", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bing-grounding": 68, "by": 13, "deepseek-search-api": 55, "edge": "bing-grounding", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "bing-grounding": 61, "by": 20, "deepseek-search-api": 81, "edge": "deepseek-search-api", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "bing-grounding": 79, "by": 36, "deepseek-search-api": 43, "edge": "bing-grounding", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "bing-grounding": 20, "by": 0, "deepseek-search-api": 20, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bing-grounding": 80, "by": 38, "deepseek-search-api": 42, "edge": "bing-grounding", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "bing-grounding": 66, "by": 6, "deepseek-search-api": 60, "edge": "bing-grounding", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Grounding with Bing Search scores 63.7 (B) on agent readiness against DeepSeek Search and Fetch API's 55.5 (C), and leads in 4 of 7 scored categories. DeepSeek Search and Fetch API leads on agent ergonomics. Both do web search. DeepSeek Search and Fetch API is cheaper for web search, $0.75 against $14 per 1,000 requests.", "tasks": null, "tutorials": [], "verdicts": { "bing-grounding": "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.", "deepseek-search-api": "Search returns up to 50 results with a model-length summary, an authority tier and optional full text, and only successful non-empty calls are billed, at $0.75 per 1,000. It opened on 17 October 2026, with 5 requests a second per account, no OpenAPI file, no free tier, and data held in the PRC under a policy that permits training." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api", "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.min.md" }, "markdown": "Grounding with Bing Search scores 63.7 (B) on agent readiness against DeepSeek Search and Fetch API's 55.5 (C), and leads in 4 of 7 scored categories. DeepSeek Search and Fetch API leads on agent ergonomics. Both do web search. DeepSeek Search and Fetch API is cheaper for web search, $0.75 against $14 per 1,000 requests.\n\n- 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\n- DeepSeek Search and Fetch API: grade C, 55.5/100, rank #861 of 1486. Markdown https://www.anchorterminal.com/tools/deepseek-search-api.md · JSON https://www.anchorterminal.com/api/v1/tools/deepseek-search-api.json\n- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md\n- All 308 search comparisons: https://www.anchorterminal.com/compare/search/index.md\n\n## Which one, for what\n\n### Grounding with Bing Search (B)\n\nGood for: Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.\n\nAhead on:\n- Schema \u0026 documentation, 68 against 55\n- Security \u0026 auth, 79 against 43\n- Maintenance \u0026 community, 80 against 42\n- Transparency \u0026 trust, 66 against 60\n\nWatch for: The Bing tools never return raw results to developers, only a model-written answer with citation links\n\n### DeepSeek Search and Fetch API (C)\n\nGood for: Cheap per-request web search with model-ready summaries and an authority signal, plus page fetching, for agents already on a DeepSeek key and comfortable with data held in the PRC.\n\nAhead on:\n- Agent ergonomics, 81 against 61\n\nAlso in its favour:\n- Cheaper for web search, $0.75 against $14 per 1,000 requests\n\nWatch for: Opened on 17 October 2026, with no service record of its own and no component for it on the status page\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Grounding with Bing Search +38\n\n- 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\u0026A 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.\n- DeepSeek Search and Fetch API (42): Closed service, per the 17 October check, not re-read on 4 November (terms pause). Opened on 17 October 2026, 18 days before this check (30). The change log's 17 October entry is the only dated one about Search or Fetch in the 90 days from 6 August (0 of 20). Dated change log, api-service@deepseek.com and a Discord server, not tested for replies (12 of 15). No official SDK (0 of 15). No SDK or package to assess (0 of 10). 30 + 0 + 12 + 0 + 0 = 42.\n\n### Security \u0026 auth: Grounding with Bing Search +36\n\n- 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.\n- DeepSeek Search and Fetch API (43): Per the 17 October check, not re-read on 4 November (terms pause). The ordinary DeepSeek bearer key, revocable, with no scopes, so a key used for search can also spend on models. No secret in a URL (20 of 30). Both endpoints only read, so there's nothing destructive to approve, but no search-only key (15 of 20). Results and fetched pages are untrusted web text. The change log says the engine filters 'SEO spam, GEO manipulation, and low-quality AIGC', with no technical detail and no prompt-injection guidance (3 of 15). No per-call log or audit log found in the docs. The platform console wasn't readable (0 of 15). Security programme 5 of 20 (was 0). The www.deepseek.com footer carries a Report Security Issue address, security@deepseek.com, per the 21 October reading used for DeepSeek's open-weight listings; no security.txt (404 on 17 October), disclosure policy, bug bounty or certification found. 20 + 15 + 3 + 0 + 5 = 43.\n\n### Agent ergonomics: DeepSeek Search and Fetch API +20\n\n- 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.\n- DeepSeek Search and Fetch API (81): Per the 17 October check, not re-read on 4 November (terms pause). Responses can be sized with `count` and `need_content`, off by default, and each result carries both a short snippet and a 600 to 800 character summary. No field selection, and full content has no length cap stated (20 of 25). Site, language, date and phrase filters, up to 50 results, no pagination (15 of 20). Ten documented codes with what to do, 402 for an empty balance and 404 for an unfetchable page. `param` is always null and `code` repeats the type (17 of 20). Both endpoints are documented as read-only and safe to retry, and failed or empty calls aren't billed (20). Only `query` or `url` is required. No official SDKs, the docs use raw HTTP and Python requests (9 of 15). 20 + 15 + 17 + 20 + 9 = 81.\n\n### Schema \u0026 documentation: Grounding with Bing Search +13\n\n- 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.\n- DeepSeek Search and Fetch API (55): Per the 17 October check, not re-read on 4 November (terms pause). No OpenAPI file found. The API reference is rendered from a schema, but no spec is linked, and /openapi.json and /openapi.yaml on the docs host serve the docs page (0). No llms.txt, since api-docs.deepseek.com answered /llms.txt with HTML (0). The guide says what each endpoint is for and which result field suits a UI or a model, and gives the score thresholds for quality and authority, but not when to use Search content against a Fetch (14 of 20). Types, required fields, defaults and limits on every field, such as `query` 1 to 128 characters and `count` 1 to 50. Filters live inside the free-text query (13 of 15). curl and Python examples, an error body and a table of ten status codes with retry guidance. The reference shows only the 200 response (13 of 15). Dated change log and a /v1 path (15). 0 + 0 + 14 + 13 + 13 + 15 = 55.\n\n### Transparency \u0026 trust: Grounding with Bing Search +6\n\n- 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.\n- DeepSeek Search and Fetch API (60): Per the 17 October check for the privacy policy, not re-read on 4 November (terms pause). Closed service with published terms under PRC law, which assign Outputs to the customer; the Open Platform terms (released 22 April, effective 29 April 2026) and the Terms of Use (last update 27 March 2026) were re-read on 4 November (15). The privacy policy of 10 February 2026 says personal data trains models unless you opt out by email and gives no retention period. It also says search runs on 'third-party APIs' that receive input keywords, which disagrees with the in-house engine described on 17 October, and nothing covers fetched URLs (5 of 30). No deprecation policy, and the only dated notice is the end of free server-side calls on 31 October (5 of 20). Data location disclosed as the PRC, third parties named only by category (10 of 20). 15 + 5 + 5 + 10 = 35.\n\n## Score by category\n\n| Category | Weight | Grounding with Bing Search | DeepSeek Search and Fetch API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 68 | 72 | DeepSeek Search and Fetch API +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 55 | Grounding with Bing Search +13 |\n| Agent ergonomics | 13% (16.2 this run) | 61 | 81 | DeepSeek Search and Fetch API +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 43 | Grounding with Bing Search +36 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 42 | Grounding with Bing Search +38 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 60 | Grounding with Bing Search +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.7 · B** | **55.5 · C** | |\n\n## Facts side by side\n\n| Fact | Grounding with Bing Search | DeepSeek Search and Fetch API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft | DeepSeek |\n| Hosted endpoint | `https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses` | `https://api.deepseek.com/v1/tools/search` |\n| Transports | Streamable HTTP | HTTP |\n| Auth | OAuth | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for web search | $14 per 1,000 requests | $0.75 per 1,000 requests |\n| x402 | no | no |\n| 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 |\n| Tools exposed | 3 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | no | no |\n| Last release | 2026-11-02 | 2026-10-17 |\n| Terms last updated | 2025-11-01 | couldn't be read |\n| Privacy policy last updated | 2026-09-01 | couldn't be read |\n| Customer content may train models | yes | couldn't be read |\n| Terms restrict automated access | yes | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### Grounding with Bing Search\n\nNo score change since it was listed.\n\n### DeepSeek Search and Fetch API\n\n- +2.3 on 4 November 2026 (D to C): correction\n\n## Verdicts\n\n**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.\n\n**DeepSeek Search and Fetch API.** Search returns up to 50 results with a model-length summary, an authority tier and optional full text, and only successful non-empty calls are billed, at $0.75 per 1,000. It opened on 17 October 2026, with 5 requests a second per account, no OpenAPI file, no free tier, and data held in the PRC under a policy that permits training.\n\n## Before you call either\n\n### Grounding with Bing Search\n\n1. 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\n2. 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\n3. Treat cited page text as untrusted input and don't put secrets or personal data in prompts, since queries leave the Azure compliance boundary\n4. On 429 back off exponentially; no Retry-After header is documented for the tool\n\n### DeepSeek Search and Fetch API\n\n1. Keep `query` to 128 characters and put filters in it as operators, such as `site:github.com lang:en after:2026-01-01`\n2. Leave `need_content` false and read `summary` first, then call Fetch on the URLs you keep\n3. Stay under 5 requests a second per account across all keys. On 408, 429 or 5xx wait and retry, since no Retry-After is documented\n4. Don't retry a Fetch 403 or 404 unchanged. The page is blocked by policy, unreachable or has no Markdown\n5. Don't send private queries or an end user's IP in `localization`. Data is stored in the PRC\n\n## Questions\n\n### Which is better for AI agents, Grounding with Bing Search or DeepSeek Search and Fetch API?\n\nGrounding with Bing Search scores 63.7 (B) on agent readiness against DeepSeek Search and Fetch API's 55.5 (C), and leads in 4 of 7 scored categories. DeepSeek Search and Fetch API leads on agent ergonomics.\n\n### Which is cheaper for web search, Grounding with Bing Search or DeepSeek Search and Fetch API?\n\nDeepSeek Search and Fetch API, at $0.75 per 1,000 requests against $14 per 1,000 requests for Grounding with Bing Search. These are the vendors' published prices for the job.\n\n### Do Grounding with Bing Search and DeepSeek Search and Fetch API need an API key?\n\nGrounding with Bing Search uses an OAuth sign-in. DeepSeek Search and Fetch API needs an API key.\n\n### Can an agent call Grounding with Bing Search and DeepSeek Search and Fetch API without installing anything?\n\nYes. Grounding with Bing Search has a hosted endpoint at https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses and DeepSeek Search and Fetch API at https://api.deepseek.com/v1/tools/search.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bing-grounding\", \"b\": \"deepseek-search-api\"}`. From a terminal: `anchor compare bing-grounding deepseek-search-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bing-grounding.json and https://www.anchorterminal.com/api/v1/tools/deepseek-search-api.json\n\n## Other comparisons with Grounding with Bing Search or DeepSeek Search and Fetch API\n\n- [Web Search Tool on Amazon Bedrock AgentCore vs Grounding with Bing Search](https://www.anchorterminal.com/compare/agentcore-web-search-vs-bing-grounding.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api.md)\n- [Arcmira vs Grounding with Bing Search](https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding.md)\n- [Arcmira vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/arcmira-vs-deepseek-search-api.md)\n- [Grounding with Bing Search vs Brave Search API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-brave-search-mcp.md)\n- [Grounding with Bing Search vs Cloudflare Web Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search.md)\n- [Grounding with Bing Search vs Exa API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-exa-mcp.md)\n- [Grounding with Bing Search vs Firecrawl MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-firecrawl-mcp.md)\n- [Grounding with Bing Search vs Kagi Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.md)\n- [Grounding with Bing Search vs Linkup](https://www.anchorterminal.com/compare/bing-grounding-vs-linkup.md)\n- [Grounding with Bing Search vs Mojeek Web Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek.md)\n- [Grounding with Bing Search vs NewsCatcher](https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.md)\n- [Grounding with Bing Search vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.md)\n- [Grounding with Bing Search vs Perplexity Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.md)\n- [Grounding with Bing Search vs SearchAPI.io](https://www.anchorterminal.com/compare/bing-grounding-vs-searchapi-io.md)\n- [Grounding with Bing Search vs SerpApi](https://www.anchorterminal.com/compare/bing-grounding-vs-serpapi.md)\n- [Grounding with Bing Search vs Serper](https://www.anchorterminal.com/compare/bing-grounding-vs-serper.md)\n- [Grounding with Bing Search vs SERPHouse](https://www.anchorterminal.com/compare/bing-grounding-vs-serphouse.md)\n- [Grounding with Bing Search vs SerpKite](https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.md)\n- [Grounding with Bing Search vs SpecStream](https://www.anchorterminal.com/compare/bing-grounding-vs-specstream.md)\n- [Grounding with Bing Search vs Tavily API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-tavily-mcp.md)\n- [Grounding with Bing Search vs TinyFish Search](https://www.anchorterminal.com/compare/bing-grounding-vs-tinyfish-search.md)\n- [Grounding with Bing Search vs Valyu](https://www.anchorterminal.com/compare/bing-grounding-vs-valyu.md)\n- [Grounding with Bing Search vs You.com APIs](https://www.anchorterminal.com/compare/bing-grounding-vs-you-com-api.md)\n- [Brave Search API + MCP vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/brave-search-mcp-vs-deepseek-search-api.md)\n- [Cloudflare Web Search API vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-deepseek-search-api.md)\n- [DeepSeek Search and Fetch API vs Exa API + MCP](https://www.anchorterminal.com/compare/deepseek-search-api-vs-exa-mcp.md)\n- [DeepSeek Search and Fetch API vs Firecrawl MCP](https://www.anchorterminal.com/compare/deepseek-search-api-vs-firecrawl-mcp.md)\n- [DeepSeek Search and Fetch API vs Grep AI](https://www.anchorterminal.com/compare/deepseek-search-api-vs-grep-ai.md)\n- [DeepSeek Search and Fetch API vs Kagi Search API](https://www.anchorterminal.com/compare/deepseek-search-api-vs-kagi-search.md)\n- [DeepSeek Search and Fetch API vs Linkup](https://www.anchorterminal.com/compare/deepseek-search-api-vs-linkup.md)\n- [DeepSeek Search and Fetch API vs Mojeek Web Search API](https://www.anchorterminal.com/compare/deepseek-search-api-vs-mojeek.md)\n- [DeepSeek Search and Fetch API vs NewsCatcher](https://www.anchorterminal.com/compare/deepseek-search-api-vs-newscatcher.md)\n- [DeepSeek Search and Fetch API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/deepseek-search-api-vs-parallel-search-api.md)\n- [DeepSeek Search and Fetch API vs Perplexity Search API](https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api.md)\n- [DeepSeek Search and Fetch API vs SearchAPI.io](https://www.anchorterminal.com/compare/deepseek-search-api-vs-searchapi-io.md)\n- [DeepSeek Search and Fetch API vs SerpApi](https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpapi.md)\n- [DeepSeek Search and Fetch API vs Serper](https://www.anchorterminal.com/compare/deepseek-search-api-vs-serper.md)\n- [DeepSeek Search and Fetch API vs SERPHouse](https://www.anchorterminal.com/compare/deepseek-search-api-vs-serphouse.md)\n- [DeepSeek Search and Fetch API vs SerpKite](https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpkite.md)\n- [DeepSeek Search and Fetch API vs SpecStream](https://www.anchorterminal.com/compare/deepseek-search-api-vs-specstream.md)\n- [DeepSeek Search and Fetch API vs Tavily API + MCP](https://www.anchorterminal.com/compare/deepseek-search-api-vs-tavily-mcp.md)\n- [DeepSeek Search and Fetch API vs TinyFish Search](https://www.anchorterminal.com/compare/deepseek-search-api-vs-tinyfish-search.md)\n- [DeepSeek Search and Fetch API vs Valyu](https://www.anchorterminal.com/compare/deepseek-search-api-vs-valyu.md)\n- [DeepSeek Search and Fetch API vs You.com APIs](https://www.anchorterminal.com/compare/deepseek-search-api-vs-you-com-api.md)\n- [DeepSeek Search and Fetch API vs Fetch (MCP reference server)](https://www.anchorterminal.com/compare/deepseek-search-api-vs-fetch-reference-server.md)\n- [Grounding with Bing Search vs Grep AI](https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Grounding with Bing Search vs DeepSeek Search and Fetch API", "url": "" } ], "description": "Grounding with Bing Search scores 63.7 (B) to DeepSeek Search and Fetch's 55.5 (C) for web search. DeepSeek Search and Fetch is cheaper for web search, $0.75 against $14 per 1,000 requests. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grounding with Bing Search B 63.7", "DeepSeek Search and Fetch API C 55.5", "scores" ], "h1": "Grounding with Bing Search vs DeepSeek Search and Fetch API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bing-grounding-vs-deepseek-search-api", "published": "2026-10-01", "section": "tools", "title": "Grounding with Bing Search vs DeepSeek Search and Fetch (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api" }, "tokens": { "markdown": 6250, "slim": 3380 }, "version": 1 }