{ "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": "Perplexity Search API scores 70.2 (BB) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth.", "b": { "slug": "perplexity-search-api", "name": "Perplexity Search API", "vendor": "Perplexity", "vendorUrl": "https://www.perplexity.ai/", "kind": "http-api", "category": "search", "summary": "Perplexity's Search API returns ranked web results with extracted page text as JSON from Perplexity's own index, through `POST /search`. The same key reaches the Agent API's web_search tool for cited answers, and a hosted MCP server wraps both.", "url": "https://www.anchorterminal.com/tools/perplexity-search-api", "markdownUrl": "https://www.anchorterminal.com/tools/perplexity-search-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/perplexity-search-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/perplexity-search-api.json", "dns": "perplexity-search-api.grade.anchorterminal.com", "repo": "https://github.com/perplexityai/modelcontextprotocol", "license": "Proprietary service under the Perplexity API Terms of Service. The MCP server is MIT and the official SDKs Apache-2.0", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://api.perplexity.ai/mcp", "packages": [ { "registry": "pypi", "name": "perplexityai" }, { "registry": "npm", "name": "@perplexity-ai/perplexity_ai" }, { "registry": "npm", "name": "@perplexity-ai/mcp-server" } ], "auth": "mixed", "authNotes": "Bearer Perplexity API key in the `Authorization` header. Keys belong to a project in the API console, are shown once, and can be generated and revoked through `/generate_auth_token` and `/revoke_auth_token`, with a rotation guide. No per-key scopes found. The hosted MCP server also accepts Sign in with Perplexity (OAuth), where the user picks the organisation to bill.", "pricing": "usage", "pricingNotes": "$5 per 1,000 successful Search API requests, or $1 with Fast Search, with up to five queries per request billed once. Invalid, rate-limited and failed requests are not billed. Agent API web_search is $2.50 per 1,000 calls plus model tokens. Prepaid credits with a card. No free allowance found.", "priceSummary": "$5 / 1k req", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Search API docs, the pricing page, the OpenAPI description or llms.txt (checked 2026-11-06). An empty balance returns 402 Payment Required with no payment requirements, per the FAQ.", "endpoints": [] }, "toolCount": 4, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.perplexity.ai/docs/search/overview", "llmsTxt": "https://docs.perplexity.ai/llms.txt", "openapi": "https://docs.perplexity.ai/openapi.json", "registryName": "ai.perplexity/mcp-server", "capabilities": [ "web.search", "search.answer", "search.research" ], "tags": [ "hosted", "usage-priced", "prepaid", "card-required", "closed-source", "openapi", "llms-txt", "mcp", "remote-mcp", "mcp-registry", "python", "typescript", "status-page", "soc2" ], "lastRelease": "2026-10-23", "graded": true, "anchor": { "graded": true, "score": 70.2, "grade": "BB", "agentReady": true, "rank": 210, "ranked": true, "rankOf": 1486, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 85, "maintenance": 82, "payments": 25, "reliability": 80, "schema": 89, "security": 56, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Raw ranked results with token-capped page text from Perplexity's own index, $5 per 1,000 requests or $1 with Fast Search, an OpenAPI description and a hosted MCP server with read-only annotations. Uptime is not guaranteed, there is no free allowance, keys carry no scopes, and no guidance on untrusted page text was found.", "bestFor": "Agents on any model that need raw ranked sources with extracted text at a low per-request price, and teams that want cited answers from the same key through the Agent API.", "strengths": [ "OpenAPI 3.1 description of `POST /search` with enums and limits, llms.txt and a Markdown twin of every docs page", "`max_tokens`, `max_tokens_per_page` and `max_results` cap what reaches the model, and up to five queries share one billed request", "Per-request prices published without login, and invalid, rate-limited and failed requests are not billed", "Hosted MCP server with OAuth or a key; the local server is in the official registry under the verified ai.perplexity namespace", "security.txt valid to 31 December 2027, a SOC 2 Type II report and a SECURITY.md that takes private reports" ], "weaknesses": [ "The FAQ says uptime and recovery time are not guaranteed, and the terms carry no SLA", "No free allowance and prepaid credits with a card; Stripe Projects still needs a $10 purchase", "Project keys have no scopes or spending limits, so any key can run every API on the account", "No guidance on treating returned snippets as untrusted text was found in the docs or the MCP server", "The DPA says Perplexity Search may follow different data terms, and no retention period for search queries is stated" ], "agentNotes": [ "Set `max_tokens_per_page` and `max_tokens` before calling; extracted text otherwise fills the context, and the price does not change with size", "Skip results with an empty `snippet` and dedupe by `url` when sending a `query` array; each query costs one rate-limit unit", "Use `search_type: \"fast\"` for $1 per 1,000 when latency and cost matter more than depth", "On 429 wait for Retry-After, then back off; on 402 stop and ask the user to add credits", "Use the Search API for sources and the Agent API's web_search tool for a written answer with citations" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 70.2 } ], "editorialScores": { "ergonomics": 85, "maintenance": 82, "payments": 25, "reliability": 80, "schema": 89, "security": 56, "transparency": 51 }, "provenanceScore": 80, "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 perplexityai", "http": "curl -X POST https://api.perplexity.ai/search \\\n -H \"Authorization: Bearer $PERPLEXITY_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"query\": \"renewable energy technologies\", \"max_results\": 10, \"max_tokens\": 50000, \"max_tokens_per_page\": 4096}'", "claudeCode": "claude mcp add --transport http perplexity https://api.perplexity.ai/mcp", "config": { "mcpServers": { "perplexity": { "url": "https://api.perplexity.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/perplexity-search-api" }, "sameCompany": [ "perplexity-space", "pplx-decider", "pplx-decider-flash" ], "area": "web-data", "unitPrices": [ { "item": "Search API request", "unit": "1k-requests", "usd": 5, "note": "Up to five queries in one request billed once; failed and rate-limited requests not billed" }, { "item": "Search API request with Fast Search", "unit": "1k-requests", "usd": 1, "note": "`search_type: \"fast\"`" }, { "item": "Agent API web_search call", "unit": "1k-calls", "usd": 2.5, "note": "Plus model tokens; $1.00 with Fast Search" }, { "item": "Agent API fetch_url call", "unit": "1k-calls", "usd": 0.5, "note": "Plus model tokens" } ], "provenance": { "legalEntity": "Perplexity AI, Inc.", "domain": "perplexity.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.perplexity.ai/hub/legal/perplexity-api-terms-of-service", "privacy": "https://www.perplexity.ai/hub/legal/privacy-notice", "statusPage": "https://status.perplexity.com/", "changelog": "https://docs.perplexity.ai/docs/resources/changelog", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "The API Terms of Service (last updated 23 January 2026) name Perplexity AI, Inc. and California law. The Data Processing Addendum (last updated 13 August 2026) deletes personal data within 30 days of the service ending and notes that Perplexity Search may follow different data terms.", "www.perplexity.ai/.well-known/security.txt is valid until 31 December 2027 and links www.perplexity.ai/security.", "The status page moved to incident.io on 10 September 2026 and has Website, App, Computer and API components, with no separate Search component.", "docs.perplexity.ai/robots.txt allows the docs and carries Content-Signal ai-train=yes, search=yes, ai-input=yes. The terms have no clause on automated access to the website.", "The changelog dates entries by month only. Domain registration was not checked." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/perplexity-search-api.json", "live": { "slug": "perplexity-search-api", "probe": { "target": "https://api.perplexity.ai/mcp", "method": "get", "lastAt": "2026-11-07T18:20:46.568623937Z", "lastOk": true, "lastStatus": 401, "lastMs": 254, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 164, "p95ms24h": 262, "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.perplexity.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:53.516499278Z" }, "versions": [ { "registry": "mcp-registry", "name": "ai.perplexity/mcp-server", "version": "1.2.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@perplexity-ai/mcp-server", "version": "1.3.0", "seenAt": "2026-11-06T23:55:31.394431614Z" }, { "registry": "npm", "name": "@perplexity-ai/perplexity_ai", "version": "0.41.0", "seenAt": "2026-11-06T23:55:30.575713692Z" }, { "registry": "pypi", "name": "perplexityai", "version": "0.46.1", "released": "2026-10-23", "seenAt": "2026-11-06T23:55:30.34668899Z" } ], "githubStars": 2612, "npmWeekly": 97298, "pypiWeekly": 401537, "securityTxt": { "url": "https://perplexity.ai/.well-known/security.txt", "state": "valid", "expires": "2027-12-31T00:00:00Z", "checkedAt": "2026-11-07T16:01:03.917430365Z" }, "llmsTxt": { "url": "https://docs.perplexity.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:36.681222085Z" }, "pages": [ { "url": "https://docs.perplexity.ai/docs/resources/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:27.675707255Z", "changedAt": "2026-11-06T13:29:48.535494355Z", "fingerprint": "a52a171e1f1f" }, { "url": "https://www.perplexity.ai/hub/legal/privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:32:54.875760985Z", "changedAt": "2026-11-06T13:53:25.792168971Z", "fingerprint": "29c9dd01613d" }, { "url": "https://www.perplexity.ai/hub/legal/perplexity-api-terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:32:50.897959644Z", "changedAt": "2026-11-06T13:53:22.592031411Z", "fingerprint": "6a7e4a95f45b" } ], "mcpTools": { "url": "https://api.perplexity.ai/mcp", "checkedAt": "2026-11-07T01:46:49.011542458Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:49.011542458Z" }, "updatedAt": "2026-11-07T18:21:53.516499278Z" } }, "edges": [ { "by": 24, "category": "ergonomics", "leads": "perplexity-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": "`max_results` 1 to 20, `max_tokens` and `max_tokens_per_page` cap the extracted text, and results are title, url, snippet and two dates. The MCP server has four tools (23 of 25). Domain, language, recency, publication and update date filters and `country`, with up to five queries in one request. No pagination or offset (16 of 20). 429 bodies name the limit hit, the SDKs map status codes to typed errors, and 402 marks an empty balance. Search-specific error bodies beyond 422 validation are not documented (13 of 20). Searches only read, failed and rate-limited requests are not billed, and the MCP server sets readOnlyHint true, destructiveHint false and idempotentHint false on every tool (18 of 20). Only `query` is required. Official Python and TypeScript SDKs, a CLI and a Python Search SDK (15). 23 + 16 + 13 + 18 + 15 = 85." }, "scores": { "a": 61, "b": 85 } }, { "by": 23, "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": "Project API keys, shown once, revocable, and generated and revoked through two documented endpoints with a rotation guide. No per-key scopes or spending limits were found. The hosted MCP server also takes Sign in with Perplexity (OAuth). Keys go in the Authorization header only (22 of 30, as on the Decisions API listing). Search only reads, and MCP clients can disable tools, but any key reaches every API on the account, including the Agent API's sandbox and MCP tools (8 of 20). Snippets are third-party page text, and no guidance on treating them as untrusted was found in the docs, the MCP server or its SECURITY.md (0 of 15). Responses carry a request `id`, and the console shows usage by key. The Audit API covers enterprise organisations' web app events with its own keys, not API calls (8 of 15). security.txt valid until 31 December 2027 linking a security page, a SOC 2 Type II report, a 2025 HIPAA gap assessment and a CAIQlite listed on the trust centre, and a SECURITY.md on the MCP server that takes private reports through GitHub advisories or security@perplexity.ai. The trust centre is drawn by script and wasn't read (18 of 20). 22 + 8 + 0 + 8 + 18 = 56." }, "scores": { "a": 79, "b": 56 } }, { "by": 21, "category": "schema", "leads": "perplexity-search-api", "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.0 at docs.perplexity.ai/openapi.json describes `POST /search` with typed request and response schemas, listed in llms.txt (25). llms.txt indexes every page, each with a Markdown twin (10). The overview says what a result holds, that snippets can be empty, when to use the Search API instead of the Agent API, and that it takes queries not URLs and does not re-fetch pages (19 of 20). `search_type` is an enum, `max_results`, `max_tokens` and `max_tokens_per_page` carry minimum and maximum, country and language codes carry lengths, and `query` is a string or an array. The recency filter is an enum in the docs, and date filters are `MM/DD/YYYY` strings (14 of 15). Python, TypeScript and cURL examples with a recorded response. The spec documents only 200 and 422 for `/search`, and status codes are listed on the SDK error-handling page and the rate-limit page rather than for Search (11 of 15). A public changelog with several entries a month, dated by month only, and an unversioned `/search` path (10 of 15). 25 + 10 + 19 + 14 + 11 + 10 = 89." }, "scores": { "a": 68, "b": 89 } }, { "by": 12, "category": "reliability", "leads": "perplexity-search-api", "name": "Reliability", "reasons": { "a": "Graded on the hosted lines, for the Foundry Agent Service tools agents call. Azure status page with post-incident reviews and a Foundry Agent Service component (20). The history page read on 6 November lists one review in the 90 days from 8 August that names Foundry Agent Service, intermittent failures and latency in Sweden Central from 10:03 to 15:58 UTC on 29 September 2026. It was one region and partial, and the review doesn't name Grounding with Bing, so minor only, the reading the Azure Translator listing got for the same review (20). The pricing page publishes 150 transactions a second and 1 million a day for each Grounding with Bing resource (15). The web search troubleshooting table says to answer 429 with exponential backoff and retries. No Retry-After or tool-specific overload guidance was found, and searches have no side effects (8 of 15). No SLA naming Grounding with Bing was found. The terms make it a First Party Consumption Service apart from the Online Services terms, and the Online Services SLA document wasn't opened (0). Grounding with Bing Custom Search is marked preview and Grounding with Bing Search is not, but no page read states general availability for it or for the web_search tool, and the .NET SDK is in preview (5 of 10). 20 + 20 + 15 + 8 + 0 + 5 = 68.", "b": "Graded on the hosted lines, for `POST /search` and the hosted MCP server. status.perplexity.com, on incident.io since 10 September 2026, has an API component with an RSS feed and a JSON summary. There is no separate Search component (20). In the 90 days from 8 August the feed lists 'Investigating API issue' on 13 August, resolved with no detail, a usage-based billing issue on 3 September, and on 9 October elevated errors on the website, app and Computer, where the API 'remained operational throughout'. Minor only, with the caveat that history before the migration may be incomplete (20). The Search API is limited to 50 query units a second with a burst of 50 on every tier, and the other APIs publish QPS and token limits per tier (15). 429 carries Retry-After and an `error.type`, the SDKs retry 429 and 5xx twice honouring Retry-After, the Search best-practices page shows backoff, and failed or rate-limited searches are not billed. Searches have no side effects (15). The FAQ says Perplexity does not guarantee uptime, failure frequency or recovery time, and the terms carry no SLA (0). No beta label on the Search API, launched on 25 September 2025 (10). 20 + 20 + 15 + 15 + 0 + 10 = 80." }, "scores": { "a": 68, "b": 80 } }, { "by": 5, "category": "payments", "leads": "perplexity-search-api", "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 in the docs, pricing page, OpenAPI or llms.txt (0). $5 per 1,000 successful requests, $1 with Fast Search, published without a login, with failed and rate-limited requests not billed (20). Usage is prepaid with a card on the billing page, and no free allowance was found. The console playground needs no key but is a page for a person, not an API allowance (0). A person signs up in the console. The Stripe Projects route provisions a project, key and credits from a terminal, but needs a person's Stripe account with a payment method and a $10 minimum purchase (5 of 20, as on the Decisions API listing). 0 + 20 + 0 + 5 = 25." }, "scores": { "a": 20, "b": 25 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Microsoft", "b": "Perplexity", "name": "Vendor" }, { "a": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "b": "https://api.perplexity.ai/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or 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": "Proprietary service under the Perplexity API Terms of Service. The MCP server is MIT and the official SDKs Apache-2.0", "name": "Licence" }, { "a": "3", "b": "4", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "ai.perplexity/mcp-server", "name": "MCP registry" }, { "a": "2026-11-02", "b": "2026-10-23", "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" } ], "faq": [ { "answer": "Perplexity Search API scores 70.2 (BB) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth.", "question": "Which is better for AI agents, Grounding with Bing Search or Perplexity Search API?" }, { "answer": "Perplexity Search API, 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 Perplexity Search API?" }, { "answer": "Grounding with Bing Search uses an OAuth sign-in. Perplexity Search API takes an API key or an OAuth sign-in.", "question": "Do Grounding with Bing Search and Perplexity Search 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 Perplexity Search API at https://api.perplexity.ai/mcp.", "question": "Can an agent call Grounding with Bing Search and Perplexity Search API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 79 against 56" ], "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": [ "Reliability, 80 against 68", "Schema \u0026 documentation, 89 against 68", "Agent ergonomics, 85 against 61", "Payments \u0026 pricing, 25 against 20" ], "also": [ "Cheaper for web search, $1 against $14 per 1,000 requests", "Agent-ready, a grade of BB or better", "Runs on your own machine" ], "goodFor": "Agents on any model that need raw ranked sources with extracted text at a low per-request price, and teams that want cited answers from the same key through the Agent API.", "slug": "perplexity-search-api", "watchFor": "The FAQ says uptime and recovery time are not guaranteed, and the terms carry no SLA" } ], "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-perplexity-search-api.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-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/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-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-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-perplexity-search-api.json", "title": "Brave Search API + MCP vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-perplexity-search-api.json", "title": "Cloudflare Web Search API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-perplexity-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/exa-mcp-vs-perplexity-search-api.json", "title": "Exa API + MCP vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-perplexity-search-api.json", "title": "Firecrawl MCP vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api.json", "title": "Kagi Search API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api.json", "title": "Linkup vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api.json", "title": "Mojeek Web Search API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/mojeek-vs-perplexity-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/parallel-search-api-vs-perplexity-search-api.json", "title": "Parallel Search and Task APIs vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-searchapi-io.json", "title": "Perplexity Search API vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpapi.json", "title": "Perplexity Search API vs SerpApi", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serper.json", "title": "Perplexity Search API vs Serper", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serphouse.json", "title": "Perplexity Search API vs SERPHouse", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite.json", "title": "Perplexity Search API vs SerpKite", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-specstream.json", "title": "Perplexity Search API vs SpecStream", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tavily-mcp.json", "title": "Perplexity Search API vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tinyfish-search.json", "title": "Perplexity Search API vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-valyu.json", "title": "Perplexity Search API vs Valyu", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-you-com-api.json", "title": "Perplexity Search API vs You.com APIs", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-perplexity-search-api.json", "title": "Arcmira vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/arcmira-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-api.json", "title": "Grep AI vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-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": 12, "edge": "perplexity-search-api", "key": "reliability", "name": "Reliability", "perplexity-search-api": 80, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bing-grounding": 68, "by": 21, "edge": "perplexity-search-api", "key": "schema", "name": "Schema \u0026 documentation", "perplexity-search-api": 89, "weight": 13 }, { "bing-grounding": 61, "by": 24, "edge": "perplexity-search-api", "key": "ergonomics", "name": "Agent ergonomics", "perplexity-search-api": 85, "weight": 13 }, { "bing-grounding": 79, "by": 23, "edge": "bing-grounding", "key": "security", "name": "Security \u0026 auth", "perplexity-search-api": 56, "weight": 14 }, { "bing-grounding": 20, "by": 5, "edge": "perplexity-search-api", "key": "payments", "name": "Payments \u0026 pricing", "perplexity-search-api": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bing-grounding": 80, "by": 2, "edge": "perplexity-search-api", "key": "maintenance", "name": "Maintenance \u0026 community", "perplexity-search-api": 82, "weight": 7 }, { "bing-grounding": 66, "by": 0, "edge": "", "key": "transparency", "name": "Transparency \u0026 trust", "perplexity-search-api": 66, "weight": 7 } ], "summary": "Perplexity Search API scores 70.2 (BB) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth. Both do web search. Perplexity Search API 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.", "perplexity-search-api": "Raw ranked results with token-capped page text from Perplexity's own index, $5 per 1,000 requests or $1 with Fast Search, an OpenAPI description and a hosted MCP server with read-only annotations. Uptime is not guaranteed, there is no free allowance, keys carry no scopes, and no guidance on untrusted page text was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api", "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.min.md" }, "markdown": "Perplexity Search API scores 70.2 (BB) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth. Both do web search. Perplexity Search API 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- Perplexity Search API: grade BB, 70.2/100, rank #210 of 1486. Markdown https://www.anchorterminal.com/tools/perplexity-search-api.md · JSON https://www.anchorterminal.com/api/v1/tools/perplexity-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- Security \u0026 auth, 79 against 56\n\nWatch for: The Bing tools never return raw results to developers, only a model-written answer with citation links\n\n### Perplexity Search API (BB)\n\nGood for: Agents on any model that need raw ranked sources with extracted text at a low per-request price, and teams that want cited answers from the same key through the Agent API.\n\nAhead on:\n- Reliability, 80 against 68\n- Schema \u0026 documentation, 89 against 68\n- Agent ergonomics, 85 against 61\n- Payments \u0026 pricing, 25 against 20\n\nAlso in its favour:\n- Cheaper for web search, $1 against $14 per 1,000 requests\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n\nWatch for: The FAQ says uptime and recovery time are not guaranteed, and the terms carry no SLA\n\n\n## Why the edge\n\n### Agent ergonomics: Perplexity Search API +24\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- Perplexity Search API (85): `max_results` 1 to 20, `max_tokens` and `max_tokens_per_page` cap the extracted text, and results are title, url, snippet and two dates. The MCP server has four tools (23 of 25). Domain, language, recency, publication and update date filters and `country`, with up to five queries in one request. No pagination or offset (16 of 20). 429 bodies name the limit hit, the SDKs map status codes to typed errors, and 402 marks an empty balance. Search-specific error bodies beyond 422 validation are not documented (13 of 20). Searches only read, failed and rate-limited requests are not billed, and the MCP server sets readOnlyHint true, destructiveHint false and idempotentHint false on every tool (18 of 20). Only `query` is required. Official Python and TypeScript SDKs, a CLI and a Python Search SDK (15). 23 + 16 + 13 + 18 + 15 = 85.\n\n### Security \u0026 auth: Grounding with Bing Search +23\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- Perplexity Search API (56): Project API keys, shown once, revocable, and generated and revoked through two documented endpoints with a rotation guide. No per-key scopes or spending limits were found. The hosted MCP server also takes Sign in with Perplexity (OAuth). Keys go in the Authorization header only (22 of 30, as on the Decisions API listing). Search only reads, and MCP clients can disable tools, but any key reaches every API on the account, including the Agent API's sandbox and MCP tools (8 of 20). Snippets are third-party page text, and no guidance on treating them as untrusted was found in the docs, the MCP server or its SECURITY.md (0 of 15). Responses carry a request `id`, and the console shows usage by key. The Audit API covers enterprise organisations' web app events with its own keys, not API calls (8 of 15). security.txt valid until 31 December 2027 linking a security page, a SOC 2 Type II report, a 2025 HIPAA gap assessment and a CAIQlite listed on the trust centre, and a SECURITY.md on the MCP server that takes private reports through GitHub advisories or security@perplexity.ai. The trust centre is drawn by script and wasn't read (18 of 20). 22 + 8 + 0 + 8 + 18 = 56.\n\n### Schema \u0026 documentation: Perplexity Search API +21\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- Perplexity Search API (89): OpenAPI 3.1.0 at docs.perplexity.ai/openapi.json describes `POST /search` with typed request and response schemas, listed in llms.txt (25). llms.txt indexes every page, each with a Markdown twin (10). The overview says what a result holds, that snippets can be empty, when to use the Search API instead of the Agent API, and that it takes queries not URLs and does not re-fetch pages (19 of 20). `search_type` is an enum, `max_results`, `max_tokens` and `max_tokens_per_page` carry minimum and maximum, country and language codes carry lengths, and `query` is a string or an array. The recency filter is an enum in the docs, and date filters are `MM/DD/YYYY` strings (14 of 15). Python, TypeScript and cURL examples with a recorded response. The spec documents only 200 and 422 for `/search`, and status codes are listed on the SDK error-handling page and the rate-limit page rather than for Search (11 of 15). A public changelog with several entries a month, dated by month only, and an unversioned `/search` path (10 of 15). 25 + 10 + 19 + 14 + 11 + 10 = 89.\n\n### Reliability: Perplexity Search API +12\n\n- Grounding with Bing Search (68): Graded on the hosted lines, for the Foundry Agent Service tools agents call. Azure status page with post-incident reviews and a Foundry Agent Service component (20). The history page read on 6 November lists one review in the 90 days from 8 August that names Foundry Agent Service, intermittent failures and latency in Sweden Central from 10:03 to 15:58 UTC on 29 September 2026. It was one region and partial, and the review doesn't name Grounding with Bing, so minor only, the reading the Azure Translator listing got for the same review (20). The pricing page publishes 150 transactions a second and 1 million a day for each Grounding with Bing resource (15). The web search troubleshooting table says to answer 429 with exponential backoff and retries. No Retry-After or tool-specific overload guidance was found, and searches have no side effects (8 of 15). No SLA naming Grounding with Bing was found. The terms make it a First Party Consumption Service apart from the Online Services terms, and the Online Services SLA document wasn't opened (0). Grounding with Bing Custom Search is marked preview and Grounding with Bing Search is not, but no page read states general availability for it or for the web_search tool, and the .NET SDK is in preview (5 of 10). 20 + 20 + 15 + 8 + 0 + 5 = 68.\n- Perplexity Search API (80): Graded on the hosted lines, for `POST /search` and the hosted MCP server. status.perplexity.com, on incident.io since 10 September 2026, has an API component with an RSS feed and a JSON summary. There is no separate Search component (20). In the 90 days from 8 August the feed lists 'Investigating API issue' on 13 August, resolved with no detail, a usage-based billing issue on 3 September, and on 9 October elevated errors on the website, app and Computer, where the API 'remained operational throughout'. Minor only, with the caveat that history before the migration may be incomplete (20). The Search API is limited to 50 query units a second with a burst of 50 on every tier, and the other APIs publish QPS and token limits per tier (15). 429 carries Retry-After and an `error.type`, the SDKs retry 429 and 5xx twice honouring Retry-After, the Search best-practices page shows backoff, and failed or rate-limited searches are not billed. Searches have no side effects (15). The FAQ says Perplexity does not guarantee uptime, failure frequency or recovery time, and the terms carry no SLA (0). No beta label on the Search API, launched on 25 September 2025 (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.\n\n### Payments \u0026 pricing: Perplexity Search API +5\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- Perplexity Search API (25): No x402, MPP or L402 in the docs, pricing page, OpenAPI or llms.txt (0). $5 per 1,000 successful requests, $1 with Fast Search, published without a login, with failed and rate-limited requests not billed (20). Usage is prepaid with a card on the billing page, and no free allowance was found. The console playground needs no key but is a page for a person, not an API allowance (0). A person signs up in the console. The Stripe Projects route provisions a project, key and credits from a terminal, but needs a person's Stripe account with a payment method and a $10 minimum purchase (5 of 20, as on the Decisions API listing). 0 + 20 + 0 + 5 = 25.\n\n## Score by category\n\n| Category | Weight | Grounding with Bing Search | Perplexity Search API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 68 | 80 | Perplexity Search API +12 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 89 | Perplexity Search API +21 |\n| Agent ergonomics | 13% (16.2 this run) | 61 | 85 | Perplexity Search API +24 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 56 | Grounding with Bing Search +23 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 25 | Perplexity Search API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 82 | Perplexity Search API +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 66 | even |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.7 · B** | **70.2 · BB** | |\n\n## Facts side by side\n\n| Fact | Grounding with Bing Search | Perplexity Search API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft | Perplexity |\n| Hosted endpoint | `https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses` | `https://api.perplexity.ai/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP, stdio |\n| Auth | OAuth | OAuth or 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 | Proprietary service under the Perplexity API Terms of Service. The MCP server is MIT and the official SDKs Apache-2.0 |\n| Tools exposed | 3 | 4 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `ai.perplexity/mcp-server` |\n| Last release | 2026-11-02 | 2026-10-23 |\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\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**Perplexity Search API.** Raw ranked results with token-capped page text from Perplexity's own index, $5 per 1,000 requests or $1 with Fast Search, an OpenAPI description and a hosted MCP server with read-only annotations. Uptime is not guaranteed, there is no free allowance, keys carry no scopes, and no guidance on untrusted page text was found.\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### Perplexity Search API\n\n1. Set `max_tokens_per_page` and `max_tokens` before calling; extracted text otherwise fills the context, and the price does not change with size\n2. Skip results with an empty `snippet` and dedupe by `url` when sending a `query` array; each query costs one rate-limit unit\n3. Use `search_type: \"fast\"` for $1 per 1,000 when latency and cost matter more than depth\n4. On 429 wait for Retry-After, then back off; on 402 stop and ask the user to add credits\n5. Use the Search API for sources and the Agent API's web_search tool for a written answer with citations\n\n## Questions\n\n### Which is better for AI agents, Grounding with Bing Search or Perplexity Search API?\n\nPerplexity Search API scores 70.2 (BB) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth.\n\n### Which is cheaper for web search, Grounding with Bing Search or Perplexity Search API?\n\nPerplexity Search API, 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 Perplexity Search API need an API key?\n\nGrounding with Bing Search uses an OAuth sign-in. Perplexity Search API takes an API key or an OAuth sign-in.\n\n### Can an agent call Grounding with Bing Search and Perplexity Search 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 Perplexity Search API at https://api.perplexity.ai/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bing-grounding\", \"b\": \"perplexity-search-api\"}`. From a terminal: `anchor compare bing-grounding perplexity-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/perplexity-search-api.json\n\n## Other comparisons with Grounding with Bing Search or Perplexity Search 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 Perplexity Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-search-api.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 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 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 Perplexity Search API](https://www.anchorterminal.com/compare/brave-search-mcp-vs-perplexity-search-api.md)\n- [Cloudflare Web Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-perplexity-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- [Exa API + MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/exa-mcp-vs-perplexity-search-api.md)\n- [Firecrawl MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-perplexity-search-api.md)\n- [Kagi Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api.md)\n- [Linkup vs Perplexity Search API](https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api.md)\n- [Mojeek Web Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api.md)\n- [NewsCatcher vs Perplexity Search API](https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.md)\n- [Parallel Search and Task APIs vs Perplexity Search API](https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.md)\n- [Perplexity Search API vs SearchAPI.io](https://www.anchorterminal.com/compare/perplexity-search-api-vs-searchapi-io.md)\n- [Perplexity Search API vs SerpApi](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpapi.md)\n- [Perplexity Search API vs Serper](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serper.md)\n- [Perplexity Search API vs SERPHouse](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serphouse.md)\n- [Perplexity Search API vs SerpKite](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite.md)\n- [Perplexity Search API vs SpecStream](https://www.anchorterminal.com/compare/perplexity-search-api-vs-specstream.md)\n- [Perplexity Search API vs Tavily API + MCP](https://www.anchorterminal.com/compare/perplexity-search-api-vs-tavily-mcp.md)\n- [Perplexity Search API vs TinyFish Search](https://www.anchorterminal.com/compare/perplexity-search-api-vs-tinyfish-search.md)\n- [Perplexity Search API vs Valyu](https://www.anchorterminal.com/compare/perplexity-search-api-vs-valyu.md)\n- [Perplexity Search API vs You.com APIs](https://www.anchorterminal.com/compare/perplexity-search-api-vs-you-com-api.md)\n- [Arcmira vs Perplexity Search API](https://www.anchorterminal.com/compare/arcmira-vs-perplexity-search-api.md)\n- [Grep AI vs Perplexity Search API](https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-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 Perplexity Search API", "url": "" } ], "description": "Perplexity Search scores 70.2 (BB) to Grounding with Bing Search's 63.7 (B) for web search. Perplexity Search 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", "Perplexity Search API BB 70.2", "scores" ], "h1": "Grounding with Bing Search vs Perplexity Search API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bing-grounding-vs-perplexity-search-api", "published": "2026-10-01", "section": "tools", "title": "Grounding with Bing Search vs Perplexity Search for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api" }, "tokens": { "markdown": 6300, "slim": 3580 }, "version": 1 }