{ "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": "SerpKite scores 67.6 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth.", "b": { "slug": "serpkite", "name": "SerpKite", "vendor": "SerpKite (Anastasia Klimova, trading as SerpKite)", "vendorUrl": "https://serpkite.com", "kind": "http-api", "category": "search", "summary": "Google SERP API for AI agents from SerpKite, a sole trader in Ontario. It returns Google results, other verticals and public AI assistant answers as JSON or Markdown, fetches pages, and runs a remote MCP server with 23 tools.", "url": "https://www.anchorterminal.com/tools/serpkite", "markdownUrl": "https://www.anchorterminal.com/tools/serpkite.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/serpkite.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/serpkite.json", "dns": "serpkite.grade.anchorterminal.com", "repo": "https://github.com/SerpKite/serpkite-mcp", "license": "Proprietary service under SerpKite's terms of service. The SDKs (TypeScript, Python, Go, LangChain, Vercel AI SDK) and the MCP connection repository on GitHub are MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.serpkite.com/v1/search", "packages": [ { "registry": "npm", "name": "serpkite" }, { "registry": "pypi", "name": "serpkite" }, { "registry": "go", "name": "github.com/serpkite/serpkite-go" } ], "auth": "api-key", "authNotes": "API key (`skt_live_…`) as `Authorization: Bearer` on every REST call and on the remote MCP server; since 9 October 2026 the bare key without `Bearer` is accepted too. GET requests may also send it as the `?api_key=` query parameter. An account can hold many keys, each revocable and rotatable with an optional monthly credit limit, and keys are stored as SHA-256 hashes. No scopes. Since 9 October the MCP server also supports OAuth (authorisation code with PKCE, dynamic client registration, rotating refresh tokens); an approved connection runs as a named API key and its token works on /v1/mcp only (https://serpkite.com/docs/mcp, https://serpkite.com/docs/changelog).", "pricing": "freemium", "pricingNotes": "Prepaid credit packs that never expire. Starter $10 for 10,000 credits ($1.00 per 1,000), Growth $50 for 62,500 ($0.80), Pro $300 for 500,000 ($0.60), volume quotes from $0.18 per 1,000 at 25 million a month. One credit is one page of 10 results; `num=100` is 7 credits, autocomplete 0.5, batch and cache hits half price, `include_content` 1 per fetched page, AI assistant answers 2 to 4 credits. Free credits with no card (1,000 on email verification, 1,500 more after linking GitHub or Google) and 1,000 a month, with a free daily limit of 500 credits; since 28 October free credits are paused for an account sharing a device or network with another. Batch depth requests move to per-page billing on 23 November 2026. Failed, empty and blocked requests are refunded. Paddle is the merchant of record (https://serpkite.com/pricing, checked 2026-11-02).", "priceSummary": "$1 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, the OpenAPI spec or the pricing page. Packs are bought through Paddle checkout (checked 2026-10-05).", "endpoints": [] }, "toolCount": 23, "popularity": { "githubStars": null, "npmWeekly": 809, "pypiWeekly": 376, "asOf": "2026-10-05" }, "docsUrl": "https://serpkite.com/docs", "llmsTxt": "https://serpkite.com/llms.txt", "openapi": "https://serpkite.com/openapi/serp-api.yaml", "registryName": "io.github.SerpKite/serpkite", "capabilities": [ "web.search", "search.serp", "search.news", "search.images", "web.fetch", "web.extract", "web.crawl" ], "tags": [ "hosted", "freemium", "no-card", "free-tier", "closed-source", "mcp", "openapi", "llms-txt", "typescript", "python", "go", "status-page" ], "lastRelease": "2026-11-01", "graded": true, "anchor": { "graded": true, "score": 67.6, "grade": "B", "agentReady": false, "rank": 313, "ranked": true, "rankOf": 1486, "categoryRank": 9, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 97, "maintenance": 80, "payments": 40, "reliability": 75, "schema": 90, "security": 37, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": -3, "negativeNotes": [ "2 October to 1 November 2026. The `ai_overview` parameter and field, the `/v1/ai-mode` endpoint and its MCP tool, and the `/v1/lens` endpoint were removed the day each removal was announced (2 and 3 October), three to four days after the v1.0.0 changelog listed AI Overview as unchanged, with Google's refusal of logged-out requests as the reason. Later same-day changes fold into this term, among them `/v1/reviews` answering 400 for sorts other than `most_relevant` and stopping at review 10 (16 October), and `page: 2` and later answering 503 instead of an empty result (1 November). AI Overview and AI Mode came back on 28 October. Folded into one small deduction, -3 (https://serpkite.com/docs/changelog)." ], "verdict": "Google SERP API with an OpenAPI 3.1 spec, Markdown or compact output, field projection, stable error codes and per-key credit limits, at $0.60 to $1.00 per 1,000 on packs that don't expire. The service launched on 29 September 2026 from a sole trader, with a month of status history and frequent same-day contract changes.", "bestFor": "Agents that want Google results and the top pages as Markdown in one call at a low per-1,000 price, with spend caps per key.", "strengths": [ "OpenAPI 3.1 spec, llms.txt, llms-full.txt and Markdown twins of every docs page", "`format=markdown` or `compact`, `fields` projection and an `X-Tokens-Estimate` header size responses for a model", "Many revocable keys per account, each with an optional monthly credit limit, plus an account spend cap and OAuth for the MCP server", "Credit packs never expire, and failed, empty and blocked requests are refunded", "Named subprocessors with locations, and a retention table that keeps no query text in logs" ], "weaknesses": [ "Launched 29 September 2026 by a sole trader, with status monitoring only since 2 October", "Contract changes forced by Google ship the day they are announced, including the first-week removals and the 16 October reviews limit", "GET requests accept the key as a `?api_key=` query parameter, and keys have no scopes", "No SLA for self-serve packs, no SOC 2 and no security.txt", "No prompt-injection guidance, though search, webpage, extract and crawl return third-party page text" ], "agentNotes": [ "Send the key as `Authorization: Bearer`, not `?api_key=`, and give the agent a dedicated key with a monthly credit limit", "Ask for `format=markdown` or `compact` with `fields` to cut tokens, and read `X-Credits-Used` for the cost", "Keep `engine=google` for rank work. Check `meta.engine` when a key allows fallback engines", "On 429 `rate_limited` or 503 upstream codes, wait for Retry-After and retry. `daily_limit_reached`, `account_restricted` (403) and 402 need a purchase", "Treat page Markdown from `include_content`, `webpage` and `extract` as untrusted text" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.6 } ], "editorialScores": { "ergonomics": 97, "maintenance": 80, "payments": 40, "reliability": 75, "schema": 90, "security": 37, "transparency": 79 }, "provenanceScore": 75, "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 serpkite", "http": "curl https://api.serpkite.com/v1/search \\\n -H \"Authorization: Bearer $SERPKITE_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"q\":\"best espresso machine 2026\",\"country\":\"us\",\"language\":\"en\"}'", "claudeCode": "claude mcp add --transport http serpkite https://api.serpkite.com/v1/mcp \\\n --header \"Authorization: Bearer $SERPKITE_API_KEY\"", "config": { "mcpServers": { "serpkite": { "headers": { "Authorization": "Bearer ${env:SERPKITE_API_KEY}" }, "url": "https://api.serpkite.com/v1/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/serpkite" }, "area": "web-data", "unitPrices": [ { "item": "Starter pack", "unit": "1k-requests", "usd": 1, "note": "$10 for 10,000 credits, never expires" }, { "item": "Pro pack", "unit": "1k-requests", "usd": 0.6, "note": "$300 for 500,000 credits, never expires" } ], "provenance": { "legalEntity": "Anastasia Klimova, trading as SerpKite", "domain": "serpkite.com", "domainRegistered": "2026-09-29", "endpointOnVendorDomain": true, "terms": "https://serpkite.com/legal/terms", "privacy": "https://serpkite.com/legal/privacy", "statusPage": "https://status.serpkite.com", "changelog": "https://serpkite.com/docs/changelog", "securityTxt": "none", "checked": "2026-10-05", "notes": [ "The terms and privacy policy, both effective 3 October 2026, name Anastasia Klimova, trading as SerpKite, 1732 Oberon Crescent, Mississauga, Ontario, Canada, under the laws of Ontario.", "RDAP for serpkite.com gives a registration date of 2026-09-29 and Cloudflare, Inc. as registrar.", "serpkite.com/.well-known/security.txt returns the site's 404 page. The security page asks for reports by email with acknowledgement in 2 business days and says there's no paid bug bounty.", "The MCP registry entry uses the GitHub namespace io.github.SerpKite, not a domain-verified one. The repository's two commits are by the GitHub user nolikzero, and the SDK repositories are committed by serpkite-bot \u003csupport@serpkite.com\u003e.", "The subprocessor page lists Polar as merchant of record for earlier orders, which suggests sales before the domain's registration date. We couldn't establish where." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/serpkite.json", "live": { "slug": "serpkite", "probe": { "target": "https://api.serpkite.com/v1/search", "method": "get", "lastAt": "2026-11-07T18:20:53.999602293Z", "lastOk": true, "lastStatus": 401, "lastMs": 151, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.89, "p50ms24h": 121, "p95ms24h": 224, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "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": 253 }, { "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": 253 }, { "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": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "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": 241 }, { "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 } ], "outages": [ { "start": "2026-11-03T10:35:09.387488166Z", "end": "2026-11-03T11:14:41.456082867Z", "note": "HTTP 530 server error" } ] }, "vendorStatus": { "page": "https://status.serpkite.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:44.554890116Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.github.SerpKite/serpkite", "version": "1.2.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "serpkite", "version": "0.10.0", "seenAt": "2026-11-07T00:04:57.782847958Z" }, { "registry": "pypi", "name": "serpkite", "version": "0.10.0", "released": "2026-11-05", "seenAt": "2026-11-07T00:05:00.89457909Z" } ], "githubStars": 0, "npmWeekly": 357, "pypiWeekly": 256, "securityTxt": { "url": "https://serpkite.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:24.466205734Z" }, "llmsTxt": { "url": "https://serpkite.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:54.27218306Z" }, "domain": { "domain": "serpkite.com", "registered": "2026-09-29", "source": "https://rdap.verisign.com/com/v1/domain/serpkite.com", "checkedAt": "2026-11-01T14:17:34.283329903Z" }, "pages": [ { "url": "https://serpkite.com/docs/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:19:38.565738874Z", "changedAt": "2026-11-07T14:19:38.565738874Z", "fingerprint": "d68c18d17704" }, { "url": "https://serpkite.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:19:44.67004402Z", "changedAt": "2026-11-07T14:19:44.67004402Z", "fingerprint": "0c82ab61c297" }, { "url": "https://serpkite.com/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:19:40.795779718Z", "changedAt": "2026-11-05T13:04:06.216389859Z", "fingerprint": "0eaf0bbbd031" }, { "url": "https://serpkite.com/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:19:42.771170665Z", "changedAt": "2026-11-05T13:04:07.812029176Z", "fingerprint": "693478e804e1" } ], "mcpTools": { "url": "https://api.serpkite.com/v1/mcp", "checkedAt": "2026-11-07T01:47:48.000876733Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:47:48.000876733Z" }, "github": { "repo": "serpkite/serpkite-mcp", "checkedAt": "2026-11-02T09:24:51.977048937Z", "stars": 0, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-28T22:42:28Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 5 }, "updatedAt": "2026-11-07T18:20:53.999602293Z" } }, "edges": [ { "by": 42, "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": "Many keys per account, each revocable and rotatable with an optional monthly credit limit, stored as SHA-256 hashes, with no scopes. Since 9 October the MCP server also takes OAuth (authorisation code with PKCE, dynamic client registration, rotating refresh tokens, one `mcp` scope), each connection running as a named, revocable API key, while REST still needs a key (20). The docs allow the key as `?api_key=` on GET requests (minus 10). Search is read-only, and per-key limits and an account spend cap bound cost, but there's no read-only key, and the MCP server exposes crawl alongside search with no confirmation step we could see (10). Results include third-party snippets and full page Markdown, and we found no prompt-injection guidance (0). The dashboard request log keeps per-call metadata (endpoint, status, credits, key) for 31 days with CSV export, and each key records who created it (12). security.txt returns 404. The security page has a disclosure policy with acknowledgement in 2 business days, no paid bug bounty and SOC 2 marked as not yet started (5)." }, "scores": { "a": 79, "b": 37 } }, { "by": 36, "category": "ergonomics", "leads": "serpkite", "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": "`format=markdown` or `compact`, `fields` projection, `num` and an `X-Tokens-Estimate` header size REST responses. The MCP server now has 23 tools with no toolsets or read-only subset we could find (22). `page`, `num` up to 100, country, language, location, time, domain include, exclude and boost, date bounds, `highlights` and `max_tokens` on extract (20). Stable error codes with a retry column, and errors are never billed (20). Searches are read-only, failed and empty calls are refunded, and batch creation takes `Idempotency-Key`. Since 9 October 2026 the changelog says every MCP tool carries `readOnlyHint`, `destructiveHint`, `idempotentHint` and `openWorldHint`, with all read-only except `crawl`, and on 2 November the MCP page says every tool is read-only except `crawl` and `research`, which start paid tasks, and none is destructive (20). Only `q` or `url` is required, and official SDKs exist for TypeScript, Python and Go with retries built in (15). 22+20+20+20+15 = 97." }, "scores": { "a": 61, "b": 97 } }, { "by": 22, "category": "schema", "leads": "serpkite", "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 3.1 spec (version 1.12.7 on 2 November 2026, 41 paths and 47 operations) at serpkite.com/openapi/serp-api.yaml (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Endpoint descriptions state purpose and when to use them, and the guides cover which tool to pick. The MCP tool definitions aren't public and `tools/list` needs a key, so we read the MCP docs table and the matching descriptions in the MIT AI SDK package, which state purpose and some when-to-use lines but not when not to (12). Typed parameters with 64 enums in the spec, documented ranges and strict validation that rejects unknown parameters with a 400 naming the replacement. We couldn't confirm the MCP JSON Schemas (13). curl, TypeScript, Python and Go examples on each page, and an errors page with 14 codes and what to do about each (15). Versioned `/v1` paths and a dated API changelog (15)." }, "scores": { "a": 68, "b": 90 } }, { "by": 20, "category": "payments", "leads": "serpkite", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). $14 per 1,000 transactions for Grounding with Bing Search and Custom Search, published on microsoft.com without a login (20). No free tier for Grounding with Bing, and an Azure subscription needs a card, as on the Azure Translator listing (0). A person signs up for Azure, creates a Foundry project and, for bing_grounding, a Bing resource (0).", "b": "No x402, MPP or L402 in llms.txt, the OpenAPI spec or the pricing page (0). Per-pack and per-credit prices published without a login, $1.00 to $0.60 per 1,000 (20). Free credits on signup and 1,000 a month with no card, per the quickstart and home page (20). A person signs in by email, GitHub or Google in a browser (0)." }, "scores": { "a": 20, "b": 40 } }, { "by": 11, "category": "transparency", "leads": "serpkite", "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 API under terms that name the operator, an Ontario address and governing law, with the SDKs and the MCP connection repository MIT (18). The privacy policy, DPA page, retention doc and security page agree that query text of successful requests isn't logged, usage metadata lasts 31 days and batch results 24 hours. On 26 October failed and empty requests began keeping their query for 24 hours, and the changelog says the privacy policy, terms and DPA were updated the same day (27). The terms promise 30 days' notice before removing an endpoint, with exceptions for changes forced by a third party. AI Overview, AI Mode and Lens were removed in the first week without notice under that exception, and the reviews limit of 16 October came the same way, while a batch price change for 23 November 2026 was announced ahead (14). Subprocessors named with purpose and location, including Contabo in Germany, Cloudflare, Paddle, Resend, PostHog EU and Better Stack, with 30 days' notice of changes (20)." }, "scores": { "a": 66, "b": 77 } }, { "by": 7, "category": "reliability", "leads": "serpkite", "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": "Hosted API, read with the hosted lines. Better Stack status page at status.serpkite.com with four monitors (api.serpkite.com/healthz, dashboard API, dashboard, website) and daily bars (20). Monitoring began on 2 October 2026, so the record covers 31 days of the 90 from 4 August. The page's own figures give 99.978 per cent uptime over 30 days for the API health monitor and 99.971 for the dashboard API, the 5 October check saw 29 to 41 minutes of downtime on each monitor on 2 October and 19 seconds on 3 October, and the feed has never carried an incident post. No outage reached an hour. A readable record shorter than 90 days with nothing major scores 15, as this run settled for short records. Rate limits published per key, 5 to 100 requests a second by pack (15). 429 `rate_limited` with Retry-After, backoff guidance for 429 and 503, and `Idempotency-Key` on batch creation (15). The terms say self-serve plans have no uptime guarantee and an enterprise SLA sits in a separate agreement we couldn't read (0). v1 API with no beta or preview label (10). 20+15+15+15+0+10 = 75." }, "scores": { "a": 68, "b": 75 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Microsoft", "b": "SerpKite (Anastasia Klimova, trading as SerpKite)", "name": "Vendor" }, { "a": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "b": "https://api.serpkite.com/v1/search", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "$14 per 1,000 requests", "b": "not published", "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 SerpKite's terms of service. The SDKs (TypeScript, Python, Go, LangChain, Vercel AI SDK) and the MCP connection repository on GitHub are MIT", "name": "Licence" }, { "a": "3", "b": "23", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.SerpKite/serpkite", "name": "MCP registry" }, { "a": "2026-11-02", "b": "2026-11-01", "name": "Last release" }, { "a": "2025-11-01", "b": "2026-10-03", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "2026-10-03", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "809 npm/wk, 376 PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "SerpKite scores 67.6 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth.", "question": "Which is better for AI agents, Grounding with Bing Search or SerpKite?" }, { "answer": "Grounding with Bing Search uses an OAuth sign-in. SerpKite needs an API key.", "question": "Do Grounding with Bing Search and SerpKite 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 SerpKite at https://api.serpkite.com/v1/search.", "question": "Can an agent call Grounding with Bing Search and SerpKite without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 79 against 37" ], "also": [ "No incidents deducted, where SerpKite loses 3 points for them" ], "goodFor": "Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.", "slug": "bing-grounding", "watchFor": "The Bing tools never return raw results to developers, only a model-written answer with citation links" }, { "aheadOn": [ "Reliability, 75 against 68", "Schema \u0026 documentation, 90 against 68", "Agent ergonomics, 97 against 61", "Payments \u0026 pricing, 40 against 20", "Transparency \u0026 trust, 77 against 66" ], "also": [ "Free to start without a card" ], "goodFor": "Agents that want Google results and the top pages as Markdown in one call at a low per-1,000 price, with spend caps per key.", "slug": "serpkite", "watchFor": "Launched 29 September 2026 by a sole trader, with status monitoring only since 2 October" } ], "history": { "bing-grounding": null, "serpkite": [ { "causes": [ "product", "time" ], "date": "2026-11-02", "delta": 2.8, "from": 64.8, "fromGrade": "B", "to": 67.6, "toGrade": "B" } ] }, "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-serpkite.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs SerpKite", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpkite" }, { "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-serpkite.json", "title": "Arcmira vs SerpKite", "url": "https://www.anchorterminal.com/compare/arcmira-vs-serpkite" }, { "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-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-serpkite.json", "title": "Brave Search API + MCP vs SerpKite", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-serpkite.json", "title": "Cloudflare Web Search API vs SerpKite", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpkite.json", "title": "DeepSeek Search and Fetch API vs SerpKite", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-serpkite.json", "title": "Exa API + MCP vs SerpKite", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-serpkite.json", "title": "Firecrawl MCP vs SerpKite", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-serpkite" }, { "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/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/linkup-vs-serpkite.json", "title": "Linkup vs SerpKite", "url": "https://www.anchorterminal.com/compare/linkup-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-serpkite.json", "title": "Mojeek Web Search API vs SerpKite", "url": "https://www.anchorterminal.com/compare/mojeek-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-serpkite.json", "title": "Parallel Search and Task APIs vs SerpKite", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite.json", "title": "Perplexity Search API vs SerpKite", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/searchapi-io-vs-serpkite.json", "title": "SearchAPI.io vs SerpKite", "url": "https://www.anchorterminal.com/compare/searchapi-io-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/serpapi-vs-serpkite.json", "title": "SerpApi vs SerpKite", "url": "https://www.anchorterminal.com/compare/serpapi-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/serper-vs-serpkite.json", "title": "Serper vs SerpKite", "url": "https://www.anchorterminal.com/compare/serper-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/serpkite-vs-specstream.json", "title": "SerpKite vs SpecStream", "url": "https://www.anchorterminal.com/compare/serpkite-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/serpkite-vs-tavily-mcp.json", "title": "SerpKite vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/serpkite-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/serpkite-vs-tinyfish-search.json", "title": "SerpKite vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/serpkite-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/serpkite-vs-valyu.json", "title": "SerpKite vs Valyu", "url": "https://www.anchorterminal.com/compare/serpkite-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/serpkite-vs-you-com-api.json", "title": "SerpKite vs You.com APIs", "url": "https://www.anchorterminal.com/compare/serpkite-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-serpkite.json", "title": "Fetch (MCP reference server) vs SerpKite", "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-serpkite.json", "title": "NewsCatcher vs SerpKite", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/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" }, { "json": "https://www.anchorterminal.com/compare/serphouse-vs-serpkite.json", "title": "SERPHouse vs SerpKite", "url": "https://www.anchorterminal.com/compare/serphouse-vs-serpkite" } ], "panel": null, "scores": [ { "bing-grounding": 68, "by": 7, "edge": "serpkite", "key": "reliability", "name": "Reliability", "serpkite": 75, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bing-grounding": 68, "by": 22, "edge": "serpkite", "key": "schema", "name": "Schema \u0026 documentation", "serpkite": 90, "weight": 13 }, { "bing-grounding": 61, "by": 36, "edge": "serpkite", "key": "ergonomics", "name": "Agent ergonomics", "serpkite": 97, "weight": 13 }, { "bing-grounding": 79, "by": 42, "edge": "bing-grounding", "key": "security", "name": "Security \u0026 auth", "serpkite": 37, "weight": 14 }, { "bing-grounding": 20, "by": 20, "edge": "serpkite", "key": "payments", "name": "Payments \u0026 pricing", "serpkite": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bing-grounding": 80, "by": 0, "edge": "", "key": "maintenance", "name": "Maintenance \u0026 community", "serpkite": 80, "weight": 7 }, { "bing-grounding": 66, "by": 11, "edge": "serpkite", "key": "transparency", "name": "Transparency \u0026 trust", "serpkite": 77, "weight": 7 } ], "summary": "SerpKite scores 67.6 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth. Both do web search.", "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.", "serpkite": "Google SERP API with an OpenAPI 3.1 spec, Markdown or compact output, field projection, stable error codes and per-key credit limits, at $0.60 to $1.00 per 1,000 on packs that don't expire. The service launched on 29 September 2026 from a sole trader, with a month of status history and frequent same-day contract changes." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite", "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.min.md" }, "markdown": "SerpKite scores 67.6 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth. Both do web search.\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- SerpKite: grade B, 67.6/100, rank #313 of 1486. Markdown https://www.anchorterminal.com/tools/serpkite.md · JSON https://www.anchorterminal.com/api/v1/tools/serpkite.json\n- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md\n- All 308 search comparisons: https://www.anchorterminal.com/compare/search/index.md\n\n## Which one, for what\n\n### Grounding with Bing Search (B)\n\nGood for: Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.\n\nAhead on:\n- Security \u0026 auth, 79 against 37\n\nAlso in its favour:\n- No incidents deducted, where SerpKite loses 3 points for them\n\nWatch for: The Bing tools never return raw results to developers, only a model-written answer with citation links\n\n### SerpKite (B)\n\nGood for: Agents that want Google results and the top pages as Markdown in one call at a low per-1,000 price, with spend caps per key.\n\nAhead on:\n- Reliability, 75 against 68\n- Schema \u0026 documentation, 90 against 68\n- Agent ergonomics, 97 against 61\n- Payments \u0026 pricing, 40 against 20\n- Transparency \u0026 trust, 77 against 66\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Launched 29 September 2026 by a sole trader, with status monitoring only since 2 October\n\n\n## Why the edge\n\n### Security \u0026 auth: Grounding with Bing Search +42\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- SerpKite (37): Many keys per account, each revocable and rotatable with an optional monthly credit limit, stored as SHA-256 hashes, with no scopes. Since 9 October the MCP server also takes OAuth (authorisation code with PKCE, dynamic client registration, rotating refresh tokens, one `mcp` scope), each connection running as a named, revocable API key, while REST still needs a key (20). The docs allow the key as `?api_key=` on GET requests (minus 10). Search is read-only, and per-key limits and an account spend cap bound cost, but there's no read-only key, and the MCP server exposes crawl alongside search with no confirmation step we could see (10). Results include third-party snippets and full page Markdown, and we found no prompt-injection guidance (0). The dashboard request log keeps per-call metadata (endpoint, status, credits, key) for 31 days with CSV export, and each key records who created it (12). security.txt returns 404. The security page has a disclosure policy with acknowledgement in 2 business days, no paid bug bounty and SOC 2 marked as not yet started (5).\n\n### Agent ergonomics: SerpKite +36\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- SerpKite (97): `format=markdown` or `compact`, `fields` projection, `num` and an `X-Tokens-Estimate` header size REST responses. The MCP server now has 23 tools with no toolsets or read-only subset we could find (22). `page`, `num` up to 100, country, language, location, time, domain include, exclude and boost, date bounds, `highlights` and `max_tokens` on extract (20). Stable error codes with a retry column, and errors are never billed (20). Searches are read-only, failed and empty calls are refunded, and batch creation takes `Idempotency-Key`. Since 9 October 2026 the changelog says every MCP tool carries `readOnlyHint`, `destructiveHint`, `idempotentHint` and `openWorldHint`, with all read-only except `crawl`, and on 2 November the MCP page says every tool is read-only except `crawl` and `research`, which start paid tasks, and none is destructive (20). Only `q` or `url` is required, and official SDKs exist for TypeScript, Python and Go with retries built in (15). 22+20+20+20+15 = 97.\n\n### Schema \u0026 documentation: SerpKite +22\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- SerpKite (90): Public OpenAPI 3.1 spec (version 1.12.7 on 2 November 2026, 41 paths and 47 operations) at serpkite.com/openapi/serp-api.yaml (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Endpoint descriptions state purpose and when to use them, and the guides cover which tool to pick. The MCP tool definitions aren't public and `tools/list` needs a key, so we read the MCP docs table and the matching descriptions in the MIT AI SDK package, which state purpose and some when-to-use lines but not when not to (12). Typed parameters with 64 enums in the spec, documented ranges and strict validation that rejects unknown parameters with a 400 naming the replacement. We couldn't confirm the MCP JSON Schemas (13). curl, TypeScript, Python and Go examples on each page, and an errors page with 14 codes and what to do about each (15). Versioned `/v1` paths and a dated API changelog (15).\n\n### Payments \u0026 pricing: SerpKite +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- SerpKite (40): No x402, MPP or L402 in llms.txt, the OpenAPI spec or the pricing page (0). Per-pack and per-credit prices published without a login, $1.00 to $0.60 per 1,000 (20). Free credits on signup and 1,000 a month with no card, per the quickstart and home page (20). A person signs in by email, GitHub or Google in a browser (0).\n\n### Transparency \u0026 trust: SerpKite +11\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- SerpKite (77): Closed API under terms that name the operator, an Ontario address and governing law, with the SDKs and the MCP connection repository MIT (18). The privacy policy, DPA page, retention doc and security page agree that query text of successful requests isn't logged, usage metadata lasts 31 days and batch results 24 hours. On 26 October failed and empty requests began keeping their query for 24 hours, and the changelog says the privacy policy, terms and DPA were updated the same day (27). The terms promise 30 days' notice before removing an endpoint, with exceptions for changes forced by a third party. AI Overview, AI Mode and Lens were removed in the first week without notice under that exception, and the reviews limit of 16 October came the same way, while a batch price change for 23 November 2026 was announced ahead (14). Subprocessors named with purpose and location, including Contabo in Germany, Cloudflare, Paddle, Resend, PostHog EU and Better Stack, with 30 days' notice of changes (20).\n\n### Reliability: SerpKite +7\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- SerpKite (75): Hosted API, read with the hosted lines. Better Stack status page at status.serpkite.com with four monitors (api.serpkite.com/healthz, dashboard API, dashboard, website) and daily bars (20). Monitoring began on 2 October 2026, so the record covers 31 days of the 90 from 4 August. The page's own figures give 99.978 per cent uptime over 30 days for the API health monitor and 99.971 for the dashboard API, the 5 October check saw 29 to 41 minutes of downtime on each monitor on 2 October and 19 seconds on 3 October, and the feed has never carried an incident post. No outage reached an hour. A readable record shorter than 90 days with nothing major scores 15, as this run settled for short records. Rate limits published per key, 5 to 100 requests a second by pack (15). 429 `rate_limited` with Retry-After, backoff guidance for 429 and 503, and `Idempotency-Key` on batch creation (15). The terms say self-serve plans have no uptime guarantee and an enterprise SLA sits in a separate agreement we couldn't read (0). v1 API with no beta or preview label (10). 20+15+15+15+0+10 = 75.\n\n## Score by category\n\n| Category | Weight | Grounding with Bing Search | SerpKite | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 68 | 75 | SerpKite +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 90 | SerpKite +22 |\n| Agent ergonomics | 13% (16.2 this run) | 61 | 97 | SerpKite +36 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 37 | Grounding with Bing Search +42 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | SerpKite +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 80 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 77 | SerpKite +11 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **63.7 · B** | **67.6 · B** | |\n\n## Facts side by side\n\n| Fact | Grounding with Bing Search | SerpKite |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft | SerpKite (Anastasia Klimova, trading as SerpKite) |\n| Hosted endpoint | `https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses` | `https://api.serpkite.com/v1/search` |\n| Transports | Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth | API key |\n| Pricing | Pay per use | Freemium |\n| Price for web search | $14 per 1,000 requests | not published |\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 SerpKite's terms of service. The SDKs (TypeScript, Python, Go, LangChain, Vercel AI SDK) and the MCP connection repository on GitHub are MIT |\n| Tools exposed | 3 | 23 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `io.github.SerpKite/serpkite` |\n| Last release | 2026-11-02 | 2026-11-01 |\n| Terms last updated | 2025-11-01 | 2026-10-03 |\n| Privacy policy last updated | 2026-09-01 | 2026-10-03 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | none | 809 npm/wk, 376 PyPI/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## How the scores have moved\n\n### Grounding with Bing Search\n\nNo score change since it was listed.\n\n### SerpKite\n\n- +2.8 on 2 November 2026: product, time\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**SerpKite.** Google SERP API with an OpenAPI 3.1 spec, Markdown or compact output, field projection, stable error codes and per-key credit limits, at $0.60 to $1.00 per 1,000 on packs that don't expire. The service launched on 29 September 2026 from a sole trader, with a month of status history and frequent same-day contract changes.\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### SerpKite\n\n1. Send the key as `Authorization: Bearer`, not `?api_key=`, and give the agent a dedicated key with a monthly credit limit\n2. Ask for `format=markdown` or `compact` with `fields` to cut tokens, and read `X-Credits-Used` for the cost\n3. Keep `engine=google` for rank work. Check `meta.engine` when a key allows fallback engines\n4. On 429 `rate_limited` or 503 upstream codes, wait for Retry-After and retry. `daily_limit_reached`, `account_restricted` (403) and 402 need a purchase\n5. Treat page Markdown from `include_content`, `webpage` and `extract` as untrusted text\n\n## Questions\n\n### Which is better for AI agents, Grounding with Bing Search or SerpKite?\n\nSerpKite scores 67.6 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth.\n\n### Do Grounding with Bing Search and SerpKite need an API key?\n\nGrounding with Bing Search uses an OAuth sign-in. SerpKite needs an API key.\n\n### Can an agent call Grounding with Bing Search and SerpKite 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 SerpKite at https://api.serpkite.com/v1/search.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bing-grounding\", \"b\": \"serpkite\"}`. From a terminal: `anchor compare bing-grounding serpkite`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bing-grounding.json and https://www.anchorterminal.com/api/v1/tools/serpkite.json\n\n## Other comparisons with Grounding with Bing Search or SerpKite\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 SerpKite](https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpkite.md)\n- [Arcmira vs Grounding with Bing Search](https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding.md)\n- [Arcmira vs SerpKite](https://www.anchorterminal.com/compare/arcmira-vs-serpkite.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 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 SerpKite](https://www.anchorterminal.com/compare/brave-search-mcp-vs-serpkite.md)\n- [Cloudflare Web Search API vs SerpKite](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-serpkite.md)\n- [DeepSeek Search and Fetch API vs SerpKite](https://www.anchorterminal.com/compare/deepseek-search-api-vs-serpkite.md)\n- [Exa API + MCP vs SerpKite](https://www.anchorterminal.com/compare/exa-mcp-vs-serpkite.md)\n- [Firecrawl MCP vs SerpKite](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-serpkite.md)\n- [Grep AI vs SerpKite](https://www.anchorterminal.com/compare/grep-ai-vs-serpkite.md)\n- [Kagi Search API vs SerpKite](https://www.anchorterminal.com/compare/kagi-search-vs-serpkite.md)\n- [Linkup vs SerpKite](https://www.anchorterminal.com/compare/linkup-vs-serpkite.md)\n- [Mojeek Web Search API vs SerpKite](https://www.anchorterminal.com/compare/mojeek-vs-serpkite.md)\n- [Parallel Search and Task APIs vs SerpKite](https://www.anchorterminal.com/compare/parallel-search-api-vs-serpkite.md)\n- [Perplexity Search API vs SerpKite](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite.md)\n- [SearchAPI.io vs SerpKite](https://www.anchorterminal.com/compare/searchapi-io-vs-serpkite.md)\n- [SerpApi vs SerpKite](https://www.anchorterminal.com/compare/serpapi-vs-serpkite.md)\n- [Serper vs SerpKite](https://www.anchorterminal.com/compare/serper-vs-serpkite.md)\n- [SerpKite vs SpecStream](https://www.anchorterminal.com/compare/serpkite-vs-specstream.md)\n- [SerpKite vs Tavily API + MCP](https://www.anchorterminal.com/compare/serpkite-vs-tavily-mcp.md)\n- [SerpKite vs TinyFish Search](https://www.anchorterminal.com/compare/serpkite-vs-tinyfish-search.md)\n- [SerpKite vs Valyu](https://www.anchorterminal.com/compare/serpkite-vs-valyu.md)\n- [SerpKite vs You.com APIs](https://www.anchorterminal.com/compare/serpkite-vs-you-com-api.md)\n- [Fetch (MCP reference server) vs SerpKite](https://www.anchorterminal.com/compare/fetch-reference-server-vs-serpkite.md)\n- [NewsCatcher vs SerpKite](https://www.anchorterminal.com/compare/newscatcher-vs-serpkite.md)\n- [Grounding with Bing Search vs Grep AI](https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai.md)\n- [SERPHouse vs SerpKite](https://www.anchorterminal.com/compare/serphouse-vs-serpkite.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 SerpKite", "url": "" } ], "description": "SerpKite scores 67.6 (B) to Grounding with Bing Search's 63.7 (B) for web search. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grounding with Bing Search B 63.7", "SerpKite B 67.6", "scores" ], "h1": "Grounding with Bing Search vs SerpKite", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bing-grounding-vs-serpkite", "published": "2026-10-01", "section": "tools", "title": "Grounding with Bing Search vs SerpKite for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite" }, "tokens": { "markdown": 6500, "slim": 3880 }, "version": 1 }