{ "data": { "a": { "slug": "bing-grounding", "name": "Grounding with Bing Search", "vendor": "Microsoft", "vendorUrl": "https://www.microsoft.com/bing/apis", "kind": "http-api", "category": "search", "summary": "Grounding with Bing Search is Microsoft's web search tool for agents in Foundry Agent Service. A Foundry model searches Bing during a Responses API run and returns an answer with URL citations, through the bing_grounding and web_search tools.", "url": "https://www.anchorterminal.com/tools/bing-grounding", "markdownUrl": "https://www.anchorterminal.com/tools/bing-grounding.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bing-grounding.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bing-grounding.json", "dns": "bing-grounding.grade.anchorterminal.com", "license": "Proprietary service under the customer's Microsoft agreement and the separate Grounding with Bing terms of use, which exclude it from the Microsoft Data Protection Addendum", "transports": [ "streamable-http" ], "remoteUrl": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "packages": [ { "registry": "pypi", "name": "azure-ai-projects" }, { "registry": "npm", "name": "@azure/ai-projects" } ], "auth": "oauth", "authNotes": "Microsoft Entra ID bearer token for the Foundry project (scope https://ai.azure.com/.default, for example through DefaultAzureCredential), with the Foundry User role to create and run agents. The bing_grounding tool also needs a Grounding with Bing resource whose key is stored in a project connection, created by someone with Contributor and Foundry Project Manager. The agent never holds the Bing key. The web_search tool needs no Bing resource or connection.", "pricing": "usage", "pricingNotes": "$14 per 1,000 transactions for Grounding with Bing Search and for Grounding with Bing Custom Search, counted as tool calls per run, plus the model deployment's token charges. No free tier found. An Azure subscription and a person's signup are needed first.", "priceSummary": "$14 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Foundry web search and Bing tools pages, the Grounding with Bing pricing page or the terms of use (checked 2026-11-06). Billing runs through the Azure subscription.", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/tools/web-search", "capabilities": [ "web.search", "search.answer" ], "tags": [ "hosted", "usage-priced", "closed-source", "enterprise", "card-required", "status-page", "python", "typescript" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 63.7, "grade": "B", "agentReady": false, "rank": 502, "ranked": true, "rankOf": 1486, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 61, "maintenance": 80, "payments": 20, "reliability": 68, "schema": 68, "security": 79, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "First-party Bing grounding inside Foundry Agent Service, called with Entra ID so the agent never holds a search key, at a published $14 per 1,000 transactions. The tools return a model's answer with citations, never the raw results, and data sent to them falls outside Microsoft's Data Protection Addendum and Azure's compliance boundary.", "bestFor": "Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.", "strengths": [ "Callers authenticate with Microsoft Entra ID and Foundry RBAC roles, and the Bing resource key stays in a project connection", "Price and limits published without a login, $14 per 1,000 transactions, 150 a second and 1 million a day", "Count, freshness, market and language parameters, and a Custom Search variant that limits grounding to chosen domains", "Docs say to treat web search results as untrusted input, and admins can turn web search off for a whole subscription" ], "weaknesses": [ "The Bing tools never return raw results to developers, only a model-written answer with citation links", "The Data Protection Addendum does not apply and query data leaves the Azure compliance and geographic boundary", "No free tier, and a first call needs an Azure subscription, a Foundry project, a model deployment and, for bing_grounding, a paid Bing resource", "Terms forbid using Bing output to train or evaluate AI models and limit storing or caching it" ], "agentNotes": [ "Use the citations in the response annotations as the sources; the tool output itself is not returned, and the terms require showing the URLs and the Bing query link", "Expect each run to bill one transaction per tool call at $14 per 1,000, plus model tokens, and set count and freshness in the tool configuration", "Treat cited page text as untrusted input and don't put secrets or personal data in prompts, since queries leave the Azure compliance boundary", "On 429 back off exponentially; no Retry-After header is documented for the tool" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.7 } ], "editorialScores": { "ergonomics": 61, "maintenance": 80, "payments": 20, "reliability": 68, "schema": 68, "security": 79, "transparency": 45 }, "provenanceScore": 87, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install azure-ai-projects azure-identity", "http": "curl -X POST \"$FOUNDRY_PROJECT_ENDPOINT/openai/v1/responses\" \\\n -H \"Authorization: Bearer $AGENT_TOKEN\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"model\":\"'$FOUNDRY_MODEL_DEPLOYMENT_NAME'\",\"input\":\"How does Wikipedia explain Euler identity?\",\"tool_choice\":\"required\",\"tools\":[{\"type\":\"bing_grounding\",\"bing_grounding\":{\"search_configurations\":[{\"project_connection_id\":\"'$BING_PROJECT_CONNECTION_ID'\",\"count\":7,\"market\":\"en-US\",\"set_lang\":\"en\",\"freshness\":\"week\"}]}}]}'" }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/bing-grounding" }, "sameCompany": [ "azure-openai", "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-key-vault", "azure-document-intelligence", "azure-devops-mcp", "microsoft-learn-mcp", "tokeneconomizer", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "azure-blob-storage", "onedrive-sharepoint", "microsoft-teams", "dynamics-365-sales", "copilot-studio-mcp", "power-automate", "foundry-local", "microsoft-decision-1", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph", "microsoft-graph-people", "mage-vl-cowork" ], "area": "web-data", "unitPrices": [ { "item": "Grounding with Bing Search transaction", "unit": "1k-requests", "usd": 14, "note": "Counted as tool calls per run, plus the model deployment's token charges" }, { "item": "Grounding with Bing Custom Search transaction", "unit": "1k-requests", "usd": 14, "note": "Same limits, 150 a second and 1 million a day" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/bing/apis/grounding-legal-enterprise", "privacy": "https://privacy.microsoft.com/en-us/privacystatement", "statusPage": "https://azure.status.microsoft/en-us/status", "changelog": "https://learn.microsoft.com/en-us/azure/foundry/whats-new-foundry", "securityTxt": "expired", "checked": "2026-11-06", "notes": [ "The Foundry project endpoint is on services.ai.azure.com, a Microsoft domain. Domain registration date carried from the Azure listings' provenance.", "The Grounding with Bing terms of use (updated November 2025) are subject to the customer's Microsoft agreement (MCA, MBSA or MOSA) and name no separate contracting entity. They forbid using output on sites that block the customer's crawler, using links for crawling or scraping, and bypassing transaction limits.", "www.microsoft.com/.well-known/security.txt still carries Expires 2026-09-23T16:00:00.000Z on 6 November 2026.", "learn.microsoft.com/robots.txt allows the documentation paths read. The Azure status history page lists post-incident reviews for five years." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bing-grounding.json", "live": { "slug": "bing-grounding", "probe": { "target": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "method": "get", "lastAt": "2026-11-07T18:20:13.927615013Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "invalid character \"{\" in host name", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 0 }, { "date": "2026-11-07", "probes": 187, "ok": 0 } ], "outages": [ { "start": "2026-11-06T22:45:07.390416052Z", "end": "0001-01-01T00:00:00Z", "note": "invalid character \"{\" in host name" } ] }, "versions": [ { "registry": "npm", "name": "@azure/ai-projects", "version": "2.10.0", "seenAt": "2026-11-06T23:11:06.900508365Z" }, { "registry": "pypi", "name": "azure-ai-projects", "version": "2.10.0", "released": "2026-10-30", "seenAt": "2026-11-06T23:11:05.00335007Z" } ], "npmWeekly": 1368538, "pypiWeekly": 1896178, "securityTxt": { "url": "https://microsoft.com/.well-known/security.txt", "state": "valid", "expires": "2027-10-27T16:00:00.000Z", "checkedAt": "2026-11-07T16:02:01.196666056Z" }, "pages": [ { "url": "https://www.microsoft.com/bing/apis/grounding-legal-enterprise", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:31:40.128456318Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ddf25722851a" } ], "updatedAt": "2026-11-07T18:20:13.927615013Z" } }, "answer": "Grounding with Bing Search and Grep AI score within a point of each other on agent readiness, 63.7 (B) and 62.9 (B). Grep AI leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.", "b": { "slug": "grep-ai", "name": "Grep AI", "vendor": "Parcha Labs, Inc.", "vendorUrl": "https://grep.ai", "kind": "http-api", "category": "search", "summary": "Grep is a hosted platform from Parcha Labs for building and running research agents that return cited reports and structured output. Outside agents reach it through a REST API, a remote MCP server, an A2A endpoint and two SDKs.", "url": "https://www.anchorterminal.com/tools/grep-ai", "markdownUrl": "https://www.anchorterminal.com/tools/grep-ai.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/grep-ai.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/grep-ai.json", "dns": "grep-ai.grade.anchorterminal.com", "repo": "https://github.com/Parcha-ai/grepai-skills", "license": "Proprietary service under Parcha Labs' terms of service. The grep-research-skills package on npm is MIT. The @parcha/agentrun and parcha-agentrun SDK packages state no licence in their registry metadata", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.grep.ai/api/v2/runs", "packages": [ { "registry": "npm", "name": "@parcha/agentrun" }, { "registry": "pypi", "name": "parcha-agentrun" }, { "registry": "npm", "name": "grep-research-skills" } ], "auth": "mixed", "authNotes": "A Bearer credential on every call except the public agent list and publicly shared runs. Self-serve API keys (`parcha-` prefix) are created in the developer dashboard or at POST /api/v2/keys, and can be listed and revoked. The MCP server and delegated integrations take OAuth access tokens issued by Descope, with scopes research:read, research:write, billing:read, experts:read and experts:write. An agent with an AgentMail inbox can sign in through AgentID with an Ed25519 key and no human account. No partner or sales approval is documented for the self-serve plans.", "pricing": "freemium", "pricingNotes": "Credits, with a medium-effort task counted as 20. The Free Trial has 100 one-time credits and the pricing table marks it without API access, while the 4 October 2026 changelog says new personal accounts start with 500 Wallet credits. Pay As You Go tops up a wallet from $20, also marked without API access. Pro is $200 a month for 1,500 credits and Ultra $500 for 4,500, both with API access. Team plans go through sales. The page says $20 buys 200 credits and its Markdown twin says 100. Whether signup needs a card isn't stated (https://grep.ai/pricing, checked 2026-11-02).", "priceSummary": "$200 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "Not available. The changelog entry of 8 May 2026 announces x402 and MPP payments for API research, but GET https://api.grep.ai/mpp/v1/api returned 503 `gateway_disabled` (\"MPP gateway is disabled on this deployment\") on 8 October and 2 November 2026, and the grep-research-skills README says the wallet path returns once the gateway is generally available (checked 2026-11-02).", "endpoints": [] }, "toolCount": 137, "popularity": { "githubStars": null, "npmWeekly": 334, "pypiWeekly": 52, "asOf": "2026-10-08" }, "docsUrl": "https://grep.ai/developers", "llmsTxt": "https://grep.ai/llms.txt", "openapi": "https://api.grep.ai/api/v2/openapi.json", "capabilities": [ "search.research", "search.answer", "kyc.business", "kyc.screening", "kyc.documents" ], "tags": [ "hosted", "freemium", "mcp", "oauth", "openapi", "llms-txt", "python", "typescript", "async-jobs", "webhooks", "status-page" ], "lastRelease": "2026-10-20", "graded": true, "anchor": { "graded": true, "score": 62.9, "grade": "B", "agentReady": false, "rank": 533, "ranked": true, "rankOf": 1486, "categoryRank": 17, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 74, "payments": 40, "reliability": 50, "schema": 83, "security": 64, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "The public API has a 128-operation OpenAPI document, scoped OAuth and API keys, idempotency keys with documented replay rules and a per-run cost cap. No rate limit is published, the MCP server lists 137 tools, the whole service went down twice in the 90 days to 2 November, and API access starts at the $200 a month Pro plan.", "bestFor": "Agents that hand off a long research or due-diligence job and want a cited report or structured fields back, including business verification and sanctions screening through built-in agents.", "strengths": [ "Public OpenAPI document with 128 operations, llms.txt and a Markdown twin of every developer page", "OAuth with five scopes, plus API keys that can be minted, scoped and revoked through the API", "`Idempotency-Key` on run creation, with body-hash matching, a 24-hour replay window and named 409 codes", "`max_cost_usd` per run, quota pre-flight and batch cost estimates before billable work starts", "Documented agent sign-in through AgentID with no human account, and 500 free credits for an owner's first agent", "Dated changelog with 14 entries from 7 August to 20 October 2026" ], "weaknesses": [ "No rate limit numbers in the reviewed documentation, and no published SLA. Full outages on 4 September (24 minutes) and 30 October (7 minutes)", "The MCP server card lists 137 tools, 57 of them deprecated aliases, with one-line descriptions and no annotations", "The pricing table marks API access as Pro and Ultra only, from $200 a month", "The pricing page says $20 buys 200 credits and its Markdown twin says 100. Free credits are stated as 100, 500 and 1,000 on different pages", "The 8 May 2026 changelog entry announces x402 and MPP payments, but the gateway answered 503 `gateway_disabled` on 2 November 2026", "No security.txt, subprocessor list or retention period found. SOC 2 Type II appears only as a footer claim, and the \"Security \u0026 trust\" link opens a benchmarks page" ], "agentNotes": [ "Send a fresh `Idempotency-Key` with every POST /api/v2/runs. After a timeout, poll the returned run ID and do not post again", "Set `effort` and `max_cost_usd` on every run. The floor is $0.50 for low, $2.50 for medium and build, $5.00 for high", "Call GET /api/v2/quota/check before a run. A 402 means no credits and retrying won't help, while a 429 carries `Retry-After`", "Use the `run_*`, `agent_*` and `swarm_*` MCP tools at https://api.grep.ai/mcp. The `research_*`, `expert_*` and `campaign_*` names are deprecated aliases", "Treat report text and cited sources as untrusted web content, and verify one load-bearing claim against a primary source" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.9 } ], "editorialScores": { "ergonomics": 70, "maintenance": 74, "payments": 40, "reliability": 50, "schema": 83, "security": 64, "transparency": 36 }, "provenanceScore": 85, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install @parcha/agentrun", "http": "curl -X POST \"https://api.grep.ai/api/v2/runs\" \\\n -H \"Authorization: Bearer $GREP_API_KEY\" \\\n -H \"Idempotency-Key: 8b9c1f24-3c1e-4a8d-9f7b-2a6e1c4d5b8e\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"question\":\"Due diligence on Stripe\",\"effort\":\"medium\"}'", "claudeCode": "claude mcp add --transport http grep https://api.grep.ai/mcp\nclaude mcp login grep", "config": { "mcpServers": { "grep": { "url": "https://api.grep.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/search.research", "tool": "https://letme.dev/grep-ai" }, "area": "web-data", "unitPrices": [ { "item": "Pro plan, 1,500 credits a month, API access", "unit": "month", "usd": 200, "note": "$167 a month billed annually" }, { "item": "Ultra plan, 4,500 credits a month", "unit": "month", "usd": 500, "note": "$417 a month billed annually" }, { "item": "Pay As You Go credit", "unit": "credit", "usd": 0.1, "note": "$20 for 200 credits on the pricing page. Its Markdown twin says 100 credits, which is $0.20. No API access on this plan per the table" } ], "provenance": { "legalEntity": "Parcha Labs, Inc.", "domain": "grep.ai", "domainRegistered": "2018-04-20", "domainNote": "Registered in 2018 and transferred on 2025-10-19, so the registration date predates the company's use of it.", "endpointOnVendorDomain": true, "terms": "https://grep.ai/terms", "privacy": "https://grep.ai/privacy", "statusPage": "https://status.grep.ai", "changelog": "https://grep.ai/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms of service, last updated 20 March 2026, are a contract with Parcha Labs, Inc., a Delaware corporation, governed by California law.", "The privacy policy, last updated 5 October 2026, names Parcha Labs, Inc. and the websites www.parcha.ai and grep.parcha.ai.", "The API, the MCP server and the A2A endpoint answer on api.grep.ai. OAuth tokens come from Descope at api.descope.com.", "grep.ai/.well-known/security.txt and api.grep.ai/.well-known/security.txt return 404. grep.ai/trust and grep.ai/security return 404.", "RDAP for grep.ai gives a registration date of 2018-04-20 and a transfer on 2025-10-19.", "The status page's support link is support@parcha.ai and its privacy link points to parcha.ai." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/grep-ai.json", "live": { "slug": "grep-ai", "probe": { "target": "https://api.grep.ai/api/v2/runs", "method": "get", "lastAt": "2026-11-07T18:20:28.711576005Z", "lastOk": true, "lastStatus": 401, "lastMs": 463, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.92, "p50ms24h": 366, "p95ms24h": 460, "samples24h": 239, "samples30d": 7463, "days": [ { "date": "2026-10-08", "probes": 93, "ok": 93 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 252 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 252 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 250 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 183 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.grep.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:13.873754405Z" }, "versions": [ { "registry": "github", "name": "Parcha-ai/grepai-skills", "version": "v0.2.0", "released": "2026-08-04", "seenAt": "2026-11-06T23:31:17.343670403Z" }, { "registry": "npm", "name": "@parcha/agentrun", "version": "0.3.6", "seenAt": "2026-11-06T23:31:15.147980263Z" }, { "registry": "npm", "name": "grep-research-skills", "version": "0.2.0", "seenAt": "2026-11-06T23:31:16.618593403Z" }, { "registry": "pypi", "name": "parcha-agentrun", "version": "0.2.1", "released": "2026-09-30", "seenAt": "2026-11-06T23:31:16.377788056Z" } ], "githubStars": 2, "npmWeekly": 336, "pypiWeekly": 21, "securityTxt": { "url": "https://grep.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:30.039104122Z" }, "llmsTxt": { "url": "https://grep.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:39.189807584Z" }, "domain": { "domain": "grep.ai", "registered": "2018-04-20", "source": "https://rdap.identitydigital.services/rdap/domain/grep.ai", "checkedAt": "2026-11-01T14:26:20.014848352Z" }, "pages": [ { "url": "https://grep.ai/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:10:39.133932414Z", "changedAt": "2026-11-06T13:32:44.195749968Z", "fingerprint": "b2c46460857a" }, { "url": "https://grep.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:10:41.715097295Z", "changedAt": "2026-11-06T13:32:46.726727473Z", "fingerprint": "b50267997523" }, { "url": "https://grep.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:10:43.416139624Z", "changedAt": "2026-11-06T13:32:48.542806474Z", "fingerprint": "61f7ae5ed58d" }, { "url": "https://grep.ai/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:10:45.461789114Z", "changedAt": "2026-11-06T13:32:50.740021371Z", "fingerprint": "b92beb6db8a5" } ], "mcpTools": { "url": "https://api.grep.ai/mcp", "checkedAt": "2026-11-07T01:45:17.533792685Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:45:17.533792685Z" }, "github": { "repo": "parcha-ai/grepai-skills", "checkedAt": "2026-11-02T09:14:59.133383273Z", "stars": 3, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T06:32:53Z", "openIssues": 1, "openPRs": 1, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 2, "ci": { "branch": "main", "runs": 2, "success": 2, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-09-30T18:10:13Z" }, "replies": { "sampled": 1, "unanswered": 1 } }, "updatedAt": "2026-11-07T18:21:13.873754405Z" } }, "edges": [ { "by": 20, "category": "payments", "leads": "grep-ai", "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 machine payment protocol on the live endpoints. The changelog of 8 May 2026 announces x402 and MPP, and the gateway answered 503 `gateway_disabled` on 8 October and again on 2 November 2026 (0). Plan and credit prices are public, but only the medium tier's credit cost is published and the page and its Markdown twin disagree on credits per dollar (10). 100 free trial credits on the pricing page, 500 Wallet credits for new personal accounts in the 4 October changelog entry, and 500 for an owner's first agent through AgentID. The pricing page doesn't say whether a card is needed, and its table marks the trial without API access (15). AgentID sign-in is documented as needing no human account, but it depends on an AgentMail inbox and a browser step, and we didn't run it (15)." }, "scores": { "a": 20, "b": 40 } }, { "by": 18, "category": "reliability", "leads": "bing-grounding", "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 API and MCP server. status.grep.ai runs on incident.io, and since 30 October 2026 it has an API component beside Website (20). Two incidents in the 90 days from 4 August, read from the page's feed and incident pages. On 4 September \"Grep.ai currently unavailable\" said Grep.ai was \"experiencing an outage\" for 24 minutes, and on 30 October the Website and API components were both in full outage from 17:17 to 17:24 UTC after an infrastructure provider's failure. Each is a full outage of the whole service, which this run reads as a major however short, so two majors (5). The 8 October check read the September outage as minor by its length. No rate limit numbers found in the docs or the OpenAPI document (0). 429 `rate_limited` carries `Retry-After`, and run creation takes an `Idempotency-Key` with documented replay rules (15). The FAQ mentions SLA guarantees for enterprise customers, and no SLA is published (0). API v2 and the MCP server carry no beta label. The SDKs are at 0.2.1 per the 8 October check, and PyPI classified the Python one as Alpha then (10)." }, "scores": { "a": 68, "b": 50 } }, { "by": 15, "category": "schema", "leads": "grep-ai", "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": "Public OpenAPI document at api.grep.ai/api/v2/openapi.json, now 128 operations on 98 paths and 159 schemas (25). llms.txt and a Markdown twin of each developer page (10). Most operations carry a description, and the `effort` field says what each tier returns and how long it takes. 19 operations have none, and the MCP server card gives each of its 137 tools one line. The MCP input schemas need OAuth and weren't read (12). 75 enums, numeric bounds and `additionalProperties: false` on the run request (12). Curl examples and an 11-code error registry in the docs, but the OpenAPI document has no examples and documents only 200 and 422 responses (9). The path is versioned, v1 and 42 v2 operations are marked deprecated, and the dated changelog now runs to v3.71 on 20 October 2026, with 14 entries since 4 August (15)." }, "scores": { "a": 68, "b": 83 } }, { "by": 15, "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": "OAuth through Descope with five scopes, and API keys that can be created with a subset of scopes, listed and revoked through the API (30). Read scopes, `validate_only` and `dry_run` on agent changes, a per-run `max_cost_usd` and versioned restores. No confirmation step for deletes or for making a run public (14). Reports are built from untrusted web pages. The docs describe an SSRF-guarded fetch for context files, and no prompt-injection guidance for callers was found (3). Each run has a timeline of execution events, and billing transactions and usage are readable through the API (12). The footer claims SOC 2 Type II with no report linked, and its \"Security \u0026 trust\" link opens a performance benchmarks page. security.txt returns 404, and no disclosure policy or bug bounty was found, so this is a bare SOC 2 claim, which this run reads as 5 (5). Webhooks are signed with the API key itself." }, "scores": { "a": 79, "b": 64 } }, { "by": 9, "category": "ergonomics", "leads": "grep-ai", "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": "The MCP server card lists 137 tools, 57 of them deprecated aliases, with no documented toolsets. Reports default to plain Markdown and large files come back as signed URLs, so some credit back (8). Cursor pagination with `limit` on runs, timelines and transactions, and server-side filters on the skill and tool lists (18). One error envelope with stable codes and a `request_id`, and 402 for credits kept apart from 429 for rate (20). `Idempotency-Key` with body-hash matching and a 24-hour replay window. The server card shows no readOnlyHint or destructiveHint annotations, and the live tool list wasn't read (12). Only `question` is required and `effort` defaults to low. TypeScript and Python SDKs exist, though one docs page still calls the release pending and names a PyPI package that returns 404 (12)." }, "scores": { "a": 61, "b": 70 } }, { "by": 6, "category": "maintenance", "leads": "bing-grounding", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service with official SDKs, as the other Azure listings are. The web search page was updated on 2 November 2026 and the Bing tools page on 12 October, and azure-ai-projects 2.10.0 shipped on PyPI and npm on 30 October 2026, the SDK that carries the tool types (30). azure-ai-projects released 2.6.0 (4 September), 2.6.1, 2.7.0, 2.8.0 (5 October), 2.9.0 (17 October) and 2.10.0 in the 90 days from 8 August. Their changelogs weren't read for web search changes, so they count as SDK releases (20). Microsoft Learn feedback, Microsoft Q\u0026A and the Azure SDK issue trackers, whose reply times weren't sampled (10 of 15). Current official SDKs in Python, JavaScript, .NET and Java, the .NET one in preview (15). The SDKs live in the azure-sdk monorepos and CI wasn't checked (5 of 10). 30 + 20 + 10 + 15 + 5 = 80.", "b": "The changelog's newest entry is v3.71 on 20 October 2026, 13 days before this check (30). 14 dated changelog entries since 4 August, from v3.1.1 on 7 August to v3.71 on 20 October (20). Closed service with a public changelog and support at support@parcha.ai. We didn't test whether support answers (8). Current SDKs in two languages per the 8 October check (@parcha/agentrun and parcha-agentrun 0.2.1, 30 September), with docs that lag them. Not found in the official MCP registry (12). The skills repository runs a test workflow and hasn't changed since 30 September. The SDK repositories named in the package metadata asked for credentials, so their CI wasn't read (4). The 8 October PyPI reading came from a path pypi.org's robots.txt disallows and is struck; npm and PyPI didn't answer on 2 November." }, "scores": { "a": 80, "b": 74 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Microsoft", "b": "Parcha Labs, Inc.", "name": "Vendor" }, { "a": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "b": "https://api.grep.ai/api/v2/runs", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "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 Parcha Labs' terms of service. The grep-research-skills package on npm is MIT. The @parcha/agentrun and parcha-agentrun SDK packages state no licence in their registry metadata", "name": "Licence" }, { "a": "3", "b": "137", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-11-02", "b": "2026-10-20", "name": "Last release" }, { "a": "2025-11-01", "b": "2026-03-20", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "2026-09-21", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "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": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "334 npm/wk, 52 PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Grounding with Bing Search and Grep AI score within a point of each other on agent readiness, 63.7 (B) and 62.9 (B). Grep AI leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, Grounding with Bing Search or Grep AI?" }, { "answer": "Grounding with Bing Search uses an OAuth sign-in. Grep AI takes an API key or an OAuth sign-in.", "question": "Do Grounding with Bing Search and Grep AI 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 Grep AI at https://api.grep.ai/api/v2/runs.", "question": "Can an agent call Grounding with Bing Search and Grep AI without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 68 against 50", "Security \u0026 auth, 79 against 64", "Maintenance \u0026 community, 80 against 74", "Transparency \u0026 trust, 66 against 61" ], "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, 83 against 68", "Agent ergonomics, 70 against 61", "Payments \u0026 pricing, 40 against 20" ], "also": null, "goodFor": "Agents that hand off a long research or due-diligence job and want a cited report or structured fields back, including business verification and sanctions screening through built-in agents.", "slug": "grep-ai", "watchFor": "No rate limit numbers in the reviewed documentation, and no published SLA. Full outages on 4 September (24 minutes) and 30 October (7 minutes)" } ], "history": { "bing-grounding": null, "grep-ai": [ { "causes": [ "reliability", "product", "correction" ], "date": "2026-11-02", "delta": -1.7, "from": 64.6, "fromGrade": "B", "to": 62.9, "toGrade": "B" }, { "causes": [ "evidence" ], "date": "2026-10-27", "delta": 0.2, "from": 64.4, "fromGrade": "B", "to": 64.6, "toGrade": "B" } ] }, "job": { "capability": "search.answer", "name": "Answer 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-grep-ai.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Grep AI", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-grep-ai" }, { "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-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/cloudflare-web-search-vs-grep-ai.json", "title": "Cloudflare Web Search API vs Grep AI", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-grep-ai" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-grep-ai.json", "title": "DeepSeek Search and Fetch API vs Grep AI", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-grep-ai" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-grep-ai.json", "title": "Firecrawl MCP vs Grep AI", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-grep-ai" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-kagi-search.json", "title": "Grep AI vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-kagi-search" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-mojeek.json", "title": "Grep AI vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-searchapi-io.json", "title": "Grep AI vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-serpapi.json", "title": "Grep AI vs SerpApi", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-serper.json", "title": "Grep AI vs Serper", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-serpkite.json", "title": "Grep AI vs SerpKite", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-grep-ai.json", "title": "Arcmira vs Grep AI", "url": "https://www.anchorterminal.com/compare/arcmira-vs-grep-ai" }, { "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-grep-ai.json", "title": "Exa API + MCP vs Grep AI", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-grep-ai" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-linkup.json", "title": "Grep AI vs Linkup", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-linkup" }, { "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/grep-ai-vs-parallel-search-api.json", "title": "Grep AI vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-parallel-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/grep-ai-vs-specstream.json", "title": "Grep AI vs SpecStream", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-tavily-mcp.json", "title": "Grep AI vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-tinyfish-search.json", "title": "Grep AI vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-valyu.json", "title": "Grep AI vs Valyu", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-you-com-api.json", "title": "Grep AI vs You.com APIs", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-grep-ai.json", "title": "Brave Search API + MCP vs Grep AI", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-grep-ai" } ], "panel": null, "scores": [ { "bing-grounding": 68, "by": 18, "edge": "bing-grounding", "grep-ai": 50, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bing-grounding": 68, "by": 15, "edge": "grep-ai", "grep-ai": 83, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "bing-grounding": 61, "by": 9, "edge": "grep-ai", "grep-ai": 70, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "bing-grounding": 79, "by": 15, "edge": "bing-grounding", "grep-ai": 64, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "bing-grounding": 20, "by": 20, "edge": "grep-ai", "grep-ai": 40, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bing-grounding": 80, "by": 6, "edge": "bing-grounding", "grep-ai": 74, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "bing-grounding": 66, "by": 5, "edge": "bing-grounding", "grep-ai": 61, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Grounding with Bing Search and Grep AI score within a point of each other on agent readiness, 63.7 (B) and 62.9 (B). Grep AI leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing. Both do answer search.", "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.", "grep-ai": "The public API has a 128-operation OpenAPI document, scoped OAuth and API keys, idempotency keys with documented replay rules and a per-run cost cap. No rate limit is published, the MCP server lists 137 tools, the whole service went down twice in the 90 days to 2 November, and API access starts at the $200 a month Pro plan." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai", "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai.min.md" }, "markdown": "Grounding with Bing Search and Grep AI score within a point of each other on agent readiness, 63.7 (B) and 62.9 (B). Grep AI leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing. Both do answer search.\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- Grep AI: grade B, 62.9/100, rank #533 of 1486. Markdown https://www.anchorterminal.com/tools/grep-ai.md · JSON https://www.anchorterminal.com/api/v1/tools/grep-ai.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- Reliability, 68 against 50\n- Security \u0026 auth, 79 against 64\n- Maintenance \u0026 community, 80 against 74\n- Transparency \u0026 trust, 66 against 61\n\nWatch for: The Bing tools never return raw results to developers, only a model-written answer with citation links\n\n### Grep AI (B)\n\nGood for: Agents that hand off a long research or due-diligence job and want a cited report or structured fields back, including business verification and sanctions screening through built-in agents.\n\nAhead on:\n- Schema \u0026 documentation, 83 against 68\n- Agent ergonomics, 70 against 61\n- Payments \u0026 pricing, 40 against 20\n\nWatch for: No rate limit numbers in the reviewed documentation, and no published SLA. Full outages on 4 September (24 minutes) and 30 October (7 minutes)\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Grep AI +20\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- Grep AI (40): No machine payment protocol on the live endpoints. The changelog of 8 May 2026 announces x402 and MPP, and the gateway answered 503 `gateway_disabled` on 8 October and again on 2 November 2026 (0). Plan and credit prices are public, but only the medium tier's credit cost is published and the page and its Markdown twin disagree on credits per dollar (10). 100 free trial credits on the pricing page, 500 Wallet credits for new personal accounts in the 4 October changelog entry, and 500 for an owner's first agent through AgentID. The pricing page doesn't say whether a card is needed, and its table marks the trial without API access (15). AgentID sign-in is documented as needing no human account, but it depends on an AgentMail inbox and a browser step, and we didn't run it (15).\n\n### Reliability: Grounding with Bing Search +18\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- Grep AI (50): Graded on the hosted API and MCP server. status.grep.ai runs on incident.io, and since 30 October 2026 it has an API component beside Website (20). Two incidents in the 90 days from 4 August, read from the page's feed and incident pages. On 4 September \"Grep.ai currently unavailable\" said Grep.ai was \"experiencing an outage\" for 24 minutes, and on 30 October the Website and API components were both in full outage from 17:17 to 17:24 UTC after an infrastructure provider's failure. Each is a full outage of the whole service, which this run reads as a major however short, so two majors (5). The 8 October check read the September outage as minor by its length. No rate limit numbers found in the docs or the OpenAPI document (0). 429 `rate_limited` carries `Retry-After`, and run creation takes an `Idempotency-Key` with documented replay rules (15). The FAQ mentions SLA guarantees for enterprise customers, and no SLA is published (0). API v2 and the MCP server carry no beta label. The SDKs are at 0.2.1 per the 8 October check, and PyPI classified the Python one as Alpha then (10).\n\n### Schema \u0026 documentation: Grep AI +15\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- Grep AI (83): Public OpenAPI document at api.grep.ai/api/v2/openapi.json, now 128 operations on 98 paths and 159 schemas (25). llms.txt and a Markdown twin of each developer page (10). Most operations carry a description, and the `effort` field says what each tier returns and how long it takes. 19 operations have none, and the MCP server card gives each of its 137 tools one line. The MCP input schemas need OAuth and weren't read (12). 75 enums, numeric bounds and `additionalProperties: false` on the run request (12). Curl examples and an 11-code error registry in the docs, but the OpenAPI document has no examples and documents only 200 and 422 responses (9). The path is versioned, v1 and 42 v2 operations are marked deprecated, and the dated changelog now runs to v3.71 on 20 October 2026, with 14 entries since 4 August (15).\n\n### Security \u0026 auth: Grounding with Bing Search +15\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- Grep AI (64): OAuth through Descope with five scopes, and API keys that can be created with a subset of scopes, listed and revoked through the API (30). Read scopes, `validate_only` and `dry_run` on agent changes, a per-run `max_cost_usd` and versioned restores. No confirmation step for deletes or for making a run public (14). Reports are built from untrusted web pages. The docs describe an SSRF-guarded fetch for context files, and no prompt-injection guidance for callers was found (3). Each run has a timeline of execution events, and billing transactions and usage are readable through the API (12). The footer claims SOC 2 Type II with no report linked, and its \"Security \u0026 trust\" link opens a performance benchmarks page. security.txt returns 404, and no disclosure policy or bug bounty was found, so this is a bare SOC 2 claim, which this run reads as 5 (5). Webhooks are signed with the API key itself.\n\n### Agent ergonomics: Grep AI +9\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- Grep AI (70): The MCP server card lists 137 tools, 57 of them deprecated aliases, with no documented toolsets. Reports default to plain Markdown and large files come back as signed URLs, so some credit back (8). Cursor pagination with `limit` on runs, timelines and transactions, and server-side filters on the skill and tool lists (18). One error envelope with stable codes and a `request_id`, and 402 for credits kept apart from 429 for rate (20). `Idempotency-Key` with body-hash matching and a 24-hour replay window. The server card shows no readOnlyHint or destructiveHint annotations, and the live tool list wasn't read (12). Only `question` is required and `effort` defaults to low. TypeScript and Python SDKs exist, though one docs page still calls the release pending and names a PyPI package that returns 404 (12).\n\n### Maintenance \u0026 community: Grounding with Bing Search +6\n\n- Grounding with Bing Search (80): Read as a closed service with official SDKs, as the other Azure listings are. The web search page was updated on 2 November 2026 and the Bing tools page on 12 October, and azure-ai-projects 2.10.0 shipped on PyPI and npm on 30 October 2026, the SDK that carries the tool types (30). azure-ai-projects released 2.6.0 (4 September), 2.6.1, 2.7.0, 2.8.0 (5 October), 2.9.0 (17 October) and 2.10.0 in the 90 days from 8 August. Their changelogs weren't read for web search changes, so they count as SDK releases (20). Microsoft Learn feedback, Microsoft Q\u0026A and the Azure SDK issue trackers, whose reply times weren't sampled (10 of 15). Current official SDKs in Python, JavaScript, .NET and Java, the .NET one in preview (15). The SDKs live in the azure-sdk monorepos and CI wasn't checked (5 of 10). 30 + 20 + 10 + 15 + 5 = 80.\n- Grep AI (74): The changelog's newest entry is v3.71 on 20 October 2026, 13 days before this check (30). 14 dated changelog entries since 4 August, from v3.1.1 on 7 August to v3.71 on 20 October (20). Closed service with a public changelog and support at support@parcha.ai. We didn't test whether support answers (8). Current SDKs in two languages per the 8 October check (@parcha/agentrun and parcha-agentrun 0.2.1, 30 September), with docs that lag them. Not found in the official MCP registry (12). The skills repository runs a test workflow and hasn't changed since 30 September. The SDK repositories named in the package metadata asked for credentials, so their CI wasn't read (4). The 8 October PyPI reading came from a path pypi.org's robots.txt disallows and is struck; npm and PyPI didn't answer on 2 November.\n\n## Score by category\n\n| Category | Weight | Grounding with Bing Search | Grep AI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 68 | 50 | Grounding with Bing Search +18 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 83 | Grep AI +15 |\n| Agent ergonomics | 13% (16.2 this run) | 61 | 70 | Grep AI +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 64 | Grounding with Bing Search +15 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | Grep AI +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 74 | Grounding with Bing Search +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 61 | Grounding with Bing Search +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.7 · B** | **62.9 · B** | |\n\n## Facts side by side\n\n| Fact | Grounding with Bing Search | Grep AI |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft | Parcha Labs, Inc. |\n| Hosted endpoint | `https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses` | `https://api.grep.ai/api/v2/runs` |\n| Transports | Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Pay per use | Freemium |\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 Parcha Labs' terms of service. The grep-research-skills package on npm is MIT. The @parcha/agentrun and parcha-agentrun SDK packages state no licence in their registry metadata |\n| Tools exposed | 3 | 137 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-11-02 | 2026-10-20 |\n| Terms last updated | 2025-11-01 | 2026-03-20 |\n| Privacy policy last updated | 2026-09-01 | 2026-09-21 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | yes | yes |\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 | not found in the text |\n| Popularity | none | 334 npm/wk, 52 PyPI/wk |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### Grounding with Bing Search\n\nNo score change since it was listed.\n\n### Grep AI\n\n- -1.7 on 2 November 2026: reliability, product, correction\n- +0.2 on 27 October 2026: new evidence\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**Grep AI.** The public API has a 128-operation OpenAPI document, scoped OAuth and API keys, idempotency keys with documented replay rules and a per-run cost cap. No rate limit is published, the MCP server lists 137 tools, the whole service went down twice in the 90 days to 2 November, and API access starts at the $200 a month Pro plan.\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### Grep AI\n\n1. Send a fresh `Idempotency-Key` with every POST /api/v2/runs. After a timeout, poll the returned run ID and do not post again\n2. Set `effort` and `max_cost_usd` on every run. The floor is $0.50 for low, $2.50 for medium and build, $5.00 for high\n3. Call GET /api/v2/quota/check before a run. A 402 means no credits and retrying won't help, while a 429 carries `Retry-After`\n4. Use the `run_*`, `agent_*` and `swarm_*` MCP tools at https://api.grep.ai/mcp. The `research_*`, `expert_*` and `campaign_*` names are deprecated aliases\n5. Treat report text and cited sources as untrusted web content, and verify one load-bearing claim against a primary source\n\n## Questions\n\n### Which is better for AI agents, Grounding with Bing Search or Grep AI?\n\nGrounding with Bing Search and Grep AI score within a point of each other on agent readiness, 63.7 (B) and 62.9 (B). Grep AI leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.\n\n### Do Grounding with Bing Search and Grep AI need an API key?\n\nGrounding with Bing Search uses an OAuth sign-in. Grep AI takes an API key or an OAuth sign-in.\n\n### Can an agent call Grounding with Bing Search and Grep AI 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 Grep AI at https://api.grep.ai/api/v2/runs.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bing-grounding\", \"b\": \"grep-ai\"}`. From a terminal: `anchor compare bing-grounding grep-ai`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bing-grounding.json and https://www.anchorterminal.com/api/v1/tools/grep-ai.json\n\n## Other comparisons with Grounding with Bing Search or Grep AI\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 Grep AI](https://www.anchorterminal.com/compare/agentcore-web-search-vs-grep-ai.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 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- [Cloudflare Web Search API vs Grep AI](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-grep-ai.md)\n- [DeepSeek Search and Fetch API vs Grep AI](https://www.anchorterminal.com/compare/deepseek-search-api-vs-grep-ai.md)\n- [Firecrawl MCP vs Grep AI](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-grep-ai.md)\n- [Grep AI vs Kagi Search API](https://www.anchorterminal.com/compare/grep-ai-vs-kagi-search.md)\n- [Grep AI vs Mojeek Web Search API](https://www.anchorterminal.com/compare/grep-ai-vs-mojeek.md)\n- [Grep AI vs SearchAPI.io](https://www.anchorterminal.com/compare/grep-ai-vs-searchapi-io.md)\n- [Grep AI vs SerpApi](https://www.anchorterminal.com/compare/grep-ai-vs-serpapi.md)\n- [Grep AI vs Serper](https://www.anchorterminal.com/compare/grep-ai-vs-serper.md)\n- [Grep AI vs SerpKite](https://www.anchorterminal.com/compare/grep-ai-vs-serpkite.md)\n- [Arcmira vs Grep AI](https://www.anchorterminal.com/compare/arcmira-vs-grep-ai.md)\n- [Exa API + MCP vs Grep AI](https://www.anchorterminal.com/compare/exa-mcp-vs-grep-ai.md)\n- [Grep AI vs Linkup](https://www.anchorterminal.com/compare/grep-ai-vs-linkup.md)\n- [Grep AI vs NewsCatcher](https://www.anchorterminal.com/compare/grep-ai-vs-newscatcher.md)\n- [Grep AI vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/grep-ai-vs-parallel-search-api.md)\n- [Grep AI vs Perplexity Search API](https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-api.md)\n- [Grep AI vs SpecStream](https://www.anchorterminal.com/compare/grep-ai-vs-specstream.md)\n- [Grep AI vs Tavily API + MCP](https://www.anchorterminal.com/compare/grep-ai-vs-tavily-mcp.md)\n- [Grep AI vs TinyFish Search](https://www.anchorterminal.com/compare/grep-ai-vs-tinyfish-search.md)\n- [Grep AI vs Valyu](https://www.anchorterminal.com/compare/grep-ai-vs-valyu.md)\n- [Grep AI vs You.com APIs](https://www.anchorterminal.com/compare/grep-ai-vs-you-com-api.md)\n- [Brave Search API + MCP vs Grep AI](https://www.anchorterminal.com/compare/brave-search-mcp-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 Grep AI", "url": "" } ], "description": "Grounding with Bing Search and Grep AI score within a point of each other for answer search, 63.7 and 62.9 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grounding with Bing Search B 63.7", "Grep AI B 62.9", "scores" ], "h1": "Grounding with Bing Search vs Grep AI", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bing-grounding-vs-grep-ai", "published": "2026-10-01", "section": "tools", "title": "Grounding with Bing Search vs Grep AI for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai" }, "tokens": { "markdown": 6350, "slim": 3780 }, "version": 1 }