{ "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": "NewsCatcher scores 67.5 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth.", "b": { "slug": "newscatcher", "name": "NewsCatcher", "vendor": "NewsCatcher, Inc.", "vendorUrl": "https://www.newscatcherapi.com", "kind": "http-api", "category": "search", "summary": "NewsCatcher's API searches the last 30 days of news in every language, grouped into stories, and runs a background agent that builds tables of events or company news, through REST and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/newscatcher", "markdownUrl": "https://www.anchorterminal.com/tools/newscatcher.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/newscatcher.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/newscatcher.json", "dns": "newscatcher.grade.anchorterminal.com", "repo": "https://github.com/Newscatcher/newscatcher-mcp", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.newscatcherapi.com/mcp", "packages": [], "auth": "api-key", "authNotes": "API key from the NewsCatcher platform after a browser signup, sent in the `x-api-key` header. One key works for the News API and the agent; several keys can be made and revoked in the platform. The MCP server also accepts `Authorization: Bearer` or `?apiKey=` in the URL; OAuth is announced as coming soon. No scopes found.", "pricing": "usage", "pricingNotes": "Prepaid credits at $1 per 1,000 (top-ups from $25, valid 12 months). Search costs 1, 5 or 10 credits by effort, a story 1, `/articles` 5 per call. Agent runs 1,000 to 6,000 credits. 10,000 free credits every 30 days. Failed and refused requests aren't charged.", "priceSummary": "$1 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, the docs, the pricing page or the OpenAPI specs (checked 2026-11-06). An empty balance returns 402 with no payment requirements; top-ups go through the platform.", "endpoints": [] }, "toolCount": 15, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://www.newscatcherapi.com/docs/get-started/overview", "llmsTxt": "https://www.newscatcherapi.com/docs/llms.txt", "openapi": "https://github.com/NewscatcherAPI/docs/blob/main/api-reference/news-api/openapi.json", "capabilities": [ "search.news", "search.research", "web.search" ], "tags": [ "hosted", "usage", "prepaid", "free-tier", "mcp", "remote-mcp", "openapi", "llms-txt", "status-page", "yc" ], "lastRelease": "2026-11-06", "graded": true, "anchor": { "graded": true, "score": 67.5, "grade": "B", "agentReady": false, "rank": 321, "ranked": true, "rankOf": 1486, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 84, "maintenance": 76, "payments": 30, "reliability": 67, "schema": 94, "security": 45, "transparency": 79 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "One key and one credit balance cover a ranked news search, a background research agent and a hosted MCP server with toolsets and annotated tools, under OpenAPI 3.1 specs and a dated changelog. The current API launched on 30 October 2026, the MCP server accepts the key in its URL, and no SLA is published below Enterprise.", "bestFor": "Agents that need current news across languages, grouped into stories, or tables of events and company news on a schedule.", "strengths": [ "OpenAPI 3.1 specs for the News API and the agent, llms.txt, Markdown pages and a docs MCP server", "Hosted MCP server with 15 tools in four toolsets, selectable with `?tools=`, and read-only, destructive and idempotent hints on every tool", "Documented errors with retry advice per status, 429 with Retry-After, and refused or failed requests never charged", "Published credit prices, $1 per 1,000 credits, and 10,000 free credits every 30 days", "Terms say inputs and generated data are never used to train models, with a dated sub-processor list" ], "weaknesses": [ "The current News API and agent launched on 30 October 2026 and the MCP repository went public on 6 November 2026", "The MCP server documents `?apiKey=` in the URL for clients without headers, and keys have no scopes found", "No SLA below a signed Enterprise agreement; the status page monitors one News API component", "API logs, which can include query text, are archived indefinitely after 90 days", "The pricing page and the docs disagree on whether empty agent runs are charged and on the price of `/articles`" ], "agentNotes": [ "Send the key in the `x-api-key` header, and use a separate key for the MCP server so it can be revoked alone", "Call `start_research` with `dry_run` first, since agent runs cost 1,000 to 6,000 credits", "Use `effort=low` for quick lookups; the default `medium` costs five times as much", "Use `/articles` or `list_articles` for news older than 30 days or exact counts; `/search` covers 30 days only", "On 429 or 503 wait for Retry-After, and quote the Correlation-ID header to support" ], "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": 67.5 } ], "editorialScores": { "ergonomics": 84, "maintenance": 76, "payments": 30, "reliability": 67, "schema": 94, "security": 45, "transparency": 73 }, "provenanceScore": 85, "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": { "http": "curl -X POST \"https://api.newscatcherapi.com/news-api/search\" \\\n -H \"x-api-key: $NEWSCATCHER_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"q\": \"hurricane recovery florida\", \"limit\": 5}'", "claudeCode": "claude mcp add --transport http newscatcher https://mcp.newscatcherapi.com/mcp --header \"x-api-key: YOUR_API_KEY\"", "config": { "mcpServers": { "newscatcher": { "headers": { "x-api-key": "YOUR_API_KEY" }, "url": "https://mcp.newscatcherapi.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/search.news", "tool": "https://letme.dev/newscatcher" }, "area": "web-data", "unitPrices": [ { "item": "News search, low effort", "unit": "1k-requests", "usd": 1, "note": "1 credit a search at $1 per 1,000 credits" }, { "item": "News search, medium effort (default)", "unit": "1k-requests", "usd": 5, "note": "5 credits" }, { "item": "News search, high effort", "unit": "1k-requests", "usd": 10, "note": "10 credits" }, { "item": "Articles listing", "unit": "1k-requests", "usd": 5, "note": "5 credits a call per the docs; the pricing page says 15 a page" }, { "item": "Agent event research, fast run", "unit": "tx", "usd": 1, "note": "1,000 credits, 50 rows included; standard $3, max $6" }, { "item": "Credit", "unit": "credit", "usd": 0.001, "note": "Top-ups from $25 for 25,000 credits, valid 12 months" } ], "provenance": { "legalEntity": "NewsCatcher, Inc.", "domain": "newscatcherapi.com", "domainRegistered": "2020-02-16", "endpointOnVendorDomain": true, "terms": "https://www.newscatcherapi.com/company/legal/terms-and-conditions", "privacy": "https://www.newscatcherapi.com/company/legal/privacy-policy", "statusPage": "https://status.newscatcherapi.com/", "changelog": "https://www.newscatcherapi.com/docs/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The service terms (Terms and Conditions) and the website Terms of Service are both dated 2 November 2026 and name NewsCatcher, Inc. under Delaware law.", "The website Terms of Service forbid using the site or its content 'to spam, phish, pharm, pretext, spider, crawl, or scrape'. Recorded as a fact; only public pages were read, within robots.txt.", "www.newscatcherapi.com/robots.txt disallows /~gitbook, /*?ref= and /api/ for all agents; none of the pages read is under those paths. status.newscatcherapi.com allows all.", "/.well-known/security.txt answers 404. The MCP repository's SECURITY.md takes private reports through GitHub with a 3-business-day acknowledgement target.", "Status page on Hyperping with one News API component, 99.820% uptime for August to November 2026 and one incident in the 90 days, on 1 September 2026.", "RDAP gives newscatcherapi.com a registration date of 16 February 2020." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/newscatcher.json", "live": { "slug": "newscatcher", "probe": { "target": "https://mcp.newscatcherapi.com/mcp", "method": "get", "lastAt": "2026-11-07T18:20:41.854849144Z", "lastOk": true, "lastStatus": 405, "lastMs": 305, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 167, "p95ms24h": 346, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.newscatcherapi.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:15.638845153Z" }, "githubStars": 0, "securityTxt": { "url": "https://newscatcherapi.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:58.85886795Z" }, "llmsTxt": { "url": "https://www.newscatcherapi.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:19.853404264Z" }, "pages": [ { "url": "https://www.newscatcherapi.com/docs/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:32:00.60078463Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "849b66383503" }, { "url": "https://www.newscatcherapi.com/company/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:31:56.385466242Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "818e0cf9f82d" }, { "url": "https://www.newscatcherapi.com/company/legal/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:31:58.548719689Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "79f84eff4353" } ], "mcpTools": { "url": "https://mcp.newscatcherapi.com/mcp", "checkedAt": "2026-11-07T01:46:25.078047109Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:25.078047109Z" }, "updatedAt": "2026-11-07T18:20:41.854849144Z" } }, "edges": [ { "by": 34, "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": "API keys in the `x-api-key` header, several per account, revocable in the platform, with advice to keep one per application. A 403 for 'a key that may not use this API' suggests per-key API access, but no scopes are documented (20). The MCP server documents `?apiKey=` on the server URL for Claude.ai custom connectors, with a warning, so less 10 (10 of 30). The MCP repository's SECURITY.md says URL keys are rejected unless the operator enables them, which the hosted server does per the docs. Toolsets let an operator load only the read-only `news` tools, write tools carry destructiveHint, and the server tells the assistant to confirm large or hourly agent jobs (14 of 20). Results are third-party article text and summaries, and no prompt-injection guidance was found in the docs or the MCP server's instructions (0 of 15). Every response carries a Correlation-ID, `GET /subscription` shows usage and balance, and runs are listed in the platform. No per-call audit log for the customer was found (7 of 15). The security page and footer claim SOC 2 Type II and link a trust centre on Oneleet, which wasn't read. A vulnerability disclosure policy covers the MCP server. No security.txt (404) and no bug bounty found (14 of 20). 10 + 14 + 0 + 7 + 14 = 45." }, "scores": { "a": 79, "b": 45 } }, { "by": 26, "category": "schema", "leads": "newscatcher", "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": "OpenAPI 3.1 for the News API (version 1.3.9, 4 paths) and the agent (version 1.5.1, 33 paths), linked from llms.txt, and typed JSON Schema on every MCP tool through Pydantic (25). llms.txt, a Markdown copy of every page and a docs MCP server (10). MCP tool descriptions say when to use each and which tool to use instead, such as `list_articles` for older news; the REST reference explains each endpoint and the 'Choose an API' page compares them (17 of 20). Inputs are typed with enums for effort, mode and dimensions, length and range limits such as a 500-character query and limit 1 to 100, and required fields marked (13 of 15). Runnable examples in curl, Python and JavaScript, and an error table with retry advice for every status. The agent spec carries no response examples (14 of 15). Versioned APIs with a dated changelog, the latest entries on 4 November 2026, and separate changelogs for the v3 News API and CatchAll (15). 25 + 10 + 17 + 13 + 14 + 15 = 94." }, "scores": { "a": 68, "b": 94 } }, { "by": 23, "category": "ergonomics", "leads": "newscatcher", "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": "15 MCP tools in four toolsets, chosen per connection with `?tools=`, and tools return compact text rather than the full JSON. 15 for 11 to 30 tools plus 7 for toolsets (22 of 25). `limit`, `search_window`, effort, language, country, publisher, coverage and content-type filters, sorting, and paging on `/articles`; agent tables come back up to 200 rows at a time over MCP (20). Every status is documented with whether to retry; the agent returns stable `code` values, while the News API body has a `status_code` and a message meant for people (17 of 20). Every tool carries readOnlyHint and idempotentHint, writes carry destructiveHint, `start_research` has a free `dry_run`, and refused or failed calls aren't charged. No idempotency key for starting runs (17 of 20). Only `q` is required, with medium effort and a 7-day window as defaults. No official SDK for the current API was found; the docs show raw HTTP in three languages (8 of 15). 22 + 20 + 17 + 17 + 8 = 84." }, "scores": { "a": 61, "b": 84 } }, { "by": 13, "category": "transparency", "leads": "newscatcher", "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": "The API is closed under terms of 2 November 2026 naming NewsCatcher, Inc., and the MCP server is MIT, so between the two bands (20 of 30). The terms say inputs and generated data are not used to train models, a DPA applies automatically, and the privacy policy gives retention periods (server logs 7 days, API logs with query text 90 days, then archived indefinitely, billing records about seven years). They agree with each other, but indefinite archives of query logs hold it back (22 of 30). The terms promise 30 days' email notice before a paid product or API version is discontinued, with refunds of unused credits, and the v3 News API has a migration guide (15 of 20). A sub-processor list dated 2 November 2026 with each provider's location and the data it handles. The MCP repository deploys to Vercel and can send pseudonymised analytics to PostHog, and neither appears on the list (16 of 20). 20 + 22 + 15 + 16 = 73." }, "scores": { "a": 66, "b": 79 } }, { "by": 10, "category": "payments", "leads": "newscatcher", "name": "Payments \u0026 pricing", "reasons": { "a": "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).", "b": "No x402, MPP or L402 (0). Credit prices per call published without login, and credits cost $1 per 1,000 through top-ups from $25 (20). 10,000 free credits every 30 days on a $0 plan, and the first top-up moves an account to pay as you go. No page says whether a card is needed to open the free plan, so half (10). A person signs up in the platform in a browser to get a key (0). NewsMCP's keyless tier belongs to a separate product and isn't counted. 0 + 20 + 10 + 0 = 30." }, "scores": { "a": 20, "b": 30 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Microsoft", "b": "NewsCatcher, Inc.", "name": "Vendor" }, { "a": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "b": "https://mcp.newscatcherapi.com/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable 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": "$1 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": "15", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-11-02", "b": "2026-11-06", "name": "Last release" }, { "a": "2025-11-01", "b": "2026-11-02", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "2026-11-02", "name": "Privacy policy last updated" }, { "a": "yes", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "NewsCatcher scores 67.5 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth.", "question": "Which is better for AI agents, Grounding with Bing Search or NewsCatcher?" }, { "answer": "NewsCatcher, at $1 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 NewsCatcher?" }, { "answer": "Grounding with Bing Search uses an OAuth sign-in. NewsCatcher needs an API key.", "question": "Do Grounding with Bing Search and NewsCatcher 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 NewsCatcher at https://mcp.newscatcherapi.com/mcp.", "question": "Can an agent call Grounding with Bing Search and NewsCatcher without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 79 against 45" ], "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": [ "Schema \u0026 documentation, 94 against 68", "Agent ergonomics, 84 against 61", "Payments \u0026 pricing, 30 against 20", "Transparency \u0026 trust, 79 against 66" ], "also": [ "Cheaper for web search, $1 against $14 per 1,000 requests" ], "goodFor": "Agents that need current news across languages, grouped into stories, or tables of events and company news on a schedule.", "slug": "newscatcher", "watchFor": "The current News API and agent launched on 30 October 2026 and the MCP repository went public on 6 November 2026" } ], "history": null, "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-newscatcher.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-newscatcher" }, { "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/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-deepseek-search-api.json", "title": "Grounding with Bing Search vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api" }, { "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-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-newscatcher.json", "title": "Brave Search API + MCP vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-newscatcher.json", "title": "Cloudflare Web Search API vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-newscatcher" }, { "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/exa-mcp-vs-newscatcher.json", "title": "Exa API + MCP vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-newscatcher.json", "title": "Kagi Search API vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-newscatcher.json", "title": "Linkup vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/linkup-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-newscatcher.json", "title": "Mojeek Web Search API vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/mojeek-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-parallel-search-api.json", "title": "NewsCatcher vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.json", "title": "NewsCatcher vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-tinyfish-search.json", "title": "NewsCatcher vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-newscatcher.json", "title": "Arcmira vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/arcmira-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-newscatcher.json", "title": "Grep AI vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-specstream.json", "title": "NewsCatcher vs SpecStream", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-searchapi-io.json", "title": "NewsCatcher vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-serpapi.json", "title": "NewsCatcher vs SerpApi", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-serper.json", "title": "NewsCatcher vs Serper", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-serphouse.json", "title": "NewsCatcher vs SERPHouse", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-serpkite.json", "title": "NewsCatcher vs SerpKite", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-tavily-mcp.json", "title": "NewsCatcher vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-valyu.json", "title": "NewsCatcher vs Valyu", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-you-com-api.json", "title": "NewsCatcher vs You.com APIs", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-you-com-api" }, { "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": 1, "edge": "bing-grounding", "key": "reliability", "name": "Reliability", "newscatcher": 67, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bing-grounding": 68, "by": 26, "edge": "newscatcher", "key": "schema", "name": "Schema \u0026 documentation", "newscatcher": 94, "weight": 13 }, { "bing-grounding": 61, "by": 23, "edge": "newscatcher", "key": "ergonomics", "name": "Agent ergonomics", "newscatcher": 84, "weight": 13 }, { "bing-grounding": 79, "by": 34, "edge": "bing-grounding", "key": "security", "name": "Security \u0026 auth", "newscatcher": 45, "weight": 14 }, { "bing-grounding": 20, "by": 10, "edge": "newscatcher", "key": "payments", "name": "Payments \u0026 pricing", "newscatcher": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bing-grounding": 80, "by": 4, "edge": "bing-grounding", "key": "maintenance", "name": "Maintenance \u0026 community", "newscatcher": 76, "weight": 7 }, { "bing-grounding": 66, "by": 13, "edge": "newscatcher", "key": "transparency", "name": "Transparency \u0026 trust", "newscatcher": 79, "weight": 7 } ], "summary": "NewsCatcher scores 67.5 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth. Both do web search. NewsCatcher is cheaper for web search, $1 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.", "newscatcher": "One key and one credit balance cover a ranked news search, a background research agent and a hosted MCP server with toolsets and annotated tools, under OpenAPI 3.1 specs and a dated changelog. The current API launched on 30 October 2026, the MCP server accepts the key in its URL, and no SLA is published below Enterprise." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher", "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.min.md" }, "markdown": "NewsCatcher scores 67.5 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth. Both do web search. NewsCatcher is cheaper for web search, $1 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- NewsCatcher: grade B, 67.5/100, rank #321 of 1486. Markdown https://www.anchorterminal.com/tools/newscatcher.md · JSON https://www.anchorterminal.com/api/v1/tools/newscatcher.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- Security \u0026 auth, 79 against 45\n\nWatch for: The Bing tools never return raw results to developers, only a model-written answer with citation links\n\n### NewsCatcher (B)\n\nGood for: Agents that need current news across languages, grouped into stories, or tables of events and company news on a schedule.\n\nAhead on:\n- Schema \u0026 documentation, 94 against 68\n- Agent ergonomics, 84 against 61\n- Payments \u0026 pricing, 30 against 20\n- Transparency \u0026 trust, 79 against 66\n\nAlso in its favour:\n- Cheaper for web search, $1 against $14 per 1,000 requests\n\nWatch for: The current News API and agent launched on 30 October 2026 and the MCP repository went public on 6 November 2026\n\n\n## Why the edge\n\n### Security \u0026 auth: Grounding with Bing Search +34\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- NewsCatcher (45): API keys in the `x-api-key` header, several per account, revocable in the platform, with advice to keep one per application. A 403 for 'a key that may not use this API' suggests per-key API access, but no scopes are documented (20). The MCP server documents `?apiKey=` on the server URL for Claude.ai custom connectors, with a warning, so less 10 (10 of 30). The MCP repository's SECURITY.md says URL keys are rejected unless the operator enables them, which the hosted server does per the docs. Toolsets let an operator load only the read-only `news` tools, write tools carry destructiveHint, and the server tells the assistant to confirm large or hourly agent jobs (14 of 20). Results are third-party article text and summaries, and no prompt-injection guidance was found in the docs or the MCP server's instructions (0 of 15). Every response carries a Correlation-ID, `GET /subscription` shows usage and balance, and runs are listed in the platform. No per-call audit log for the customer was found (7 of 15). The security page and footer claim SOC 2 Type II and link a trust centre on Oneleet, which wasn't read. A vulnerability disclosure policy covers the MCP server. No security.txt (404) and no bug bounty found (14 of 20). 10 + 14 + 0 + 7 + 14 = 45.\n\n### Schema \u0026 documentation: NewsCatcher +26\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- NewsCatcher (94): OpenAPI 3.1 for the News API (version 1.3.9, 4 paths) and the agent (version 1.5.1, 33 paths), linked from llms.txt, and typed JSON Schema on every MCP tool through Pydantic (25). llms.txt, a Markdown copy of every page and a docs MCP server (10). MCP tool descriptions say when to use each and which tool to use instead, such as `list_articles` for older news; the REST reference explains each endpoint and the 'Choose an API' page compares them (17 of 20). Inputs are typed with enums for effort, mode and dimensions, length and range limits such as a 500-character query and limit 1 to 100, and required fields marked (13 of 15). Runnable examples in curl, Python and JavaScript, and an error table with retry advice for every status. The agent spec carries no response examples (14 of 15). Versioned APIs with a dated changelog, the latest entries on 4 November 2026, and separate changelogs for the v3 News API and CatchAll (15). 25 + 10 + 17 + 13 + 14 + 15 = 94.\n\n### Agent ergonomics: NewsCatcher +23\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- NewsCatcher (84): 15 MCP tools in four toolsets, chosen per connection with `?tools=`, and tools return compact text rather than the full JSON. 15 for 11 to 30 tools plus 7 for toolsets (22 of 25). `limit`, `search_window`, effort, language, country, publisher, coverage and content-type filters, sorting, and paging on `/articles`; agent tables come back up to 200 rows at a time over MCP (20). Every status is documented with whether to retry; the agent returns stable `code` values, while the News API body has a `status_code` and a message meant for people (17 of 20). Every tool carries readOnlyHint and idempotentHint, writes carry destructiveHint, `start_research` has a free `dry_run`, and refused or failed calls aren't charged. No idempotency key for starting runs (17 of 20). Only `q` is required, with medium effort and a 7-day window as defaults. No official SDK for the current API was found; the docs show raw HTTP in three languages (8 of 15). 22 + 20 + 17 + 17 + 8 = 84.\n\n### Transparency \u0026 trust: NewsCatcher +13\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- NewsCatcher (79): The API is closed under terms of 2 November 2026 naming NewsCatcher, Inc., and the MCP server is MIT, so between the two bands (20 of 30). The terms say inputs and generated data are not used to train models, a DPA applies automatically, and the privacy policy gives retention periods (server logs 7 days, API logs with query text 90 days, then archived indefinitely, billing records about seven years). They agree with each other, but indefinite archives of query logs hold it back (22 of 30). The terms promise 30 days' email notice before a paid product or API version is discontinued, with refunds of unused credits, and the v3 News API has a migration guide (15 of 20). A sub-processor list dated 2 November 2026 with each provider's location and the data it handles. The MCP repository deploys to Vercel and can send pseudonymised analytics to PostHog, and neither appears on the list (16 of 20). 20 + 22 + 15 + 16 = 73.\n\n### Payments \u0026 pricing: NewsCatcher +10\n\n- 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).\n- NewsCatcher (30): No x402, MPP or L402 (0). Credit prices per call published without login, and credits cost $1 per 1,000 through top-ups from $25 (20). 10,000 free credits every 30 days on a $0 plan, and the first top-up moves an account to pay as you go. No page says whether a card is needed to open the free plan, so half (10). A person signs up in the platform in a browser to get a key (0). NewsMCP's keyless tier belongs to a separate product and isn't counted. 0 + 20 + 10 + 0 = 30.\n\n## Score by category\n\n| Category | Weight | Grounding with Bing Search | NewsCatcher | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 68 | 67 | Grounding with Bing Search +1 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 94 | NewsCatcher +26 |\n| Agent ergonomics | 13% (16.2 this run) | 61 | 84 | NewsCatcher +23 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 45 | Grounding with Bing Search +34 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 30 | NewsCatcher +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 76 | Grounding with Bing Search +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 79 | NewsCatcher +13 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.7 · B** | **67.5 · B** | |\n\n## Facts side by side\n\n| Fact | Grounding with Bing Search | NewsCatcher |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft | NewsCatcher, Inc. |\n| Hosted endpoint | `https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses` | `https://mcp.newscatcherapi.com/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for web search | $14 per 1,000 requests | $1 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 | 15 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| Last release | 2026-11-02 | 2026-11-06 |\n| Terms last updated | 2025-11-01 | 2026-11-02 |\n| Privacy policy last updated | 2026-09-01 | 2026-11-02 |\n| Customer content may train models | yes | yes |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\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**NewsCatcher.** One key and one credit balance cover a ranked news search, a background research agent and a hosted MCP server with toolsets and annotated tools, under OpenAPI 3.1 specs and a dated changelog. The current API launched on 30 October 2026, the MCP server accepts the key in its URL, and no SLA is published below Enterprise.\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### NewsCatcher\n\n1. Send the key in the `x-api-key` header, and use a separate key for the MCP server so it can be revoked alone\n2. Call `start_research` with `dry_run` first, since agent runs cost 1,000 to 6,000 credits\n3. Use `effort=low` for quick lookups; the default `medium` costs five times as much\n4. Use `/articles` or `list_articles` for news older than 30 days or exact counts; `/search` covers 30 days only\n5. On 429 or 503 wait for Retry-After, and quote the Correlation-ID header to support\n\n## Questions\n\n### Which is better for AI agents, Grounding with Bing Search or NewsCatcher?\n\nNewsCatcher scores 67.5 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth.\n\n### Which is cheaper for web search, Grounding with Bing Search or NewsCatcher?\n\nNewsCatcher, at $1 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 NewsCatcher need an API key?\n\nGrounding with Bing Search uses an OAuth sign-in. NewsCatcher needs an API key.\n\n### Can an agent call Grounding with Bing Search and NewsCatcher 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 NewsCatcher at https://mcp.newscatcherapi.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bing-grounding\", \"b\": \"newscatcher\"}`. From a terminal: `anchor compare bing-grounding newscatcher`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bing-grounding.json and https://www.anchorterminal.com/api/v1/tools/newscatcher.json\n\n## Other comparisons with Grounding with Bing Search or NewsCatcher\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 NewsCatcher](https://www.anchorterminal.com/compare/agentcore-web-search-vs-newscatcher.md)\n- [Arcmira vs Grounding with Bing Search](https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding.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 DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.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 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 NewsCatcher](https://www.anchorterminal.com/compare/brave-search-mcp-vs-newscatcher.md)\n- [Cloudflare Web Search API vs NewsCatcher](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-newscatcher.md)\n- [DeepSeek Search and Fetch API vs NewsCatcher](https://www.anchorterminal.com/compare/deepseek-search-api-vs-newscatcher.md)\n- [Exa API + MCP vs NewsCatcher](https://www.anchorterminal.com/compare/exa-mcp-vs-newscatcher.md)\n- [Kagi Search API vs NewsCatcher](https://www.anchorterminal.com/compare/kagi-search-vs-newscatcher.md)\n- [Linkup vs NewsCatcher](https://www.anchorterminal.com/compare/linkup-vs-newscatcher.md)\n- [Mojeek Web Search API vs NewsCatcher](https://www.anchorterminal.com/compare/mojeek-vs-newscatcher.md)\n- [NewsCatcher vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/newscatcher-vs-parallel-search-api.md)\n- [NewsCatcher vs Perplexity Search API](https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.md)\n- [NewsCatcher vs TinyFish Search](https://www.anchorterminal.com/compare/newscatcher-vs-tinyfish-search.md)\n- [Arcmira vs NewsCatcher](https://www.anchorterminal.com/compare/arcmira-vs-newscatcher.md)\n- [Grep AI vs NewsCatcher](https://www.anchorterminal.com/compare/grep-ai-vs-newscatcher.md)\n- [NewsCatcher vs SpecStream](https://www.anchorterminal.com/compare/newscatcher-vs-specstream.md)\n- [NewsCatcher vs SearchAPI.io](https://www.anchorterminal.com/compare/newscatcher-vs-searchapi-io.md)\n- [NewsCatcher vs SerpApi](https://www.anchorterminal.com/compare/newscatcher-vs-serpapi.md)\n- [NewsCatcher vs Serper](https://www.anchorterminal.com/compare/newscatcher-vs-serper.md)\n- [NewsCatcher vs SERPHouse](https://www.anchorterminal.com/compare/newscatcher-vs-serphouse.md)\n- [NewsCatcher vs SerpKite](https://www.anchorterminal.com/compare/newscatcher-vs-serpkite.md)\n- [NewsCatcher vs Tavily API + MCP](https://www.anchorterminal.com/compare/newscatcher-vs-tavily-mcp.md)\n- [NewsCatcher vs Valyu](https://www.anchorterminal.com/compare/newscatcher-vs-valyu.md)\n- [NewsCatcher vs You.com APIs](https://www.anchorterminal.com/compare/newscatcher-vs-you-com-api.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 NewsCatcher", "url": "" } ], "description": "NewsCatcher scores 67.5 (B) to Grounding with Bing Search's 63.7 (B) for web search. NewsCatcher is cheaper for web search, $1 against $14 per 1,000 requests. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grounding with Bing Search B 63.7", "NewsCatcher B 67.5", "scores" ], "h1": "Grounding with Bing Search vs NewsCatcher", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bing-grounding-vs-newscatcher", "published": "2026-10-01", "section": "tools", "title": "Grounding with Bing Search vs NewsCatcher for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher" }, "tokens": { "markdown": 5850, "slim": 3280 }, "version": 1 }