{ "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": "Linkup scores 68 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "linkup", "name": "Linkup", "vendor": "Linkup", "vendorUrl": "https://www.linkup.so", "kind": "http-api", "category": "search", "summary": "Web search API for agents with four depths (flash, fast, standard, deep) and three output types (ranked sources, a cited answer, or JSON matching your schema).", "url": "https://www.anchorterminal.com/tools/linkup", "markdownUrl": "https://www.anchorterminal.com/tools/linkup.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/linkup.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/linkup.json", "dns": "linkup.grade.anchorterminal.com", "repo": "https://github.com/LinkupPlatform/linkup-mcp-server", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.linkup.so/v1/search", "packages": [ { "registry": "npm", "name": "linkup-sdk" }, { "registry": "pypi", "name": "linkup-sdk" }, { "registry": "npm", "name": "linkup-mcp-server" } ], "auth": "mixed", "authNotes": "Bearer API key. x402 (USDC on Base) works without any key on `/v1/search` and `/v1/fetch`. The hosted MCP takes the key as a Bearer header or, in the documented one-click configs, as `?apiKey=` in the URL.", "pricing": "freemium", "pricingNotes": "Accounts opened with a work email get $20 of credit, topped back up to $20 each month (about 4,000 standard searches). Search $0.005 per call for flash, fast or standard with sources, $0.006 with a sourced answer or structured output, deep $0.05 or $0.055. Fetch $0.001 to $0.011 by mode and JavaScript rendering. Research $0.25 (S) to $2.50 (XL). Errors and empty results aren't charged. x402 is a flat $0.01 a request (https://www.linkup.so/pricing).", "priceSummary": "$0.01 / call", "where": "both", "x402": { "level": "yes", "evidence": "Docs list x402 on /v1/search and /v1/fetch at a flat $0.01 a request in USDC on Base with no account. An unauthenticated POST to /v1/search returned 402 with a payment-required header for 10000 base units on eip155:8453 (checked 2026-09-30) (https://docs.linkup.so/pages/documentation/platform/x402).", "endpoints": [ { "url": "https://api.linkup.so/v1/search", "priceUsd": 0.01, "network": "eip155:8453" }, { "url": "https://api.linkup.so/v1/fetch", "priceUsd": 0.01, "network": "eip155:8453" } ] }, "toolCount": 4, "popularity": { "githubStars": 29, "npmWeekly": 53872, "pypiWeekly": 84459, "asOf": "2026-09-30" }, "docsUrl": "https://docs.linkup.so", "llmsTxt": "https://docs.linkup.so/llms.txt", "openapi": "https://api.linkup.so/v1/openapi.json", "registryName": "so.linkup.mcp/linkup-mcp-server", "capabilities": [ "web.search", "web.fetch", "search.answer", "search.research", "web.extract", "search.images" ], "tags": [ "hosted", "freemium", "mcp", "llms-txt", "openapi", "x402", "python", "typescript", "async-jobs" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 68, "grade": "B", "agentReady": false, "rank": 297, "ranked": true, "rankOf": 1486, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 73, "payments": 80, "reliability": 70, "schema": 88, "security": 32, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "Per-call prices from $0.005, and no credit taken for errors, missing parameters or empty results. 429 covers both exhausted credit and rate limiting, with no `Retry-After`.", "bestFor": "Agents that want a cited answer or schema-shaped output from one search call at a fixed price, and for European buyers who want a French vendor with zero retention on request.", "strengths": [ "Per-call prices from $0.005, and no credit taken for errors, missing parameters or empty results", "x402 on /v1/search and /v1/fetch at $0.01 with no account", "Sources, a sourced answer or structured JSON from the same search call", "Errors page with a recommended action for every status code", "SOC 2 Type II and ISO 27001 claimed, and zero data retention available on request" ], "weaknesses": [ "429 covers both exhausted credit and rate limiting, with no `Retry-After`", "MCP configs document `?apiKey=` in the URL and an `apiKey=` argument for stdio", "10 queries a second per organisation by default", "No deprecation policy, and the changelog is dated by month with no entry since September 2026", "MCP tools carry no read-only or destructive annotations, and the server has no tests in CI" ], "agentNotes": [ "On 429, check the credit balance before backing off. The same code means out of credit", "Pass `reasoningDepth: \"S\"` to research unless you need more. The MCP default is L at $1.50", "Start with `depth=fast` and `outputType=searchResults`. Deep costs $0.05, ten times as much", "Send the key as an `Authorization: Bearer` header, not `?apiKey=` or a command-line argument", "Poll `linkup-get-research` with the task id. Research runs take minutes" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68 } ], "editorialScores": { "ergonomics": 76, "maintenance": 73, "payments": 80, "reliability": 70, "schema": 88, "security": 32, "transparency": 45 }, "provenanceScore": 77, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -G https://api.linkup.so/v1/search -H \"Authorization: Bearer $LINKUP_API_KEY\" \\\n --data-urlencode \"q=What is Microsoft's 2024 revenue?\" -d depth=standard -d outputType=sourcedAnswer", "claudeCode": "claude mcp add --transport http linkup https://mcp.linkup.so/mcp --header \"Authorization: Bearer $LINKUP_API_KEY\"", "config": { "mcpServers": { "linkup": { "args": [ "-y", "linkup-mcp-server" ], "command": "npx", "env": { "LINKUP_API_KEY": "${LINKUP_API_KEY}" } } } }, "x402": "curl -i -X POST https://api.linkup.so/v1/search -H 'content-type: application/json' \\\n -d '{\"q\":\"test\",\"depth\":\"standard\",\"outputType\":\"searchResults\"}'\n# 402 -\u003e sign USDC transfer (eip155:8453) -\u003e resend with payment-signature header" }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/linkup" }, "area": "web-data", "unitPrices": [ { "item": "Search, standard depth, sources", "unit": "1k-requests", "usd": 5, "note": "$0.005 a call, $0.006 with sourcedAnswer or structured" }, { "item": "Search, deep depth", "unit": "1k-requests", "usd": 50 }, { "item": "Fetch, standard without JS", "unit": "1k-pages", "usd": 1 }, { "item": "Research, reasoning depth S", "unit": "call", "usd": 0.25, "note": "M $0.50, L $1.50, XL $2.50" }, { "item": "x402 request", "unit": "call", "usd": 0.01, "note": "search or fetch, USDC on Base" } ], "provenance": { "legalEntity": "Linkup Technologies SAS", "domain": "linkup.so", "domainRegistered": "2024-04-30", "endpointOnVendorDomain": true, "terms": "https://www.linkup.so/terms-of-use", "privacy": "https://www.linkup.so/privacy-policy", "statusPage": "https://status.linkup.so", "changelog": "https://docs.linkup.so/pages/changelog", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Registration date from rdap.nic.so. The registry also records a re-registration on 2025-04-01" ], "score": 77 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/linkup.json", "live": { "slug": "linkup", "probe": { "target": "https://api.linkup.so/v1/search", "method": "get", "lastAt": "2026-11-07T18:20:35.469228496Z", "lastOk": true, "lastStatus": 404, "lastMs": 136, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 54, "p95ms24h": 135, "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": 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.linkup.so", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:00.068218251Z" }, "versions": [ { "registry": "github", "name": "LinkupPlatform/linkup-mcp-server", "version": "v3.4.0", "released": "2026-09-15", "seenAt": "2026-11-06T23:40:11.150279233Z" }, { "registry": "mcp-registry", "name": "so.linkup.mcp/linkup-mcp-server", "version": "0.0.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "linkup-mcp-server", "version": "3.4.0", "seenAt": "2026-11-06T23:40:09.383071473Z" }, { "registry": "npm", "name": "linkup-sdk", "version": "3.7.2", "seenAt": "2026-11-06T23:40:07.179433289Z" }, { "registry": "pypi", "name": "linkup-sdk", "version": "0.24.0", "released": "2026-10-22", "seenAt": "2026-11-06T23:40:09.181096963Z" } ], "githubStars": 29, "npmWeekly": 71303, "pypiWeekly": 131839, "securityTxt": { "url": "https://linkup.so/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:38.439698642Z" }, "llmsTxt": { "url": "https://docs.linkup.so/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:52.745699763Z" }, "domain": { "domain": "linkup.so", "checkedAt": "2026-11-01T14:16:42.858704018Z" }, "pages": [ { "url": "https://docs.linkup.so/pages/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:06:48.740505524Z", "changedAt": "2026-11-07T14:06:48.740505524Z", "fingerprint": "aabfbafe49bb" }, { "url": "https://www.linkup.so/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:30:50.981340041Z", "changedAt": "2026-10-03T15:38:53.686360467Z", "fingerprint": "190e16c16e4d" }, { "url": "https://www.linkup.so/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:30:53.184401232Z", "changedAt": "2026-10-03T15:38:55.83913627Z", "fingerprint": "7c5016bc9dd8" }, { "url": "https://www.linkup.so/terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:30:55.393208003Z", "changedAt": "2026-10-03T15:38:58.282868656Z", "fingerprint": "785d2335f5ea" } ], "mcpTools": { "url": "https://mcp.linkup.so/mcp", "checkedAt": "2026-11-07T01:45:44.972726897Z", "status": "error", "note": "initialize: MCP error -32603: Version negotiation failed: the server requires authorization (HTTP 401)", "changedAt": "2026-11-07T01:45:44.972726897Z" }, "github": { "repo": "linkupplatform/linkup-mcp-server", "checkedAt": "2026-11-02T09:00:56.9114257Z", "stars": 29, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-01T16:33:53Z", "openIssues": 4, "openPRs": 17, "issuesOpened90d": 3, "issuesClosed90d": 0, "prsMerged90d": 3, "ci": { "branch": "main", "runs": 22, "success": 16, "failure": 6, "other": 0, "latest": "success", "latestAt": "2026-10-01T14:18:18Z" }, "replies": { "sampled": 4, "unanswered": 4 } }, "updatedAt": "2026-11-07T18:20:35.469228496Z" } }, "edges": [ { "by": 60, "category": "payments", "leads": "linkup", "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": "x402 on Linkup's own /v1/search and /v1/fetch at a flat $0.01 in USDC on Base, not on research or extract, so partial (30). Per-call prices published without login (20). $20 of credit topped up monthly for work-email signups. The docs don't say whether a card is needed, so half credit (10). An agent can pay by x402 with no account (20)." }, "scores": { "a": 20, "b": 80 } }, { "by": 47, "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": "One Bearer key per organisation. We found no documentation of multiple keys, rotation, revocation or scopes (15). The MCP README documents `?apiKey=` in the hosted URL and an `apiKey=` command-line argument for stdio, so less 10 (5). Every action is a read, but the MCP server has no tool subsets (15). Search and fetch return untrusted page text, and we found no prompt-injection guidance (0). No per-call audit log found (0). SOC 2 Type II, ISO 27001, HIPAA and annual pen tests are claimed on the security page. No security.txt, no bug bounty, and contact@linkup.so is the only security contact (12)." }, "scores": { "a": 79, "b": 32 } }, { "by": 20, "category": "schema", "leads": "linkup", "name": "Schema \u0026 documentation", "reasons": { "a": "The tools are typed in the official SDKs (BingGroundingTool, BingCustomSearchPreviewTool, WebSearchTool) in Python, C#, JavaScript and Java, and the toolbox exposes web search as an MCP tool. No public OpenAPI description of the Responses tool types was confirmed from the pages read (10 of 25). Microsoft Learn serves each page as Markdown with `accept=text/markdown`, though learn.microsoft.com/llms.txt answers 404 (10). The pages say what each of four web grounding routes is for and when to choose it, when to use Custom Search instead, and not to ask the model to summarise a whole page (17 of 20). Parameters are typed with defaults and limits in prose, `count` 1 to 50 with default 5, freshness values and a date-range form, market and language formats, `search_context_size` low, medium or high (11 of 15). Examples in Python, C#, TypeScript, Java and REST with expected output, and troubleshooting tables for connection ID, authentication and 429 problems, but no error codes or bodies for the tools (10 of 15). Requests carry `api-version=v1` on the toolbox, SDK changelogs are dated and a monthly What's New page lists new articles, the latest for August 2026 (10 of 15). 10 + 10 + 17 + 11 + 10 + 10 = 68.", "b": "OpenAPI at api.linkup.so/v1/openapi.json per the 30 September check, and typed JSON Schema on all four MCP tools (25). llms.txt and Markdown pages (10). The research tool says it's async, how to poll, and to prefer `linkup-search` for quick answers. The search tool lists what to use it for but not when not to (17). Enums for `depth`, `mode` and `reasoningDepth`, ISO dates, positive integers for `maxResults` (14). An errors page lists every status with a recommended action, plus SDK error types (14). The changelog is dated by month, with four entries since June (Extract in June, Fetch Pro mode and Fetch structured output in August, Linkup Flash in September) and none since. Versioning is the /v1 path only (8)." }, "scores": { "a": 68, "b": 88 } }, { "by": 15, "category": "ergonomics", "leads": "linkup", "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": "Four tools, search, fetch, research and research polling, compact. Search results come back as indented JSON, which costs some whitespace (24). `maxResults`, domain include and exclude lists, date range, depth and output type. No result pagination (18). Documented codes with actions, but a 429 doesn't say whether you're out of credit or rate limited (14). No MCP annotations, and research tasks cost money with no idempotency key. Searches are safe to repeat (5). Only `query` is required and `depth` defaults to fast. Python and JavaScript SDKs (15)." }, "scores": { "a": 61, "b": 76 } }, { "by": 7, "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 newest release that changes code is 30 September 2026, Python linkup-sdk 0.23.1 (request deadline errors) and JavaScript linkup-sdk 3.7.1, 32 days before this check (20). Python 0.24.0 of 22 October drops Python 3.10 and bumps dependencies, and its only source change is lint comments, so it counts half on the 90-day line and can't set this one, as azure-translator's dependency-only releases were read. Python 0.19.1 to 0.23.1, JavaScript 3.4.0 to 3.7.1 and MCP server 3.4.0 fall in the 90 days to 1 November (20). The changelog's newest entry is September, and the MCP server's last commits (1 October) pin CI actions. We didn't read the GitHub issues (10). Registered as so.linkup.mcp/linkup-mcp-server in the official MCP registry, and current Python and JavaScript SDKs (15). The MCP server's CI lints and builds but runs no tests. Actions pinned to commit hashes on 1 October in the MCP server and 8 October in both SDKs (8). 20+20+10+15+8 = 73." }, "scores": { "a": 80, "b": 73 } }, { "by": 5, "category": "transparency", "leads": "bing-grounding", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service. The terms of use, updated November 2025, are separate from the Online Services terms and sit under the customer's Microsoft agreement (15 of 30). The docs and the terms agree that the Data Protection Addendum and the Product Terms' privacy and security terms don't apply, that Microsoft and the customer are independent controllers, and that the query and parameters leave the Azure compliance and geographic boundary. The terms defer storage and use of query data to the general Microsoft Privacy Statement and state no retention period (15 of 30). The Bing Search APIs retirement was announced on 16 May 2025 for 11 August 2025, under three months' notice, and the web search page marks the Deep Research tool deprecated with a replacement. Microsoft's lifecycle policy covers Azure services, but no deprecation terms for Grounding with Bing were found (10 of 20). Data location for Bing processing isn't stated, and no sub-processor list for it was found (5 of 20). 15 + 15 + 10 + 5 = 45.", "b": "The API is closed with published terms, and the MCP server is MIT (20). Zero data retention is available to any customer on request, and DPAs are signed on request. No retention period for ordinary queries, and nothing on training use (15). No deprecation policy or dated notices found (0). Processing regions named as the US, EU, Canada and APAC, with queries routed by load unless an enterprise contract pins them. No subprocessor list (10)." }, "scores": { "a": 66, "b": 61 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Microsoft", "b": "Linkup", "name": "Vendor" }, { "a": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses", "b": "https://api.linkup.so/v1/search", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "$14 per 1,000 requests", "b": "$5 per 1,000 requests", "name": "Price for web search" }, { "a": "no", "b": "yes, from $0.01/call", "name": "x402" }, { "a": "Proprietary service under the customer's Microsoft agreement and the separate Grounding with Bing terms of use, which exclude it from the Microsoft Data Protection Addendum", "b": "none", "name": "Licence" }, { "a": "3", "b": "4", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "so.linkup.mcp/linkup-mcp-server", "name": "MCP registry" }, { "a": "2026-11-02", "b": "2026-09-30", "name": "Last release" }, { "a": "2025-11-01", "b": "2025-08-01", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "2025-04-01", "name": "Privacy policy last updated" }, { "a": "yes", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "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": "29 stars, 54k npm/wk, 84k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "4/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Linkup scores 68 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Grounding with Bing Search or Linkup?" }, { "answer": "Linkup, at $5 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 Linkup?" }, { "answer": "Grounding with Bing Search uses an OAuth sign-in. Linkup takes an API key or an OAuth sign-in. An agent can also pay Linkup per call over x402, with no account.", "question": "Do Grounding with Bing Search and Linkup 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 Linkup at https://api.linkup.so/v1/search.", "question": "Can an agent call Grounding with Bing Search and Linkup without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 79 against 32", "Maintenance \u0026 community, 80 against 73", "Transparency \u0026 trust, 66 against 61" ], "also": null, "goodFor": "Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.", "slug": "bing-grounding", "watchFor": "The Bing tools never return raw results to developers, only a model-written answer with citation links" }, { "aheadOn": [ "Schema \u0026 documentation, 88 against 68", "Agent ergonomics, 76 against 61", "Payments \u0026 pricing, 80 against 20" ], "also": [ "Cheaper for web search, $5 against $14 per 1,000 requests", "An agent can pay per call over x402, with no account", "Runs on your own machine" ], "goodFor": "Agents that want a cited answer or schema-shaped output from one search call at a fixed price, and for European buyers who want a French vendor with zero retention on request.", "slug": "linkup", "watchFor": "429 covers both exhausted credit and rate limiting, with no `Retry-After`" } ], "history": { "bing-grounding": null, "linkup": [ { "causes": [ "time" ], "date": "2026-11-01", "delta": -0.9, "from": 68.9, "fromGrade": "B", "to": 68, "toGrade": "B" }, { "causes": [ "correction" ], "date": "2026-10-28", "delta": 0, "from": 68.9, "fromGrade": "B", "to": 68.9, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0, "from": 68.9, "fromGrade": "B", "to": 68.9, "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-linkup.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Linkup", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding.json", "title": "Arcmira vs Grounding with Bing Search", "url": "https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-brave-search-mcp.json", "title": "Grounding with Bing Search vs Brave Search API + MCP", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-brave-search-mcp" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search.json", "title": "Grounding with Bing Search vs Cloudflare Web Search API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.json", "title": "Grounding with Bing Search vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-exa-mcp.json", "title": "Grounding with Bing Search vs Exa API + MCP", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-exa-mcp" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-firecrawl-mcp.json", "title": "Grounding with Bing Search vs Firecrawl MCP", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-firecrawl-mcp" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.json", "title": "Grounding with Bing Search vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-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-linkup.json", "title": "Brave Search API + MCP vs Linkup", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-linkup.json", "title": "Cloudflare Web Search API vs Linkup", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-linkup.json", "title": "DeepSeek Search and Fetch API vs Linkup", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-linkup.json", "title": "Exa API + MCP vs Linkup", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-linkup.json", "title": "Firecrawl MCP vs Linkup", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-linkup" }, { "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/linkup-vs-mojeek.json", "title": "Linkup vs Mojeek Web Search API", "url": "https://www.anchorterminal.com/compare/linkup-vs-mojeek" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-newscatcher.json", "title": "Linkup vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/linkup-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-parallel-search-api.json", "title": "Linkup vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/linkup-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api.json", "title": "Linkup vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-searchapi-io.json", "title": "Linkup vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/linkup-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-serpapi.json", "title": "Linkup vs SerpApi", "url": "https://www.anchorterminal.com/compare/linkup-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-serper.json", "title": "Linkup vs Serper", "url": "https://www.anchorterminal.com/compare/linkup-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-serphouse.json", "title": "Linkup vs SERPHouse", "url": "https://www.anchorterminal.com/compare/linkup-vs-serphouse" }, { "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/linkup-vs-specstream.json", "title": "Linkup vs SpecStream", "url": "https://www.anchorterminal.com/compare/linkup-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-tavily-mcp.json", "title": "Linkup vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/linkup-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-tinyfish-search.json", "title": "Linkup vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/linkup-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-valyu.json", "title": "Linkup vs Valyu", "url": "https://www.anchorterminal.com/compare/linkup-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-you-com-api.json", "title": "Linkup vs You.com APIs", "url": "https://www.anchorterminal.com/compare/linkup-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-linkup.json", "title": "Arcmira vs Linkup", "url": "https://www.anchorterminal.com/compare/arcmira-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-linkup.json", "title": "Grep AI vs Linkup", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-linkup.json", "title": "Fetch (MCP reference server) vs Linkup", "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-linkup" }, { "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": 2, "edge": "linkup", "key": "reliability", "linkup": 70, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bing-grounding": 68, "by": 20, "edge": "linkup", "key": "schema", "linkup": 88, "name": "Schema \u0026 documentation", "weight": 13 }, { "bing-grounding": 61, "by": 15, "edge": "linkup", "key": "ergonomics", "linkup": 76, "name": "Agent ergonomics", "weight": 13 }, { "bing-grounding": 79, "by": 47, "edge": "bing-grounding", "key": "security", "linkup": 32, "name": "Security \u0026 auth", "weight": 14 }, { "bing-grounding": 20, "by": 60, "edge": "linkup", "key": "payments", "linkup": 80, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bing-grounding": 80, "by": 7, "edge": "bing-grounding", "key": "maintenance", "linkup": 73, "name": "Maintenance \u0026 community", "weight": 7 }, { "bing-grounding": 66, "by": 5, "edge": "bing-grounding", "key": "transparency", "linkup": 61, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Linkup scores 68 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do web search. Linkup is cheaper for web search, $5 against $14 per 1,000 requests. Linkup accepts x402. Grounding with Bing Search doesn't.", "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.", "linkup": "Per-call prices from $0.005, and no credit taken for errors, missing parameters or empty results. 429 covers both exhausted credit and rate limiting, with no `Retry-After`." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bing-grounding-vs-linkup", "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-linkup.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bing-grounding-vs-linkup.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bing-grounding-vs-linkup.min.md" }, "markdown": "Linkup scores 68 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. Both do web search. Linkup is cheaper for web search, $5 against $14 per 1,000 requests. Linkup accepts x402. Grounding with Bing Search doesn't.\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- Linkup: grade B, 68/100, rank #297 of 1486. Markdown https://www.anchorterminal.com/tools/linkup.md · JSON https://www.anchorterminal.com/api/v1/tools/linkup.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 32\n- Maintenance \u0026 community, 80 against 73\n- Transparency \u0026 trust, 66 against 61\n\nWatch for: The Bing tools never return raw results to developers, only a model-written answer with citation links\n\n### Linkup (B)\n\nGood for: Agents that want a cited answer or schema-shaped output from one search call at a fixed price, and for European buyers who want a French vendor with zero retention on request.\n\nAhead on:\n- Schema \u0026 documentation, 88 against 68\n- Agent ergonomics, 76 against 61\n- Payments \u0026 pricing, 80 against 20\n\nAlso in its favour:\n- Cheaper for web search, $5 against $14 per 1,000 requests\n- An agent can pay per call over x402, with no account\n- Runs on your own machine\n\nWatch for: 429 covers both exhausted credit and rate limiting, with no `Retry-After`\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Linkup +60\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- Linkup (80): x402 on Linkup's own /v1/search and /v1/fetch at a flat $0.01 in USDC on Base, not on research or extract, so partial (30). Per-call prices published without login (20). $20 of credit topped up monthly for work-email signups. The docs don't say whether a card is needed, so half credit (10). An agent can pay by x402 with no account (20).\n\n### Security \u0026 auth: Grounding with Bing Search +47\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- Linkup (32): One Bearer key per organisation. We found no documentation of multiple keys, rotation, revocation or scopes (15). The MCP README documents `?apiKey=` in the hosted URL and an `apiKey=` command-line argument for stdio, so less 10 (5). Every action is a read, but the MCP server has no tool subsets (15). Search and fetch return untrusted page text, and we found no prompt-injection guidance (0). No per-call audit log found (0). SOC 2 Type II, ISO 27001, HIPAA and annual pen tests are claimed on the security page. No security.txt, no bug bounty, and contact@linkup.so is the only security contact (12).\n\n### Schema \u0026 documentation: Linkup +20\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- Linkup (88): OpenAPI at api.linkup.so/v1/openapi.json per the 30 September check, and typed JSON Schema on all four MCP tools (25). llms.txt and Markdown pages (10). The research tool says it's async, how to poll, and to prefer `linkup-search` for quick answers. The search tool lists what to use it for but not when not to (17). Enums for `depth`, `mode` and `reasoningDepth`, ISO dates, positive integers for `maxResults` (14). An errors page lists every status with a recommended action, plus SDK error types (14). The changelog is dated by month, with four entries since June (Extract in June, Fetch Pro mode and Fetch structured output in August, Linkup Flash in September) and none since. Versioning is the /v1 path only (8).\n\n### Agent ergonomics: Linkup +15\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- Linkup (76): Four tools, search, fetch, research and research polling, compact. Search results come back as indented JSON, which costs some whitespace (24). `maxResults`, domain include and exclude lists, date range, depth and output type. No result pagination (18). Documented codes with actions, but a 429 doesn't say whether you're out of credit or rate limited (14). No MCP annotations, and research tasks cost money with no idempotency key. Searches are safe to repeat (5). Only `query` is required and `depth` defaults to fast. Python and JavaScript SDKs (15).\n\n### Maintenance \u0026 community: Grounding with Bing Search +7\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- Linkup (73): The newest release that changes code is 30 September 2026, Python linkup-sdk 0.23.1 (request deadline errors) and JavaScript linkup-sdk 3.7.1, 32 days before this check (20). Python 0.24.0 of 22 October drops Python 3.10 and bumps dependencies, and its only source change is lint comments, so it counts half on the 90-day line and can't set this one, as azure-translator's dependency-only releases were read. Python 0.19.1 to 0.23.1, JavaScript 3.4.0 to 3.7.1 and MCP server 3.4.0 fall in the 90 days to 1 November (20). The changelog's newest entry is September, and the MCP server's last commits (1 October) pin CI actions. We didn't read the GitHub issues (10). Registered as so.linkup.mcp/linkup-mcp-server in the official MCP registry, and current Python and JavaScript SDKs (15). The MCP server's CI lints and builds but runs no tests. Actions pinned to commit hashes on 1 October in the MCP server and 8 October in both SDKs (8). 20+20+10+15+8 = 73.\n\n### Transparency \u0026 trust: Grounding with Bing Search +5\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- Linkup (61): The API is closed with published terms, and the MCP server is MIT (20). Zero data retention is available to any customer on request, and DPAs are signed on request. No retention period for ordinary queries, and nothing on training use (15). No deprecation policy or dated notices found (0). Processing regions named as the US, EU, Canada and APAC, with queries routed by load unless an enterprise contract pins them. No subprocessor list (10).\n\n## Score by category\n\n| Category | Weight | Grounding with Bing Search | Linkup | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 68 | 70 | Linkup +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 88 | Linkup +20 |\n| Agent ergonomics | 13% (16.2 this run) | 61 | 76 | Linkup +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 32 | Grounding with Bing Search +47 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 80 | Linkup +60 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 73 | Grounding with Bing Search +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 61 | Grounding with Bing Search +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.7 · B** | **68 · B** | |\n\n## Facts side by side\n\n| Fact | Grounding with Bing Search | Linkup |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft | Linkup |\n| Hosted endpoint | `https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses` | `https://api.linkup.so/v1/search` |\n| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | OAuth | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| Price for web search | $14 per 1,000 requests | $5 per 1,000 requests |\n| x402 | no | yes, from $0.01/call |\n| Licence | Proprietary service under the customer's Microsoft agreement and the separate Grounding with Bing terms of use, which exclude it from the Microsoft Data Protection Addendum | none |\n| Tools exposed | 3 | 4 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `so.linkup.mcp/linkup-mcp-server` |\n| Last release | 2026-11-02 | 2026-09-30 |\n| Terms last updated | 2025-11-01 | 2025-08-01 |\n| Privacy policy last updated | 2026-09-01 | 2025-04-01 |\n| Customer content may train models | yes | yes |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | 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 | 29 stars, 54k npm/wk, 84k PyPI/wk |\n| Agent reviews | none | 4/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### Linkup\n\n- -0.9 on 1 November 2026: time\n- no change on 28 October 2026: correction\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**Linkup.** Per-call prices from $0.005, and no credit taken for errors, missing parameters or empty results. 429 covers both exhausted credit and rate limiting, with no `Retry-After`.\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### Linkup\n\n1. On 429, check the credit balance before backing off. The same code means out of credit\n2. Pass `reasoningDepth: \"S\"` to research unless you need more. The MCP default is L at $1.50\n3. Start with `depth=fast` and `outputType=searchResults`. Deep costs $0.05, ten times as much\n4. Send the key as an `Authorization: Bearer` header, not `?apiKey=` or a command-line argument\n5. Poll `linkup-get-research` with the task id. Research runs take minutes\n\n## Questions\n\n### Which is better for AI agents, Grounding with Bing Search or Linkup?\n\nLinkup scores 68 (B) on agent readiness against Grounding with Bing Search's 63.7 (B), and leads in 4 of 7 scored categories. Grounding with Bing Search leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.\n\n### Which is cheaper for web search, Grounding with Bing Search or Linkup?\n\nLinkup, at $5 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 Linkup need an API key?\n\nGrounding with Bing Search uses an OAuth sign-in. Linkup takes an API key or an OAuth sign-in. An agent can also pay Linkup per call over x402, with no account.\n\n### Can an agent call Grounding with Bing Search and Linkup 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 Linkup at https://api.linkup.so/v1/search.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bing-grounding-vs-linkup.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bing-grounding-vs-linkup.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bing-grounding\", \"b\": \"linkup\"}`. From a terminal: `anchor compare bing-grounding linkup`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bing-grounding.json and https://www.anchorterminal.com/api/v1/tools/linkup.json\n\n## Other comparisons with Grounding with Bing Search or Linkup\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 Linkup](https://www.anchorterminal.com/compare/agentcore-web-search-vs-linkup.md)\n- [Arcmira vs Grounding with Bing Search](https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding.md)\n- [Grounding with Bing Search vs Brave Search API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-brave-search-mcp.md)\n- [Grounding with Bing Search vs Cloudflare Web Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search.md)\n- [Grounding with Bing Search vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.md)\n- [Grounding with Bing Search vs Exa API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-exa-mcp.md)\n- [Grounding with Bing Search vs Firecrawl MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-firecrawl-mcp.md)\n- [Grounding with Bing Search vs Kagi Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.md)\n- [Grounding with Bing Search vs 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 Linkup](https://www.anchorterminal.com/compare/brave-search-mcp-vs-linkup.md)\n- [Cloudflare Web Search API vs Linkup](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-linkup.md)\n- [DeepSeek Search and Fetch API vs Linkup](https://www.anchorterminal.com/compare/deepseek-search-api-vs-linkup.md)\n- [Exa API + MCP vs Linkup](https://www.anchorterminal.com/compare/exa-mcp-vs-linkup.md)\n- [Firecrawl MCP vs Linkup](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-linkup.md)\n- [Kagi Search API vs Linkup](https://www.anchorterminal.com/compare/kagi-search-vs-linkup.md)\n- [Linkup vs Mojeek Web Search API](https://www.anchorterminal.com/compare/linkup-vs-mojeek.md)\n- [Linkup vs NewsCatcher](https://www.anchorterminal.com/compare/linkup-vs-newscatcher.md)\n- [Linkup vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/linkup-vs-parallel-search-api.md)\n- [Linkup vs Perplexity Search API](https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api.md)\n- [Linkup vs SearchAPI.io](https://www.anchorterminal.com/compare/linkup-vs-searchapi-io.md)\n- [Linkup vs SerpApi](https://www.anchorterminal.com/compare/linkup-vs-serpapi.md)\n- [Linkup vs Serper](https://www.anchorterminal.com/compare/linkup-vs-serper.md)\n- [Linkup vs SERPHouse](https://www.anchorterminal.com/compare/linkup-vs-serphouse.md)\n- [Linkup vs SerpKite](https://www.anchorterminal.com/compare/linkup-vs-serpkite.md)\n- [Linkup vs SpecStream](https://www.anchorterminal.com/compare/linkup-vs-specstream.md)\n- [Linkup vs Tavily API + MCP](https://www.anchorterminal.com/compare/linkup-vs-tavily-mcp.md)\n- [Linkup vs TinyFish Search](https://www.anchorterminal.com/compare/linkup-vs-tinyfish-search.md)\n- [Linkup vs Valyu](https://www.anchorterminal.com/compare/linkup-vs-valyu.md)\n- [Linkup vs You.com APIs](https://www.anchorterminal.com/compare/linkup-vs-you-com-api.md)\n- [Arcmira vs Linkup](https://www.anchorterminal.com/compare/arcmira-vs-linkup.md)\n- [Grep AI vs Linkup](https://www.anchorterminal.com/compare/grep-ai-vs-linkup.md)\n- [Fetch (MCP reference server) vs Linkup](https://www.anchorterminal.com/compare/fetch-reference-server-vs-linkup.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 Linkup", "url": "" } ], "description": "Linkup scores 68 (B) to Grounding with Bing Search's 63.7 (B) for web search. Linkup is cheaper for web search, $5 against $14 per 1,000 requests. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grounding with Bing Search B 63.7", "Linkup B 68", "scores" ], "h1": "Grounding with Bing Search vs Linkup", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bing-grounding-vs-linkup", "published": "2026-10-01", "section": "tools", "title": "Grounding with Bing Search vs Linkup for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-linkup" }, "tokens": { "markdown": 5950, "slim": 3380 }, "version": 1 }