{ "data": { "a": { "slug": "bing-grounding", "name": "Grounding with Bing Search", "vendor": "Microsoft", "vendorUrl": "https://www.microsoft.com/bing/apis", "kind": "http-api", "category": "search", "summary": "Grounding with Bing Search is Microsoft's web search tool for agents in Foundry Agent Service. A Foundry model searches Bing during a Responses API run and returns an answer with URL citations, through the bing_grounding and web_search tools.", "url": "https://www.anchorterminal.com/tools/bing-grounding", "markdownUrl": "https://www.anchorterminal.com/tools/bing-grounding.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bing-grounding.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bing-grounding.json", "dns": "bing-grounding.grade.anchorterminal.com", "license": "Proprietary service under the customer's Microsoft agreement and the separate Grounding with Bing terms of use, which exclude it from the Microsoft Data Protection Addendum", "transports": [ "streamable-http" ], "remoteUrl": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "packages": [ { "registry": "pypi", "name": "azure-ai-projects" }, { "registry": "npm", "name": "@azure/ai-projects" } ], "auth": "oauth", "authNotes": "Microsoft Entra ID bearer token for the Foundry project (scope https://ai.azure.com/.default, for example through DefaultAzureCredential), with the Foundry User role to create and run agents. The bing_grounding tool also needs a Grounding with Bing resource whose key is stored in a project connection, created by someone with Contributor and Foundry Project Manager. The agent never holds the Bing key. The web_search tool needs no Bing resource or connection.", "pricing": "usage", "pricingNotes": "$14 per 1,000 transactions for Grounding with Bing Search and for Grounding with Bing Custom Search, counted as tool calls per run, plus the model deployment's token charges. No free tier found. An Azure subscription and a person's signup are needed first.", "priceSummary": "$14 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Foundry web search and Bing tools pages, the Grounding with Bing pricing page or the terms of use (checked 2026-11-06). Billing runs through the Azure subscription.", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/tools/web-search", "capabilities": [ "web.search", "search.answer" ], "tags": [ "hosted", "usage-priced", "closed-source", "enterprise", "card-required", "status-page", "python", "typescript" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 63.7, "grade": "B", "agentReady": false, "rank": 502, "ranked": true, "rankOf": 1486, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 61, "maintenance": 80, "payments": 20, "reliability": 68, "schema": 68, "security": 79, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "First-party Bing grounding inside Foundry Agent Service, called with Entra ID so the agent never holds a search key, at a published $14 per 1,000 transactions. The tools return a model's answer with citations, never the raw results, and data sent to them falls outside Microsoft's Data Protection Addendum and Azure's compliance boundary.", "bestFor": "Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.", "strengths": [ "Callers authenticate with Microsoft Entra ID and Foundry RBAC roles, and the Bing resource key stays in a project connection", "Price and limits published without a login, $14 per 1,000 transactions, 150 a second and 1 million a day", "Count, freshness, market and language parameters, and a Custom Search variant that limits grounding to chosen domains", "Docs say to treat web search results as untrusted input, and admins can turn web search off for a whole subscription" ], "weaknesses": [ "The Bing tools never return raw results to developers, only a model-written answer with citation links", "The Data Protection Addendum does not apply and query data leaves the Azure compliance and geographic boundary", "No free tier, and a first call needs an Azure subscription, a Foundry project, a model deployment and, for bing_grounding, a paid Bing resource", "Terms forbid using Bing output to train or evaluate AI models and limit storing or caching it" ], "agentNotes": [ "Use the citations in the response annotations as the sources; the tool output itself is not returned, and the terms require showing the URLs and the Bing query link", "Expect each run to bill one transaction per tool call at $14 per 1,000, plus model tokens, and set count and freshness in the tool configuration", "Treat cited page text as untrusted input and don't put secrets or personal data in prompts, since queries leave the Azure compliance boundary", "On 429 back off exponentially; no Retry-After header is documented for the tool" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.7 } ], "editorialScores": { "ergonomics": 61, "maintenance": 80, "payments": 20, "reliability": 68, "schema": 68, "security": 79, "transparency": 45 }, "provenanceScore": 87, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install azure-ai-projects azure-identity", "http": "curl -X POST \"$FOUNDRY_PROJECT_ENDPOINT/openai/v1/responses\" \\\n -H \"Authorization: Bearer $AGENT_TOKEN\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"model\":\"'$FOUNDRY_MODEL_DEPLOYMENT_NAME'\",\"input\":\"How does Wikipedia explain Euler identity?\",\"tool_choice\":\"required\",\"tools\":[{\"type\":\"bing_grounding\",\"bing_grounding\":{\"search_configurations\":[{\"project_connection_id\":\"'$BING_PROJECT_CONNECTION_ID'\",\"count\":7,\"market\":\"en-US\",\"set_lang\":\"en\",\"freshness\":\"week\"}]}}]}'" }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/bing-grounding" }, "sameCompany": [ "azure-openai", "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-key-vault", "azure-document-intelligence", "azure-devops-mcp", "microsoft-learn-mcp", "tokeneconomizer", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "azure-blob-storage", "onedrive-sharepoint", "microsoft-teams", "dynamics-365-sales", "copilot-studio-mcp", "power-automate", "foundry-local", "microsoft-decision-1", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph", "microsoft-graph-people", "mage-vl-cowork" ], "area": "web-data", "unitPrices": [ { "item": "Grounding with Bing Search transaction", "unit": "1k-requests", "usd": 14, "note": "Counted as tool calls per run, plus the model deployment's token charges" }, { "item": "Grounding with Bing Custom Search transaction", "unit": "1k-requests", "usd": 14, "note": "Same limits, 150 a second and 1 million a day" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/bing/apis/grounding-legal-enterprise", "privacy": "https://privacy.microsoft.com/en-us/privacystatement", "statusPage": "https://azure.status.microsoft/en-us/status", "changelog": "https://learn.microsoft.com/en-us/azure/foundry/whats-new-foundry", "securityTxt": "expired", "checked": "2026-11-06", "notes": [ "The Foundry project endpoint is on services.ai.azure.com, a Microsoft domain. Domain registration date carried from the Azure listings' provenance.", "The Grounding with Bing terms of use (updated November 2025) are subject to the customer's Microsoft agreement (MCA, MBSA or MOSA) and name no separate contracting entity. They forbid using output on sites that block the customer's crawler, using links for crawling or scraping, and bypassing transaction limits.", "www.microsoft.com/.well-known/security.txt still carries Expires 2026-09-23T16:00:00.000Z on 6 November 2026.", "learn.microsoft.com/robots.txt allows the documentation paths read. The Azure status history page lists post-incident reviews for five years." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bing-grounding.json", "live": { "slug": "bing-grounding", "probe": { "target": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "method": "get", "lastAt": "2026-11-07T18:20:13.927615013Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "invalid character \"{\" in host name", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 0 }, { "date": "2026-11-07", "probes": 187, "ok": 0 } ], "outages": [ { "start": "2026-11-06T22:45:07.390416052Z", "end": "0001-01-01T00:00:00Z", "note": "invalid character \"{\" in host name" } ] }, "versions": [ { "registry": "npm", "name": "@azure/ai-projects", "version": "2.10.0", "seenAt": "2026-11-06T23:11:06.900508365Z" }, { "registry": "pypi", "name": "azure-ai-projects", "version": "2.10.0", "released": "2026-10-30", "seenAt": "2026-11-06T23:11:05.00335007Z" } ], "npmWeekly": 1368538, "pypiWeekly": 1896178, "securityTxt": { "url": "https://microsoft.com/.well-known/security.txt", "state": "valid", "expires": "2027-10-27T16:00:00.000Z", "checkedAt": "2026-11-07T16:02:01.196666056Z" }, "pages": [ { "url": "https://www.microsoft.com/bing/apis/grounding-legal-enterprise", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:31:40.128456318Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ddf25722851a" } ], "updatedAt": "2026-11-07T18:20:13.927615013Z" } }, "answer": "Grounding with Bing Search scores 63.7 (B) on agent readiness against Kagi Search API's 56.1 (C), and leads in 3 of 7 scored categories. Kagi Search API leads on agent ergonomics and transparency \u0026 trust.", "b": { "slug": "kagi-search", "name": "Kagi Search API", "vendor": "Kagi", "vendorUrl": "https://kagi.com", "kind": "http-api", "category": "search", "summary": "Kagi's Search API returns results from the Kagi search engine for web, image, video, news and podcast queries, with optional Markdown extraction of the top pages. It is a paid HTTP API in public preview, with a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/kagi-search", "markdownUrl": "https://www.anchorterminal.com/tools/kagi-search.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kagi-search.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kagi-search.json", "dns": "kagi-search.grade.anchorterminal.com", "repo": "https://github.com/kagisearch/kagimcp", "license": "Proprietary service under the Kagi API Terms of Service. The MCP server is MIT and the OpenAPI file states Apache-2.0", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://kagi.com/api/v1/search", "packages": [ { "registry": "pypi", "name": "kagimcp" } ], "auth": "api-key", "authNotes": "Self-serve API key from the portal at kagi.com/api, sent as `Authorization: Bearer \u003ckey\u003e` per the OpenAPI file. Each key can be limited to chosen products and to IP addresses or ranges, and deleted to revoke it. On Family and Team plans only the account owner can open the portal. The hosted MCP server takes the same key as a Bearer header, with no OAuth yet.", "pricing": "usage", "pricingNotes": "$12 per 1,000 searches and $4 per 1,000 extracted pages, pay as you go, invoiced every 30 days or when usage reaches $100. Prepaid credit and a spending cap are available. No free tier or sandbox. The quick start asks for a Kagi account and a payment method first. Enterprise volume prices are by quote (https://kagi.com/api/pricing, checked 2026-10-09).", "priceSummary": "$12 / 1k req", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI file, the API docs or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 535, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://help.kagi.com/kagi/api/overview.html", "openapi": "https://kagi.com/api/docs/_spec/openapi.yaml", "capabilities": [ "web.search", "web.fetch", "web.extract", "search.news", "search.images" ], "tags": [ "official", "hosted", "api-key", "closed-source", "usage-based", "openapi", "preview", "mcp", "ip-allowlist", "python", "typescript", "go", "rust" ], "lastRelease": "2026-08-21", "graded": true, "anchor": { "graded": true, "score": 56.1, "grade": "C", "agentReady": false, "rank": 841, "ranked": true, "rankOf": 1486, "categoryRank": 20, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 41, "payments": 20, "reliability": 43, "schema": 71, "security": 64, "transparency": 74 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "A public OpenAPI file, typed filters and API keys that can be limited by product and IP address make the API simple to call, at $12 per 1,000 searches. It is still a public preview, with no published rate limits and no free allowance, and the terms forbid storing results. Its status page logged only regional incidents since August.", "bestFor": "An owner who already pays for Kagi and wants its ranking, lenses and domain rules inside an agent, with page text in the same call.", "strengths": [ "Public OpenAPI 3.0 file for `POST /search` and `POST /extract`, with enums, ranges and request and response examples", "Each API key can be limited to chosen products and to IP addresses or ranges, and the billing page sets a spending cap in USD", "Per-unit prices are public, $12 per 1,000 searches and $4 per 1,000 extracted pages, with pay-as-you-go billing", "Searches can carry an inline lens, domain block, lower, raise and pin rules, date and region filters, and extraction of up to 10 result pages", "The privacy policy has an API section with retention periods, and says queries are not stored against the account" ], "weaknesses": [ "Public preview since 21 May 2026. The API terms say it is under active development with no uptime or service-level commitment", "No rate limit numbers are published, and the status page isn't linked from the docs, pricing, terms or changelog pages we read", "No free allowance. The quick start asks for a Kagi account and a payment method before the first call", "The API terms forbid storing or caching results beyond transient caching, building datasets from them, and probing or testing Kagi's systems", "The last dated API change is the 21 August 2026 Extract fix, and the MCP server's last tag is v0.1.5 of 8 April 2026" ], "agentNotes": [ "Send `POST https://kagi.com/api/v1/search` with a JSON body and `Authorization: Bearer \u003ckey\u003e`, as the OpenAPI file defines. Only `query` is required", "Set `limit` to cap results returned. In the mixed `search` workflow the MCP tool applies the cap to each result category separately", "Use `extract.count` (1 to 10) only when page text is needed. Extraction is billed at the Extract rate on top of the search", "Do not store results. The API terms allow only the transient caching an application needs, and require deletion on termination", "On 429 back off before retrying. The response covers both rate limiting and an exhausted usage limit, and no `Retry-After` header is documented. Check status.kagi.com for regional incidents" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.1 } ], "editorialScores": { "ergonomics": 75, "maintenance": 41, "payments": 20, "reliability": 43, "schema": 71, "security": 64, "transparency": 54 }, "provenanceScore": 94, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "uvx kagimcp", "http": "curl -X POST https://kagi.com/api/v1/search \\\n -H \"Authorization: Bearer $KAGI_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"query\":\"steve jobs\",\"workflow\":\"search\"}'", "claudeCode": "claude mcp add kagi https://mcp.kagi.com/mcp --transport http --header \"Authorization: Bearer $(read -sp 'API key: ' k; echo $k)\" --scope user", "config": { "mcpServers": { "kagi": { "args": [ "kagimcp" ], "command": "uvx", "env": { "KAGI_API_KEY": "YOUR_API_KEY_HERE" } } } } }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/kagi-search" }, "area": "web-data", "unitPrices": [ { "item": "Search", "unit": "1k-requests", "usd": 12, "note": "page extraction inside a search is billed at the Extract rate on top" }, { "item": "Extract", "unit": "1k-pages", "usd": 4, "note": "up to 10 URLs a request" } ], "provenance": { "legalEntity": "Kagi Inc.", "domain": "kagi.com", "domainRegistered": "1993-11-18", "domainNote": "kagi.com was registered in 1993, long before Kagi Inc. was founded in 2018.", "endpointOnVendorDomain": true, "terms": "https://kagi.com/privacy/api", "privacy": "https://kagi.com/privacy", "statusPage": "https://status.kagi.com/", "changelog": "https://kagi.com/changelog", "securityTxt": "valid", "checked": "2026-11-04", "notes": [ "The Kagi API Terms of Service (effective and last updated 22 September 2026) govern the Search API and incorporate the privacy policy and a Data Processing Addendum that is not yet published.", "The privacy policy at kagi.com/privacy has a Kagi API section added on 22 September 2026. The same page also holds the general Terms of Service.", "The API terms do not name a legal entity. The docs' company page gives Kagi Inc., and the privacy page describes Kagi as a Delaware public benefit corporation.", "kagi.com/.well-known/security.txt gives security@kagi.com and a bug bounty with a safe harbour policy, and has no Expires field. It is recorded as valid, although RFC 9116 asks for that field.", "status.kagi.com is an Instatus page with Kagi Search, Kagi API, Kagi Translate, Kagi Assistant and Other Services groups and a /history.atom feed. It wasn't found linked from the API docs, pricing, terms or changelog pages; a web search found it on 4 November 2026.", "The changelog covers every Kagi product. API entries are a few lines inside those posts.", "kagi.com/robots.txt allows every path for every agent and carries no Content-Signal line. help.kagi.com/robots.txt answered 404.", "The registration date came from an RDAP lookup on 9 October, a source this run doesn't use. Kept pending the correction pass." ], "score": 94 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/kagi-search.json", "live": { "slug": "kagi-search", "probe": { "target": "https://kagi.com/api/v1/search", "method": "get", "lastAt": "2026-11-07T18:20:33.100150768Z", "lastOk": true, "lastStatus": 404, "lastMs": 224, "authRequired": false, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 159, "p95ms24h": 448, "samples24h": 239, "samples30d": 7205, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "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": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 252 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.kagi.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:57.929767418Z" }, "versions": [ { "registry": "pypi", "name": "kagimcp", "version": "1.1.0", "released": "2026-10-28", "seenAt": "2026-11-06T23:36:18.273275631Z" } ], "githubStars": 560, "pypiWeekly": 907, "securityTxt": { "url": "https://kagi.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:02:05.625292402Z" }, "domain": { "domain": "kagi.com", "registered": "1993-11-18", "source": "https://rdap.verisign.com/com/v1/domain/kagi.com", "checkedAt": "2026-11-01T14:18:50.123684408Z" }, "pages": [ { "url": "https://kagi.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:11:53.635112538Z", "changedAt": "2026-11-06T13:33:57.614071228Z", "fingerprint": "b16eae5ff40e" }, { "url": "https://kagi.com/api/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:11:51.560663477Z", "changedAt": "2026-10-27T03:48:19.358068766Z", "fingerprint": "8e909f92ad50" }, { "url": "https://kagi.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:11:55.90595014Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2bfce4b7e89a" }, { "url": "https://kagi.com/privacy/api", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:11:57.59824854Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5a5c47392cf0" } ], "github": { "repo": "kagisearch/kagimcp", "checkedAt": "2026-11-02T08:57:55.693015256Z", "stars": 557, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-28T13:39:24Z", "openIssues": 4, "openPRs": 3, "issuesOpened90d": 5, "issuesClosed90d": 3, "prsMerged90d": 1, "replies": { "sampled": 19, "unanswered": 3, "medianDays": 5.3 } }, "updatedAt": "2026-11-07T18:20:33.100150768Z" } }, "edges": [ { "by": 39, "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 last dated API change is the Extract API fix in the changelog post of 21 August 2026, 75 days before this check. The posts of 10 September and 16 October carry no API item (20). That is the only dated API entry in the 90 days from 6 August (0). The MCP server's repository gained commits on 27 and 28 October 2026 (compact JSON results, `readOnlyHint`, per-page extraction errors) and a version bump to 1.1.0 with no tag, so no release is shown; PyPI didn't resolve for us. A public changelog that credits user reports, developers@kagi.com, a Discord `#api` forum and GitHub discussions. We could not read the issue list, since the GitHub API answered 403 (9). Four generated clients last synced on 26 May 2026, Python tagged only as 1.0.0rc3, TypeScript not on npm on 9 October, and `kagimcp` tagged last as v0.1.5 (8 April 2026). We did not look the server up in the MCP registry (8). The Python client has a generated CI workflow and the MCP server has a lock file but no CI workflow (4). 20 + 0 + 9 + 8 + 4 = 41." }, "scores": { "a": 80, "b": 41 } }, { "by": 25, "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": "Status page at status.kagi.com (Instatus), found through a web search on 4 November, with a Kagi API group of nine regional components such as `[API] us-east4` and `[API] europe-west2`, and history back to 2025 (20). In the 90 days from 6 August its feed and incident list show `[API]` incidents on single regions only. us-central1 on 12 September (1 hour 3 minutes), 19 September, 12 October and 19 October (2 to 3 minutes each), europe-west2 on 19 October (1 minute) and 20 October (8 hours 11 minutes, the region taken out of the global load balancer), asia-east2 on 30 September (4 minutes), australia-southeast1 on 11 September (1 minute) and asia-southeast1 on 7 August (about a minute). Each hit one region of nine, so all read as partial and the record is minor incidents only (20). The six 'API outage' entries (10, 20 and 26 August, two on 14 October and 22 October, 5 to 21 minutes each) name the API component of the Kagi Assistant group, not the Search API, and the 27 September database maintenance had an announced window. No rate limit numbers are published. The terms say only that limits and quotas apply per plan (0). The OpenAPI file documents 429 as 'Rate limited or usage limit exhausted' with no `Retry-After` header or backoff guidance. The calls are read-only, and Kagi's own MCP server retries 429 and 5xx twice by default (3). The pricing page lists SLAs under Enterprise by quote, and the API terms say there is no uptime or service-level commitment unless agreed in writing (0). The OpenAPI file still describes a preview period (0). 20 + 20 + 0 + 3 + 0 + 0 = 43." }, "scores": { "a": 68, "b": 43 } }, { "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": "Several named keys an account, each limited to chosen products and optionally to IP addresses or ranges, revoked by deleting. The v1 key travels only in the `Authorization` header. No expiry or OAuth (27). The API only reads. Per-key product limits and a spending cap in USD narrow what a leaked key can do (16). Search and Extract return third-party page text, and we found no prompt-injection guidance in the reference, the docs or the MCP README (2). The portal shows use count and last-used time per key and requests and cost per day per API, and every response carries a trace ID. No per-call log (7). security.txt with a contact, a bug bounty with a safe harbour policy, and an independent audit by Illumant cited on the security page, whose date we did not read. No SOC 2 or ISO 27001 statement found. security.txt re-read on 4 November (12). 27 + 16 + 2 + 7 + 12 = 64." }, "scores": { "a": 79, "b": 64 } }, { "by": 14, "category": "ergonomics", "leads": "kagi-search", "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": "`limit` caps results, extraction of page text is opt-in, snippet length follows an account setting, and an experimental Markdown response format exists. The MCP server has two tools (22). `page` 1 to 10, `limit` 1 to 1,024, lens and `filters` for domains, keywords, file type, dates and region (20). Errors return a namespaced `code`, a message, the field `location` and a trace ID, but no code catalogue is published and the linked error pages are not live (12). Both operations are read-only, so a retry is safe, though the docs do not say so and failed-call billing is stated only for extraction. The released MCP server sets no read-only annotations. A commit of 27 October adds `readOnlyHint` to its source with an untagged 1.1.0 version bump, not yet shown as released (10). Only `query` is required and defaults are stated. Generated clients exist for Python, TypeScript, Go and Rust, installable from GitHub. `@kagi/api` returned 404 on npm on 9 October (11). 22 + 20 + 12 + 10 + 11 = 75." }, "scores": { "a": 61, "b": 75 } }, { "by": 8, "category": "transparency", "leads": "kagi-search", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service. The terms of use, updated November 2025, are separate from the Online Services terms and sit under the customer's Microsoft agreement (15 of 30). The docs and the terms agree that the Data Protection Addendum and the Product Terms' privacy and security terms don't apply, that Microsoft and the customer are independent controllers, and that the query and parameters leave the Azure compliance and geographic boundary. The terms defer storage and use of query data to the general Microsoft Privacy Statement and state no retention period (15 of 30). The Bing Search APIs retirement was announced on 16 May 2025 for 11 August 2025, under three months' notice, and the web search page marks the Deep Research tool deprecated with a replacement. Microsoft's lifecycle policy covers Azure services, but no deprecation terms for Grounding with Bing were found (10 of 20). Data location for Bing processing isn't stated, and no sub-processor list for it was found (5 of 20). 15 + 15 + 10 + 5 = 45.", "b": "Closed service with clear API terms dated 22 September 2026. The MCP server is MIT and the OpenAPI file states Apache-2.0 (18). The privacy policy's API section agrees with the API terms. Queries are not stored against the account, load balancer and VM logs are kept 7 days and sampled Sentry errors 90 days. The Data Processing Addendum both documents cite is not yet published (23). v0 is marked deprecated with no end date, and the terms promise reasonable notice of breaking changes only where practicable (5). The privacy page names the payment processors and Sentry, the FAQ names GCP as the hosting provider and the docs name search sources, but there is no subprocessor list and no data locations (8). 18 + 23 + 5 + 8 = 54." }, "scores": { "a": 66, "b": 74 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Microsoft", "b": "Kagi", "name": "Vendor" }, { "a": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "b": "https://kagi.com/api/v1/search", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$14 per 1,000 requests", "b": "$12 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 Kagi API Terms of Service. The MCP server is MIT and the OpenAPI file states Apache-2.0", "name": "Licence" }, { "a": "3", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-11-02", "b": "2026-08-21", "name": "Last release" }, { "a": "2025-11-01", "b": "2026-09-22", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "no date given", "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": "yes", "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": "535 stars", "name": "Popularity" } ], "faq": [ { "answer": "Grounding with Bing Search scores 63.7 (B) on agent readiness against Kagi Search API's 56.1 (C), and leads in 3 of 7 scored categories. Kagi Search API leads on agent ergonomics and transparency \u0026 trust.", "question": "Which is better for AI agents, Grounding with Bing Search or Kagi Search API?" }, { "answer": "Kagi Search API, at $12 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 Kagi Search API?" }, { "answer": "Grounding with Bing Search uses an OAuth sign-in. Kagi Search API needs an API key.", "question": "Do Grounding with Bing Search and Kagi 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 Kagi Search API at https://kagi.com/api/v1/search.", "question": "Can an agent call Grounding with Bing Search and Kagi Search API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 68 against 43", "Security \u0026 auth, 79 against 64", "Maintenance \u0026 community, 80 against 41" ], "also": null, "goodFor": "Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.", "slug": "bing-grounding", "watchFor": "The Bing tools never return raw results to developers, only a model-written answer with citation links" }, { "aheadOn": [ "Agent ergonomics, 75 against 61", "Transparency \u0026 trust, 74 against 66" ], "also": [ "Cheaper for web search, $12 against $14 per 1,000 requests", "Runs on your own machine" ], "goodFor": "An owner who already pays for Kagi and wants its ranking, lenses and domain rules inside an agent, with page text in the same call.", "slug": "kagi-search", "watchFor": "Public preview since 21 May 2026. The API terms say it is under active development with no uptime or service-level commitment" } ], "history": { "bing-grounding": null, "kagi-search": [ { "causes": [ "evidence" ], "date": "2026-11-04", "delta": 7.4, "from": 48.7, "fromGrade": "D", "to": 56.1, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0, "from": 48.7, "fromGrade": "D", "to": 48.7, "toGrade": "D" } ] }, "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-kagi-search.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-kagi-search" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding.json", "title": "Arcmira vs Grounding with Bing Search", "url": "https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-kagi-search.json", "title": "Arcmira vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/arcmira-vs-kagi-search" }, { "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-linkup.json", "title": "Grounding with Bing Search vs Linkup", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek.json", "title": "Grounding with Bing Search vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.json", "title": "Grounding with Bing Search vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.json", "title": "Grounding with Bing Search vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.json", "title": "Grounding with Bing Search vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-searchapi-io.json", "title": "Grounding with Bing Search vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpapi.json", "title": "Grounding with Bing Search vs SerpApi", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serper.json", "title": "Grounding with Bing Search vs Serper", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serphouse.json", "title": "Grounding with Bing Search vs SERPHouse", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.json", "title": "Grounding with Bing Search vs SerpKite", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-specstream.json", "title": "Grounding with Bing Search vs SpecStream", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-tavily-mcp.json", "title": "Grounding with Bing Search vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-tinyfish-search.json", "title": "Grounding with Bing Search vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-valyu.json", "title": "Grounding with Bing Search vs Valyu", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-you-com-api.json", "title": "Grounding with Bing Search vs You.com APIs", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-kagi-search.json", "title": "Brave Search API + MCP vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-kagi-search" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-kagi-search.json", "title": "Cloudflare Web Search API vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-kagi-search" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-kagi-search.json", "title": "DeepSeek Search and Fetch API vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-kagi-search" }, { "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-kagi-search.json", "title": "Exa API + MCP vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-kagi-search" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-kagi-search.json", "title": "Firecrawl MCP vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-kagi-search" }, { "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/kagi-search-vs-linkup.json", "title": "Kagi Search API vs Linkup", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-mojeek.json", "title": "Kagi Search API vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-newscatcher.json", "title": "Kagi Search API vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-parallel-search-api.json", "title": "Kagi Search API vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-parallel-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/kagi-search-vs-searchapi-io.json", "title": "Kagi Search API vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-serpapi.json", "title": "Kagi Search API vs SerpApi", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-serper.json", "title": "Kagi Search API vs Serper", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-serphouse.json", "title": "Kagi Search API vs SERPHouse", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-serpkite.json", "title": "Kagi Search API vs SerpKite", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-specstream.json", "title": "Kagi Search API vs SpecStream", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-tavily-mcp.json", "title": "Kagi Search API vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-tinyfish-search.json", "title": "Kagi Search API vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-valyu.json", "title": "Kagi Search API vs Valyu", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-you-com-api.json", "title": "Kagi Search API vs You.com APIs", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-kagi-search.json", "title": "Fetch (MCP reference server) vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-kagi-search" }, { "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": 25, "edge": "bing-grounding", "kagi-search": 43, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bing-grounding": 68, "by": 3, "edge": "kagi-search", "kagi-search": 71, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "bing-grounding": 61, "by": 14, "edge": "kagi-search", "kagi-search": 75, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "bing-grounding": 79, "by": 15, "edge": "bing-grounding", "kagi-search": 64, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "bing-grounding": 20, "by": 0, "edge": "", "kagi-search": 20, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bing-grounding": 80, "by": 39, "edge": "bing-grounding", "kagi-search": 41, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "bing-grounding": 66, "by": 8, "edge": "kagi-search", "kagi-search": 74, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Grounding with Bing Search scores 63.7 (B) on agent readiness against Kagi Search API's 56.1 (C), and leads in 3 of 7 scored categories. Kagi Search API leads on agent ergonomics and transparency \u0026 trust. Both do web search. Kagi Search API is cheaper for web search, $12 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.", "kagi-search": "A public OpenAPI file, typed filters and API keys that can be limited by product and IP address make the API simple to call, at $12 per 1,000 searches. It is still a public preview, with no published rate limits and no free allowance, and the terms forbid storing results. Its status page logged only regional incidents since August." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search", "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.min.md" }, "markdown": "Grounding with Bing Search scores 63.7 (B) on agent readiness against Kagi Search API's 56.1 (C), and leads in 3 of 7 scored categories. Kagi Search API leads on agent ergonomics and transparency \u0026 trust. Both do web search. Kagi Search API is cheaper for web search, $12 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- Kagi Search API: grade C, 56.1/100, rank #841 of 1486. Markdown https://www.anchorterminal.com/tools/kagi-search.md · JSON https://www.anchorterminal.com/api/v1/tools/kagi-search.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 43\n- Security \u0026 auth, 79 against 64\n- Maintenance \u0026 community, 80 against 41\n\nWatch for: The Bing tools never return raw results to developers, only a model-written answer with citation links\n\n### Kagi Search API (C)\n\nGood for: An owner who already pays for Kagi and wants its ranking, lenses and domain rules inside an agent, with page text in the same call.\n\nAhead on:\n- Agent ergonomics, 75 against 61\n- Transparency \u0026 trust, 74 against 66\n\nAlso in its favour:\n- Cheaper for web search, $12 against $14 per 1,000 requests\n- Runs on your own machine\n\nWatch for: Public preview since 21 May 2026. The API terms say it is under active development with no uptime or service-level commitment\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Grounding with Bing Search +39\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- Kagi Search API (41): The last dated API change is the Extract API fix in the changelog post of 21 August 2026, 75 days before this check. The posts of 10 September and 16 October carry no API item (20). That is the only dated API entry in the 90 days from 6 August (0). The MCP server's repository gained commits on 27 and 28 October 2026 (compact JSON results, `readOnlyHint`, per-page extraction errors) and a version bump to 1.1.0 with no tag, so no release is shown; PyPI didn't resolve for us. A public changelog that credits user reports, developers@kagi.com, a Discord `#api` forum and GitHub discussions. We could not read the issue list, since the GitHub API answered 403 (9). Four generated clients last synced on 26 May 2026, Python tagged only as 1.0.0rc3, TypeScript not on npm on 9 October, and `kagimcp` tagged last as v0.1.5 (8 April 2026). We did not look the server up in the MCP registry (8). The Python client has a generated CI workflow and the MCP server has a lock file but no CI workflow (4). 20 + 0 + 9 + 8 + 4 = 41.\n\n### Reliability: Grounding with Bing Search +25\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- Kagi Search API (43): Status page at status.kagi.com (Instatus), found through a web search on 4 November, with a Kagi API group of nine regional components such as `[API] us-east4` and `[API] europe-west2`, and history back to 2025 (20). In the 90 days from 6 August its feed and incident list show `[API]` incidents on single regions only. us-central1 on 12 September (1 hour 3 minutes), 19 September, 12 October and 19 October (2 to 3 minutes each), europe-west2 on 19 October (1 minute) and 20 October (8 hours 11 minutes, the region taken out of the global load balancer), asia-east2 on 30 September (4 minutes), australia-southeast1 on 11 September (1 minute) and asia-southeast1 on 7 August (about a minute). Each hit one region of nine, so all read as partial and the record is minor incidents only (20). The six 'API outage' entries (10, 20 and 26 August, two on 14 October and 22 October, 5 to 21 minutes each) name the API component of the Kagi Assistant group, not the Search API, and the 27 September database maintenance had an announced window. No rate limit numbers are published. The terms say only that limits and quotas apply per plan (0). The OpenAPI file documents 429 as 'Rate limited or usage limit exhausted' with no `Retry-After` header or backoff guidance. The calls are read-only, and Kagi's own MCP server retries 429 and 5xx twice by default (3). The pricing page lists SLAs under Enterprise by quote, and the API terms say there is no uptime or service-level commitment unless agreed in writing (0). The OpenAPI file still describes a preview period (0). 20 + 20 + 0 + 3 + 0 + 0 = 43.\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- Kagi Search API (64): Several named keys an account, each limited to chosen products and optionally to IP addresses or ranges, revoked by deleting. The v1 key travels only in the `Authorization` header. No expiry or OAuth (27). The API only reads. Per-key product limits and a spending cap in USD narrow what a leaked key can do (16). Search and Extract return third-party page text, and we found no prompt-injection guidance in the reference, the docs or the MCP README (2). The portal shows use count and last-used time per key and requests and cost per day per API, and every response carries a trace ID. No per-call log (7). security.txt with a contact, a bug bounty with a safe harbour policy, and an independent audit by Illumant cited on the security page, whose date we did not read. No SOC 2 or ISO 27001 statement found. security.txt re-read on 4 November (12). 27 + 16 + 2 + 7 + 12 = 64.\n\n### Agent ergonomics: Kagi Search API +14\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- Kagi Search API (75): `limit` caps results, extraction of page text is opt-in, snippet length follows an account setting, and an experimental Markdown response format exists. The MCP server has two tools (22). `page` 1 to 10, `limit` 1 to 1,024, lens and `filters` for domains, keywords, file type, dates and region (20). Errors return a namespaced `code`, a message, the field `location` and a trace ID, but no code catalogue is published and the linked error pages are not live (12). Both operations are read-only, so a retry is safe, though the docs do not say so and failed-call billing is stated only for extraction. The released MCP server sets no read-only annotations. A commit of 27 October adds `readOnlyHint` to its source with an untagged 1.1.0 version bump, not yet shown as released (10). Only `query` is required and defaults are stated. Generated clients exist for Python, TypeScript, Go and Rust, installable from GitHub. `@kagi/api` returned 404 on npm on 9 October (11). 22 + 20 + 12 + 10 + 11 = 75.\n\n### Transparency \u0026 trust: Kagi Search API +8\n\n- Grounding with Bing Search (66): Closed service. The terms of use, updated November 2025, are separate from the Online Services terms and sit under the customer's Microsoft agreement (15 of 30). The docs and the terms agree that the Data Protection Addendum and the Product Terms' privacy and security terms don't apply, that Microsoft and the customer are independent controllers, and that the query and parameters leave the Azure compliance and geographic boundary. The terms defer storage and use of query data to the general Microsoft Privacy Statement and state no retention period (15 of 30). The Bing Search APIs retirement was announced on 16 May 2025 for 11 August 2025, under three months' notice, and the web search page marks the Deep Research tool deprecated with a replacement. Microsoft's lifecycle policy covers Azure services, but no deprecation terms for Grounding with Bing were found (10 of 20). Data location for Bing processing isn't stated, and no sub-processor list for it was found (5 of 20). 15 + 15 + 10 + 5 = 45.\n- Kagi Search API (74): Closed service with clear API terms dated 22 September 2026. The MCP server is MIT and the OpenAPI file states Apache-2.0 (18). The privacy policy's API section agrees with the API terms. Queries are not stored against the account, load balancer and VM logs are kept 7 days and sampled Sentry errors 90 days. The Data Processing Addendum both documents cite is not yet published (23). v0 is marked deprecated with no end date, and the terms promise reasonable notice of breaking changes only where practicable (5). The privacy page names the payment processors and Sentry, the FAQ names GCP as the hosting provider and the docs name search sources, but there is no subprocessor list and no data locations (8). 18 + 23 + 5 + 8 = 54.\n\n## Score by category\n\n| Category | Weight | Grounding with Bing Search | Kagi Search API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 68 | 43 | Grounding with Bing Search +25 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 71 | Kagi Search API +3 |\n| Agent ergonomics | 13% (16.2 this run) | 61 | 75 | Kagi Search API +14 |\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 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 41 | Grounding with Bing Search +39 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 74 | Kagi Search API +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.7 · B** | **56.1 · C** | |\n\n## Facts side by side\n\n| Fact | Grounding with Bing Search | Kagi Search API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft | Kagi |\n| Hosted endpoint | `https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses` | `https://kagi.com/api/v1/search` |\n| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for web search | $14 per 1,000 requests | $12 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 Kagi API Terms of Service. The MCP server is MIT and the OpenAPI file states Apache-2.0 |\n| Tools exposed | 3 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | 2026-11-02 | 2026-08-21 |\n| Terms last updated | 2025-11-01 | 2026-09-22 |\n| Privacy policy last updated | 2026-09-01 | no date given |\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 | yes |\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 | 535 stars |\n\n## How the scores have moved\n\n### Grounding with Bing Search\n\nNo score change since it was listed.\n\n### Kagi Search API\n\n- +7.4 on 4 November 2026 (D to C): new evidence\n- no change on 27 October 2026: checklist\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**Kagi Search API.** A public OpenAPI file, typed filters and API keys that can be limited by product and IP address make the API simple to call, at $12 per 1,000 searches. It is still a public preview, with no published rate limits and no free allowance, and the terms forbid storing results. Its status page logged only regional incidents since August.\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### Kagi Search API\n\n1. Send `POST https://kagi.com/api/v1/search` with a JSON body and `Authorization: Bearer \u003ckey\u003e`, as the OpenAPI file defines. Only `query` is required\n2. Set `limit` to cap results returned. In the mixed `search` workflow the MCP tool applies the cap to each result category separately\n3. Use `extract.count` (1 to 10) only when page text is needed. Extraction is billed at the Extract rate on top of the search\n4. Do not store results. The API terms allow only the transient caching an application needs, and require deletion on termination\n5. On 429 back off before retrying. The response covers both rate limiting and an exhausted usage limit, and no `Retry-After` header is documented. Check status.kagi.com for regional incidents\n\n## Questions\n\n### Which is better for AI agents, Grounding with Bing Search or Kagi Search API?\n\nGrounding with Bing Search scores 63.7 (B) on agent readiness against Kagi Search API's 56.1 (C), and leads in 3 of 7 scored categories. Kagi Search API leads on agent ergonomics and transparency \u0026 trust.\n\n### Which is cheaper for web search, Grounding with Bing Search or Kagi Search API?\n\nKagi Search API, at $12 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 Kagi Search API need an API key?\n\nGrounding with Bing Search uses an OAuth sign-in. Kagi Search API needs an API key.\n\n### Can an agent call Grounding with Bing Search and Kagi 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 Kagi Search API at https://kagi.com/api/v1/search.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bing-grounding\", \"b\": \"kagi-search\"}`. From a terminal: `anchor compare bing-grounding kagi-search`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bing-grounding.json and https://www.anchorterminal.com/api/v1/tools/kagi-search.json\n\n## Other comparisons with Grounding with Bing Search or Kagi 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 Kagi Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-kagi-search.md)\n- [Arcmira vs Grounding with Bing Search](https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding.md)\n- [Arcmira vs Kagi Search API](https://www.anchorterminal.com/compare/arcmira-vs-kagi-search.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 Linkup](https://www.anchorterminal.com/compare/bing-grounding-vs-linkup.md)\n- [Grounding with Bing Search vs Mojeek Web Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek.md)\n- [Grounding with Bing Search vs NewsCatcher](https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.md)\n- [Grounding with Bing Search vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.md)\n- [Grounding with Bing Search vs Perplexity Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.md)\n- [Grounding with Bing Search vs SearchAPI.io](https://www.anchorterminal.com/compare/bing-grounding-vs-searchapi-io.md)\n- [Grounding with Bing Search vs SerpApi](https://www.anchorterminal.com/compare/bing-grounding-vs-serpapi.md)\n- [Grounding with Bing Search vs Serper](https://www.anchorterminal.com/compare/bing-grounding-vs-serper.md)\n- [Grounding with Bing Search vs SERPHouse](https://www.anchorterminal.com/compare/bing-grounding-vs-serphouse.md)\n- [Grounding with Bing Search vs SerpKite](https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.md)\n- [Grounding with Bing Search vs SpecStream](https://www.anchorterminal.com/compare/bing-grounding-vs-specstream.md)\n- [Grounding with Bing Search vs Tavily API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-tavily-mcp.md)\n- [Grounding with Bing Search vs TinyFish Search](https://www.anchorterminal.com/compare/bing-grounding-vs-tinyfish-search.md)\n- [Grounding with Bing Search vs Valyu](https://www.anchorterminal.com/compare/bing-grounding-vs-valyu.md)\n- [Grounding with Bing Search vs You.com APIs](https://www.anchorterminal.com/compare/bing-grounding-vs-you-com-api.md)\n- [Brave Search API + MCP vs Kagi Search API](https://www.anchorterminal.com/compare/brave-search-mcp-vs-kagi-search.md)\n- [Cloudflare Web Search API vs Kagi Search API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-kagi-search.md)\n- [DeepSeek Search and Fetch API vs Kagi Search API](https://www.anchorterminal.com/compare/deepseek-search-api-vs-kagi-search.md)\n- [Exa API + MCP vs Kagi Search API](https://www.anchorterminal.com/compare/exa-mcp-vs-kagi-search.md)\n- [Firecrawl MCP vs Kagi Search API](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-kagi-search.md)\n- [Grep AI vs Kagi Search API](https://www.anchorterminal.com/compare/grep-ai-vs-kagi-search.md)\n- [Kagi Search API vs Linkup](https://www.anchorterminal.com/compare/kagi-search-vs-linkup.md)\n- [Kagi Search API vs Mojeek Web Search API](https://www.anchorterminal.com/compare/kagi-search-vs-mojeek.md)\n- [Kagi Search API vs NewsCatcher](https://www.anchorterminal.com/compare/kagi-search-vs-newscatcher.md)\n- [Kagi Search API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/kagi-search-vs-parallel-search-api.md)\n- [Kagi Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api.md)\n- [Kagi Search API vs SearchAPI.io](https://www.anchorterminal.com/compare/kagi-search-vs-searchapi-io.md)\n- [Kagi Search API vs SerpApi](https://www.anchorterminal.com/compare/kagi-search-vs-serpapi.md)\n- [Kagi Search API vs Serper](https://www.anchorterminal.com/compare/kagi-search-vs-serper.md)\n- [Kagi Search API vs SERPHouse](https://www.anchorterminal.com/compare/kagi-search-vs-serphouse.md)\n- [Kagi Search API vs SerpKite](https://www.anchorterminal.com/compare/kagi-search-vs-serpkite.md)\n- [Kagi Search API vs SpecStream](https://www.anchorterminal.com/compare/kagi-search-vs-specstream.md)\n- [Kagi Search API vs Tavily API + MCP](https://www.anchorterminal.com/compare/kagi-search-vs-tavily-mcp.md)\n- [Kagi Search API vs TinyFish Search](https://www.anchorterminal.com/compare/kagi-search-vs-tinyfish-search.md)\n- [Kagi Search API vs Valyu](https://www.anchorterminal.com/compare/kagi-search-vs-valyu.md)\n- [Kagi Search API vs You.com APIs](https://www.anchorterminal.com/compare/kagi-search-vs-you-com-api.md)\n- [Fetch (MCP reference server) vs Kagi Search API](https://www.anchorterminal.com/compare/fetch-reference-server-vs-kagi-search.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 Kagi Search API", "url": "" } ], "description": "Grounding with Bing Search scores 63.7 (B) to Kagi Search's 56.1 (C) for web search. Kagi Search is cheaper for web search, $12 against $14 per 1,000 requests. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grounding with Bing Search B 63.7", "Kagi Search API C 56.1", "scores" ], "h1": "Grounding with Bing Search vs Kagi Search API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bing-grounding-vs-kagi-search", "published": "2026-10-01", "section": "tools", "title": "Grounding with Bing Search vs Kagi Search for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search" }, "tokens": { "markdown": 6450, "slim": 3630 }, "version": 1 }