{
  "data": {
    "a": {
      "slug": "bing-grounding",
      "name": "Grounding with Bing Search",
      "vendor": "Microsoft",
      "vendorUrl": "https://www.microsoft.com/bing/apis",
      "company": "microsoft.com",
      "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": 64.9,
        "grade": "B",
        "agentReady": false,
        "rank": 561,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 18,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 61,
          "maintenance": 80,
          "payments": 30,
          "reliability": 68,
          "schema": 68,
          "security": 79,
          "transparency": 66
        },
        "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": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 64.9
          }
        ],
        "editorialScores": {
          "ergonomics": 61,
          "maintenance": 80,
          "payments": 30,
          "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",
          "lastMoved": "2026-11-13",
          "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-mcp-server-enterprise",
        "microsoft-decision-1",
        "microsoft-decision-1-1",
        "microsoft-advertising-api",
        "microsoft-excel-graph",
        "outlook-mail-graph",
        "microsoft-graph-people",
        "fara1-5-27b",
        "fara1-5-4b",
        "fara1-5-9b",
        "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-08T12:33:00.476652169Z",
          "lastOk": false,
          "lastStatus": 0,
          "lastMs": 0,
          "lastNote": "invalid character \"{\" in host name",
          "authRequired": false,
          "uptime24h": 0,
          "uptime30d": 0,
          "p50ms24h": 0,
          "p95ms24h": 0,
          "samples24h": 242,
          "samples30d": 383,
          "days": [
            {
              "date": "2026-11-06",
              "probes": 13,
              "ok": 0
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 0
            },
            {
              "date": "2026-11-08",
              "probes": 127,
              "ok": 0
            }
          ],
          "outages": [
            {
              "start": "2026-11-06T22:45:07.390416052Z",
              "end": "0001-01-01T00:00:00Z",
              "note": "invalid character \"{\" in host name"
            }
          ],
          "since": "0001-01-01T00:00:00Z"
        },
        "versions": [
          {
            "registry": "npm",
            "name": "@azure/ai-projects",
            "version": "2.11.0",
            "seenAt": "2026-11-18T17:32:39.746605778Z"
          },
          {
            "registry": "pypi",
            "name": "azure-ai-projects",
            "version": "2.11.0",
            "released": "2026-11-13",
            "seenAt": "2026-11-18T17:32:39.636976272Z"
          }
        ],
        "npmWeekly": 1311281,
        "pypiWeekly": 1934443,
        "securityTxt": {
          "url": "https://microsoft.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-10-27T16:00:00.000Z",
          "checkedAt": "2026-11-18T16:29:47.885824675Z"
        },
        "domain": {
          "domain": "microsoft.com",
          "registered": "1991-05-02",
          "source": "https://rdap.verisign.com/com/v1/domain/microsoft.com",
          "checkedAt": "2026-11-15T15:42:30.317222793Z"
        },
        "pages": [
          {
            "url": "https://www.microsoft.com/bing/apis/grounding-legal-enterprise",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T22:06:06.997830166Z",
            "changedAt": "2026-11-18T22:06:06.997830166Z",
            "fingerprint": "efb1188ded58"
          }
        ],
        "updatedAt": "2026-11-18T22:06:06.997830166Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "down": true,
        "last": {
          "kind": "outage",
          "date": "2026-11-06",
          "what": "invalid character \"{\" in host name"
        },
        "best": 0
      }
    },
    "answer": "Hyperresearch scores 68.1 (B) on agent readiness against Grounding with Bing Search's 64.9 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on reliability.",
    "b": {
      "slug": "hyperresearch",
      "name": "Hyperresearch",
      "vendor": "Hyperresearch",
      "vendorUrl": "https://hyperresearch.ai",
      "company": "hyperresearch.ai",
      "kind": "http-api",
      "category": "search",
      "summary": "Hyperresearch is a deep research API from Thalient Labs Inc. that turns a question into a cited, checked report, with a source vault, citation verification and per-call Answers search, through REST and two remote MCP servers.",
      "url": "https://www.anchorterminal.com/tools/hyperresearch",
      "markdownUrl": "https://www.anchorterminal.com/tools/hyperresearch.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/hyperresearch.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/hyperresearch.json",
      "dns": "hyperresearch.grade.anchorterminal.com",
      "repo": "https://github.com/jordan-gibbs/hyperresearch",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://answers.hyperresearch.ai/mcp",
      "packages": [
        {
          "registry": "pypi",
          "name": "hyperresearch"
        },
        {
          "registry": "pypi",
          "name": "langchain-hyperresearch"
        },
        {
          "registry": "npm",
          "name": "@hyperresearch/ai-sdk"
        },
        {
          "registry": "npm",
          "name": "@hyperresearch/langchain"
        }
      ],
      "auth": "mixed",
      "authNotes": "Self-serve scoped bearer keys (`hr_live_` billed, `hr_test_` free fixture mode) created in the console after a browser signup, with rotation, revocation and IP allowlists. MCP servers use OAuth with PKCE and a scope consent screen. A client that asks for no scopes gets read-only access.",
      "pricing": "usage",
      "pricingNotes": "Answers per call from a prepaid wallet: ask 2 cents (fast), 10 cents (standard, 20 when it digs deeper), 50 cents (max). Search 5 or 15 cents. Research runs flat: Light $9, Deep $49. $5 of Answers credit and one Light report free, no card. Top-ups from $10.",
      "priceSummary": "$0.02 / call",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in llms.txt, the pricing page, the Answers page or the docs (checked 2026-11-18). Payment is a Stripe wallet or monthly invoice.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://hyperresearch.ai/docs",
      "llmsTxt": "https://hyperresearch.ai/llms.txt",
      "openapi": "https://api.hyperresearch.ai/v1/openapi.json",
      "registryName": "ai.hyperresearch/answers",
      "capabilities": [
        "search.research",
        "search.answer",
        "web.search",
        "web.fetch"
      ],
      "tags": [
        "hosted",
        "remote-mcp",
        "mcp",
        "mcp-registry",
        "oauth",
        "api-key",
        "llms-txt",
        "openapi",
        "usage-priced",
        "prepaid",
        "no-card",
        "free-tier",
        "async-jobs",
        "webhooks",
        "python",
        "typescript",
        "beta",
        "no-status-page"
      ],
      "lastRelease": "2026-11-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 68.1,
        "grade": "B",
        "agentReady": false,
        "rank": 407,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 13,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 83,
          "maintenance": 88,
          "payments": 60,
          "reliability": 35,
          "schema": 76,
          "security": 79,
          "transparency": 71
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "Agents can buy one checked answer from 2 cents a call or a full research report for $9 or $49, with scoped, rotatable keys, stable error codes, idempotency keys and a six-month deprecation promise. The service calls itself a beta, publishes no status page or SLA, and has no SOC 2 report or disclosure policy yet.",
        "bestFor": "Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.",
        "strengths": [
          "Answers MCP prices are public per call: ask 2 cents (fast), 10 cents (standard), 50 cents (max), search 5 or 15 cents, with not-found calls charged less",
          "$5 of Answers credit and one free Light report on every account, no card needed. `hr_test_` keys run free fixture-mode runs",
          "Keys carry scopes (runs, vault, verify, mcp, admin), rotate with a 24-hour overlap and revoke at once. MCP uses OAuth with PKCE and a scope consent screen",
          "One error envelope with a stable `code`, `retryable` and `retry_after`, per-key rate limits by bucket, and `Idempotency-Key` on writes",
          "Fetched pages reach models inside `\u003cuntrusted-source\u003e` fences, with tool allowlists per role and private network ranges refused"
        ],
        "weaknesses": [
          "No status page, and the terms say there is no SLA and no uptime figure",
          "The terms call the service 'a beta from a young company'",
          "No SOC 2 report, no DPA on the shelf, no formal disclosure policy or bug bounty. Vulnerabilities go to the support address",
          "The research MCP server's tool schemas aren't published on a page we could read, and the OpenAPI host refused our reader",
          "Signup and MCP authorisation need a person in a browser. There is no machine payment protocol"
        ],
        "agentNotes": [
          "Use Answers (`data_and_web_answer` with mode `auto`) for one fact, and start a Light or Deep run only when the user wants a written report",
          "Send an `Idempotency-Key` on every write and reuse it only with an unchanged body, so a retried run or answer is charged once",
          "Poll a run with `GET /v1/runs/{id}` about once a minute, or stream its events. A Light run takes about 30 to 40 minutes",
          "If a response has `retryable: false`, change the request rather than retrying. Branch on `error.code`, never on the message",
          "Use a key that starts `hr_test_` to build and test an integration without spending"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 68.1
          }
        ],
        "editorialScores": {
          "ergonomics": 83,
          "maintenance": 88,
          "payments": 60,
          "reliability": 35,
          "schema": 76,
          "security": 79,
          "transparency": 84
        },
        "provenanceScore": 58,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -X POST https://api.hyperresearch.ai/v1/answers -H \"Authorization: Bearer $HYPERRESEARCH_KEY\" -H \"Idempotency-Key: $(uuidgen)\" -H 'Content-Type: application/json' -d '{\"question\":\"How old must a US senator be?\",\"mode\":\"fast\"}'",
        "claudeCode": "claude mcp add hyperresearch-answers --transport http https://answers.hyperresearch.ai/mcp",
        "config": {
          "mcpServers": {
            "hyperresearch": {
              "url": "https://mcp.hyperresearch.ai/mcp"
            },
            "hyperresearch-answers": {
              "url": "https://answers.hyperresearch.ai/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/search.research",
        "tool": "https://letme.dev/hyperresearch"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Answers ask, fast",
          "unit": "call",
          "usd": 0.02,
          "note": "1 to 2 cents if not found"
        },
        {
          "item": "Answers ask, standard",
          "unit": "call",
          "usd": 0.1,
          "note": "20 cents when it digs deeper"
        },
        {
          "item": "Answers ask, max",
          "unit": "call",
          "usd": 0.5,
          "note": "10 to 50 cents if not found"
        },
        {
          "item": "Answers search, standard",
          "unit": "call",
          "usd": 0.05
        },
        {
          "item": "Answers search, max",
          "unit": "call",
          "usd": 0.15
        },
        {
          "item": "Light research run",
          "unit": "tx",
          "usd": 9,
          "note": "one report"
        },
        {
          "item": "Deep research run",
          "unit": "tx",
          "usd": 49,
          "note": "one report"
        }
      ],
      "provenance": {
        "legalEntity": "Thalient Labs Inc.",
        "domain": "hyperresearch.ai",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://hyperresearch.ai/legal/terms",
        "privacy": "https://hyperresearch.ai/legal/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The about page names Thalient Labs Inc., a Delaware corporation incorporated on 16 March 2026, at 1001 S. Main St., Suite 500, Kalispell, MT 59901, and says the terms, privacy policy and Stripe receipts carry the same details. The terms choose Delaware law and have no arbitration clause.",
          "Terms version 1.7, effective 23 September 2026, last updated 4 October 2026. Privacy policy version 1.7, effective 17 September 2026, per the about page.",
          "hyperresearch.ai/robots.txt allows ClaudeBot, anthropic-ai and Claude-Web and disallows /api/, with Content-Signal search=yes, ai-input=yes, ai-train=yes. mcp. and answers.hyperresearch.ai publish comment-only robots files with no rules. api.hyperresearch.ai's robots.txt asked for a sign-in, so that host wasn't read.",
          "/.well-known/security.txt answers 404. No status page found.",
          "The about page asks directories to copy its product descriptions verbatim. We wrote our own."
        ],
        "score": 58
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/hyperresearch.json",
      "live": {
        "slug": "hyperresearch",
        "probe": {
          "target": "https://answers.hyperresearch.ai/mcp",
          "method": "get",
          "lastAt": "2026-11-18T22:43:33.50023008Z",
          "lastOk": true,
          "lastStatus": 406,
          "lastMs": 233,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 328,
          "p95ms24h": 813,
          "samples24h": 11,
          "samples30d": 11,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 11,
              "ok": 11
            }
          ],
          "since": "2026-11-18T21:38:05.612316973Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "ai.hyperresearch/answers",
            "version": "1.0.1",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.hyperresearch.ai/mcp",
          "checkedAt": "2026-10-01T21:59:49.591132636Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-10-01T21:59:49.591132636Z"
        },
        "updatedAt": "2026-11-18T22:45:57.054523297Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 33,
        "category": "reliability",
        "leads": "bing-grounding",
        "name": "Reliability",
        "reasons": {
          "a": "Graded on the hosted lines, for the Foundry Agent Service tools agents call. Azure status page with post-incident reviews and a Foundry Agent Service component (20). The history page read on 6 November lists one review in the 90 days from 8 August that names Foundry Agent Service, intermittent failures and latency in Sweden Central from 10:03 to 15:58 UTC on 29 September 2026. It was one region and partial, and the review doesn't name Grounding with Bing, so minor only, the reading the Azure Translator listing got for the same review (20). The pricing page publishes 150 transactions a second and 1 million a day for each Grounding with Bing resource (15). The web search troubleshooting table says to answer 429 with exponential backoff and retries. No Retry-After or tool-specific overload guidance was found, and searches have no side effects (8 of 15). No SLA naming Grounding with Bing was found. The terms make it a First Party Consumption Service apart from the Online Services terms, and the Online Services SLA document wasn't opened (0). Grounding with Bing Custom Search is marked preview and Grounding with Bing Search is not, but no page read states general availability for it or for the web_search tool, and the .NET SDK is in preview (5 of 10). 20 + 20 + 15 + 8 + 0 + 5 = 68.",
          "b": "Graded on the hosted API and the two remote MCP servers. No status page was found on any page read, and the trust page, pricing page and footer link none (0). No readable incident history (5). Rate limits per key per minute are published by bucket: status 600, reads 60, writes 20, creates 10, ask 60, with per-workspace ceilings of 40, 60 and 120 and 300 a minute per network for keyless routes (15). 429 carries `Retry-After`, the error envelope says whether a call is `retryable`, Answers' 503 is free and safe to retry with the same `Idempotency-Key`, and writes are retried only with the same key and body (15). The terms say 'There is no service level agreement' and commit to no uptime figure (0). The terms call the service 'a beta from a young company' (0). 0+5+15+15+0+0 = 35."
        },
        "scores": {
          "a": 68,
          "b": 35
        }
      },
      {
        "by": 30,
        "category": "payments",
        "leads": "hyperresearch",
        "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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.",
          "b": "No x402, MPP or L402 (0). Per-call prices for Answers and flat per-run prices (Light $9, Deep $49) are published without login, with rerun discounts and refund rules (30). $5 of Answers credit and the first Light report free on every account, no card needed, and `hr_test_` keys are never billed (30). A person signs up through Clerk in a browser and creates keys in the console, and MCP clients authorise in a browser (0). 0+30+30+0 = 60."
        },
        "scores": {
          "a": 30,
          "b": 60
        }
      },
      {
        "by": 22,
        "category": "ergonomics",
        "leads": "hyperresearch",
        "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": "Answers is three compact tools (`data_and_web_answer`, `data_and_web_search` and the free `get_pending_answer`), and an answer returns only a short answer, its quotes and links. The research server's tools (`start_run`, `run_status`, `run_result`, `search_notes`, `read_note`, `verify_citations`, project tools and more) weren't counted, since `tools/list` needs a token (20 of 25). `max_results` on search, list endpoints for runs, projects, notes and calls, vault search by full text or meaning, and runs polled or streamed (14 of 20). Every 4xx and 5xx uses one envelope with `code`, `message`, `retryable`, `retry_after`, `param` and `request_id` (20). `Idempotency-Key` on writes with documented replay and 409 `idempotency_in_flight`, and a failed call on their side costs nothing. MCP tool annotations weren't readable (14 of 20). Only a query and a tier are required to start a run. Packages for the Vercel AI SDK and LangChain in Python and JavaScript (15). 20+14+20+14+15 = 83."
        },
        "scores": {
          "a": 61,
          "b": 83
        }
      },
      {
        "by": 8,
        "category": "schema",
        "leads": "hyperresearch",
        "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": "llms.txt and the versioning page name an OpenAPI 3.1 document at api.hyperresearch.ai/v1/openapi.json, and the API reference has one page per operation generated from it. api.hyperresearch.ai's robots.txt asked for a sign-in, so read.py closed the host and the file wasn't read (20 of 25). llms.txt, and every docs page as Markdown with `.md` (10). The Answers page says when to use fast, standard, max or auto and that fast skips structured sources, and the docs say Answers is for one fact and runs for a report. The research MCP server's tool descriptions couldn't be read (12 of 20). Modes and run tiers are enums, and examples show `max_results`, but the schemas themselves weren't read (10 of 15). Request and result examples, one error envelope with status meanings and a stable `code` (14 of 15). The version is in the path (/v1) with an additive-only promise, but the hosted service has no public changelog. The open-source CLI's CHANGELOG.md is dated (10 of 15). 20+10+12+10+14+10 = 76."
        },
        "scores": {
          "a": 68,
          "b": 76
        }
      },
      {
        "by": 8,
        "category": "maintenance",
        "leads": "hyperresearch",
        "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 pricing and about pages were updated on 17 November 2026, and the open-source CLI that the hosted service runs was tagged v0.13.3 on 16 November (30). Four tagged CLI releases in the 90 days to this check: v0.13.0 (27 October), v0.13.1 (9 November), v0.13.2 (12 November), v0.13.3 (16 November) (20). The CLI changelog credits fixes to issues and pull requests from outside contributors (#71, #201 to #206). We didn't read the issue threads (15 of 25). `ai.hyperresearch/hyperresearch` and `ai.hyperresearch/answers` are in the official MCP registry under the vendor's domain namespace (15). The repository has CI and publish workflows, and AI SDK and LangChain packages are published (8 of 10). 30+20+15+15+8 = 88."
        },
        "scores": {
          "a": 80,
          "b": 88
        }
      },
      {
        "by": 5,
        "category": "transparency",
        "leads": "hyperresearch",
        "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 hosted service is closed with terms from Thalient Labs Inc. (version 1.7), and the CLI that runs the same pipeline is MIT (20 of 30). The trust page states retention per record type (content kept until deleted, verification inputs 7 days, billing at least 7 years, audit log 365 days by default), names the known gaps (the run index and questions are kept indefinitely, no automatic expiry), says customer content isn't used for training, and says it matches the privacy policy. No DPA on the shelf (26 of 30). A written deprecation policy: at least six months' notice, `Deprecation` and `Sunset` headers and a list of deprecations, plus 30 days' notice by email before a shutdown (20). Subprocessors are listed with what each receives and their countries, and the trust page says there is no data residency guarantee on Cloudflare's network (18 of 20). 20+26+20+18 = 84."
        },
        "scores": {
          "a": 66,
          "b": 71
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Microsoft",
        "b": "Hyperresearch",
        "name": "Vendor"
      },
      {
        "a": "https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses",
        "b": "https://answers.hyperresearch.ai/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "$14 per 1,000 requests",
        "b": "$0.05 per call",
        "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": "none",
        "name": "Licence"
      },
      {
        "a": "3",
        "b": "none",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "ai.hyperresearch/answers",
        "name": "MCP registry"
      },
      {
        "a": "2026-11-02",
        "b": "2026-11-16",
        "name": "Last release"
      },
      {
        "a": "2025-11-01",
        "b": "2026-11-17",
        "name": "Terms last updated"
      },
      {
        "a": "2026-09-01",
        "b": "2026-11-17",
        "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": "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"
      }
    ],
    "faq": [
      {
        "answer": "Hyperresearch scores 68.1 (B) on agent readiness against Grounding with Bing Search's 64.9 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on reliability.",
        "question": "Which is better for AI agents, Grounding with Bing Search or Hyperresearch?"
      },
      {
        "answer": "Grounding with Bing Search uses an OAuth sign-in. Hyperresearch takes an API key or an OAuth sign-in.",
        "question": "Do Grounding with Bing Search and Hyperresearch 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 Hyperresearch at https://answers.hyperresearch.ai/mcp.",
        "question": "Can an agent call Grounding with Bing Search and Hyperresearch without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 68 against 35"
        ],
        "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, 76 against 68",
          "Agent ergonomics, 83 against 61",
          "Payments \u0026 pricing, 60 against 30",
          "Maintenance \u0026 community, 88 against 80",
          "Transparency \u0026 trust, 71 against 66"
        ],
        "also": [
          "Free to start without a card"
        ],
        "goodFor": "Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.",
        "slug": "hyperresearch",
        "watchFor": "No status page, and the terms say there is no SLA and no uptime figure"
      }
    ],
    "history": {
      "bing-grounding": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.2,
          "from": 63.7,
          "fromGrade": "B",
          "to": 64.9,
          "toGrade": "B"
        }
      ],
      "hyperresearch": null
    },
    "job": {
      "capability": "web.search",
      "name": "Web search"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-bing-grounding.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Grounding with Bing Search",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-bing-grounding"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding.json",
        "title": "Arcmira vs Grounding with Bing Search",
        "url": "https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-brave-search-mcp.json",
        "title": "Grounding with Bing Search vs Brave Search API + MCP",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-brave-search-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search.json",
        "title": "Grounding with Bing Search vs Cloudflare Web Search API",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.json",
        "title": "Grounding with Bing Search vs DeepSeek Search and Fetch API",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-exa-mcp.json",
        "title": "Grounding with Bing Search vs Exa API + MCP",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-exa-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-firecrawl-mcp.json",
        "title": "Grounding with Bing Search vs Firecrawl MCP",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-firecrawl-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.json",
        "title": "Grounding with Bing Search vs Kagi Search API",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-linkup.json",
        "title": "Grounding with Bing Search vs Linkup",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-linkup"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek.json",
        "title": "Grounding with Bing Search vs Mojeek Web Search API",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.json",
        "title": "Grounding with Bing Search vs NewsCatcher",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.json",
        "title": "Grounding with Bing Search vs Parallel Search and Task APIs",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.json",
        "title": "Grounding with Bing Search vs Perplexity Search API",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-searchapi-io.json",
        "title": "Grounding with Bing Search vs SearchAPI.io",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-searchapi-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpapi.json",
        "title": "Grounding with Bing Search vs SerpApi",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serper.json",
        "title": "Grounding with Bing Search vs Serper",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serper"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serphouse.json",
        "title": "Grounding with Bing Search vs SERPHouse",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serphouse"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.json",
        "title": "Grounding with Bing Search vs SerpKite",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-specstream.json",
        "title": "Grounding with Bing Search vs SpecStream",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-specstream"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-tavily-mcp.json",
        "title": "Grounding with Bing Search vs Tavily API + MCP",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-tavily-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-tinyfish-search.json",
        "title": "Grounding with Bing Search vs TinyFish Search",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-tinyfish-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-valyu.json",
        "title": "Grounding with Bing Search vs Valyu",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-valyu"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-you-com-api.json",
        "title": "Grounding with Bing Search vs You.com APIs",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-you-com-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-hyperresearch.json",
        "title": "Brave Search API + MCP vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch.json",
        "title": "Cloudflare Web Search API vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch.json",
        "title": "DeepSeek Search and Fetch API vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch.json",
        "title": "Exa API + MCP vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch.json",
        "title": "Firecrawl MCP vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-kagi-search.json",
        "title": "Hyperresearch vs Kagi Search API",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-kagi-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek.json",
        "title": "Hyperresearch vs Mojeek Web Search API",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-searchapi-io.json",
        "title": "Hyperresearch vs SearchAPI.io",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-searchapi-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpapi.json",
        "title": "Hyperresearch vs SerpApi",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serper.json",
        "title": "Hyperresearch vs Serper",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serper"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serphouse.json",
        "title": "Hyperresearch vs SERPHouse",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serphouse"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpkite.json",
        "title": "Hyperresearch vs SerpKite",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpkite"
      },
      {
        "json": "https://www.anchorterminal.com/compare/arcmira-vs-hyperresearch.json",
        "title": "Arcmira vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/arcmira-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/grep-ai-vs-hyperresearch.json",
        "title": "Grep AI vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/grep-ai-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp.json",
        "title": "Hyperresearch vs Liner Search MCP",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-linkup.json",
        "title": "Hyperresearch vs Linkup",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-linkup"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-newscatcher.json",
        "title": "Hyperresearch vs NewsCatcher",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-newscatcher"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-parallel-search-api.json",
        "title": "Hyperresearch vs Parallel Search and Task APIs",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-parallel-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-perplexity-search-api.json",
        "title": "Hyperresearch vs Perplexity Search API",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-perplexity-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-specstream.json",
        "title": "Hyperresearch vs SpecStream",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-specstream"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-tavily-mcp.json",
        "title": "Hyperresearch vs Tavily API + MCP",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-tavily-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-tinyfish-search.json",
        "title": "Hyperresearch vs TinyFish Search",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-tinyfish-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-valyu.json",
        "title": "Hyperresearch vs Valyu",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-valyu"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-you-com-api.json",
        "title": "Hyperresearch vs You.com APIs",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-you-com-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch.json",
        "title": "Fetch (MCP reference server) vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch"
      },
      {
        "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/bing-grounding-vs-liner-mcp.json",
        "title": "Grounding with Bing Search vs Liner Search MCP",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-liner-mcp"
      }
    ],
    "panel": null,
    "scores": [
      {
        "bing-grounding": 68,
        "by": 33,
        "edge": "bing-grounding",
        "hyperresearch": 35,
        "key": "reliability",
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "bing-grounding": 68,
        "by": 8,
        "edge": "hyperresearch",
        "hyperresearch": 76,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "bing-grounding": 61,
        "by": 22,
        "edge": "hyperresearch",
        "hyperresearch": 83,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "bing-grounding": 79,
        "by": 0,
        "edge": "",
        "hyperresearch": 79,
        "key": "security",
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "bing-grounding": 30,
        "by": 30,
        "edge": "hyperresearch",
        "hyperresearch": 60,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "bing-grounding": 80,
        "by": 8,
        "edge": "hyperresearch",
        "hyperresearch": 88,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "bing-grounding": 66,
        "by": 5,
        "edge": "hyperresearch",
        "hyperresearch": 71,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Hyperresearch scores 68.1 (B) on agent readiness against Grounding with Bing Search's 64.9 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on reliability. 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.",
      "hyperresearch": "Agents can buy one checked answer from 2 cents a call or a full research report for $9 or $49, with scoped, rotatable keys, stable error codes, idempotency keys and a six-month deprecation promise. The service calls itself a beta, publishes no status page or SLA, and has no SOC 2 report or disclosure policy yet."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch",
    "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.min.md"
  },
  "markdown": "Hyperresearch scores 68.1 (B) on agent readiness against Grounding with Bing Search's 64.9 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on reliability. Both do web search.\n\n- Grounding with Bing Search: grade B, 64.9/100, rank #561 of 1557. Markdown https://www.anchorterminal.com/tools/bing-grounding.md · JSON https://www.anchorterminal.com/api/v1/tools/bing-grounding.json\n- Hyperresearch: grade B, 68.1/100, rank #407 of 1557. Markdown https://www.anchorterminal.com/tools/hyperresearch.md · JSON https://www.anchorterminal.com/api/v1/tools/hyperresearch.json\n- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md\n- All 353 search comparisons: https://www.anchorterminal.com/compare/search/index.md\n\n## Which one, for what\n\n### Grounding with Bing Search (B)\n\nGood for: Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.\n\nAhead on:\n- Reliability, 68 against 35\n\nWatch for: The Bing tools never return raw results to developers, only a model-written answer with citation links\n\n### Hyperresearch (B)\n\nGood for: Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.\n\nAhead on:\n- Schema \u0026 documentation, 76 against 68\n- Agent ergonomics, 83 against 61\n- Payments \u0026 pricing, 60 against 30\n- Maintenance \u0026 community, 88 against 80\n- Transparency \u0026 trust, 71 against 66\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No status page, and the terms say there is no SLA and no uptime figure\n\n\n## Why the edge\n\n### Reliability: Grounding with Bing Search +33\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- Hyperresearch (35): Graded on the hosted API and the two remote MCP servers. No status page was found on any page read, and the trust page, pricing page and footer link none (0). No readable incident history (5). Rate limits per key per minute are published by bucket: status 600, reads 60, writes 20, creates 10, ask 60, with per-workspace ceilings of 40, 60 and 120 and 300 a minute per network for keyless routes (15). 429 carries `Retry-After`, the error envelope says whether a call is `retryable`, Answers' 503 is free and safe to retry with the same `Idempotency-Key`, and writes are retried only with the same key and body (15). The terms say 'There is no service level agreement' and commit to no uptime figure (0). The terms call the service 'a beta from a young company' (0). 0+5+15+15+0+0 = 35.\n\n### Payments \u0026 pricing: Hyperresearch +30\n\n- Grounding with Bing Search (30): 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). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.\n- Hyperresearch (60): No x402, MPP or L402 (0). Per-call prices for Answers and flat per-run prices (Light $9, Deep $49) are published without login, with rerun discounts and refund rules (30). $5 of Answers credit and the first Light report free on every account, no card needed, and `hr_test_` keys are never billed (30). A person signs up through Clerk in a browser and creates keys in the console, and MCP clients authorise in a browser (0). 0+30+30+0 = 60.\n\n### Agent ergonomics: Hyperresearch +22\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- Hyperresearch (83): Answers is three compact tools (`data_and_web_answer`, `data_and_web_search` and the free `get_pending_answer`), and an answer returns only a short answer, its quotes and links. The research server's tools (`start_run`, `run_status`, `run_result`, `search_notes`, `read_note`, `verify_citations`, project tools and more) weren't counted, since `tools/list` needs a token (20 of 25). `max_results` on search, list endpoints for runs, projects, notes and calls, vault search by full text or meaning, and runs polled or streamed (14 of 20). Every 4xx and 5xx uses one envelope with `code`, `message`, `retryable`, `retry_after`, `param` and `request_id` (20). `Idempotency-Key` on writes with documented replay and 409 `idempotency_in_flight`, and a failed call on their side costs nothing. MCP tool annotations weren't readable (14 of 20). Only a query and a tier are required to start a run. Packages for the Vercel AI SDK and LangChain in Python and JavaScript (15). 20+14+20+14+15 = 83.\n\n### Schema \u0026 documentation: Hyperresearch +8\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- Hyperresearch (76): llms.txt and the versioning page name an OpenAPI 3.1 document at api.hyperresearch.ai/v1/openapi.json, and the API reference has one page per operation generated from it. api.hyperresearch.ai's robots.txt asked for a sign-in, so read.py closed the host and the file wasn't read (20 of 25). llms.txt, and every docs page as Markdown with `.md` (10). The Answers page says when to use fast, standard, max or auto and that fast skips structured sources, and the docs say Answers is for one fact and runs for a report. The research MCP server's tool descriptions couldn't be read (12 of 20). Modes and run tiers are enums, and examples show `max_results`, but the schemas themselves weren't read (10 of 15). Request and result examples, one error envelope with status meanings and a stable `code` (14 of 15). The version is in the path (/v1) with an additive-only promise, but the hosted service has no public changelog. The open-source CLI's CHANGELOG.md is dated (10 of 15). 20+10+12+10+14+10 = 76.\n\n### Maintenance \u0026 community: Hyperresearch +8\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- Hyperresearch (88): The pricing and about pages were updated on 17 November 2026, and the open-source CLI that the hosted service runs was tagged v0.13.3 on 16 November (30). Four tagged CLI releases in the 90 days to this check: v0.13.0 (27 October), v0.13.1 (9 November), v0.13.2 (12 November), v0.13.3 (16 November) (20). The CLI changelog credits fixes to issues and pull requests from outside contributors (#71, #201 to #206). We didn't read the issue threads (15 of 25). `ai.hyperresearch/hyperresearch` and `ai.hyperresearch/answers` are in the official MCP registry under the vendor's domain namespace (15). The repository has CI and publish workflows, and AI SDK and LangChain packages are published (8 of 10). 30+20+15+15+8 = 88.\n\n### Transparency \u0026 trust: Hyperresearch +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- Hyperresearch (71): The hosted service is closed with terms from Thalient Labs Inc. (version 1.7), and the CLI that runs the same pipeline is MIT (20 of 30). The trust page states retention per record type (content kept until deleted, verification inputs 7 days, billing at least 7 years, audit log 365 days by default), names the known gaps (the run index and questions are kept indefinitely, no automatic expiry), says customer content isn't used for training, and says it matches the privacy policy. No DPA on the shelf (26 of 30). A written deprecation policy: at least six months' notice, `Deprecation` and `Sunset` headers and a list of deprecations, plus 30 days' notice by email before a shutdown (20). Subprocessors are listed with what each receives and their countries, and the trust page says there is no data residency guarantee on Cloudflare's network (18 of 20). 20+26+20+18 = 84.\n\n## Score by category\n\n| Category | Weight | Grounding with Bing Search | Hyperresearch | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 68 | 35 | Grounding with Bing Search +33 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 68 | 76 | Hyperresearch +8 |\n| Agent ergonomics | 13% | 61 | 83 | Hyperresearch +22 |\n| Security \u0026 auth | 14% | 79 | 79 | even |\n| Payments \u0026 pricing | 10% | 30 | 60 | Hyperresearch +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 80 | 88 | Hyperresearch +8 |\n| Transparency \u0026 trust | 7% | 66 | 71 | Hyperresearch +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **64.9 · B** | **68.1 · B** | |\n\n## Facts side by side\n\n| Fact | Grounding with Bing Search | Hyperresearch |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft | Hyperresearch |\n| Hosted endpoint | `https://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responses` | `https://answers.hyperresearch.ai/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for web search | $14 per 1,000 requests | $0.05 per call |\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 | none |\n| Tools exposed | 3 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `ai.hyperresearch/answers` |\n| Last release | 2026-11-02 | 2026-11-16 |\n| Terms last updated | 2025-11-01 | 2026-11-17 |\n| Privacy policy last updated | 2026-09-01 | 2026-11-17 |\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 | 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\n## How the scores have moved\n\n### Grounding with Bing Search\n\n- +1.2 on 13 November 2026: checklist\n\n### Hyperresearch\n\nNo score change since it was listed.\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**Hyperresearch.** Agents can buy one checked answer from 2 cents a call or a full research report for $9 or $49, with scoped, rotatable keys, stable error codes, idempotency keys and a six-month deprecation promise. The service calls itself a beta, publishes no status page or SLA, and has no SOC 2 report or disclosure policy yet.\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### Hyperresearch\n\n1. Use Answers (`data_and_web_answer` with mode `auto`) for one fact, and start a Light or Deep run only when the user wants a written report\n2. Send an `Idempotency-Key` on every write and reuse it only with an unchanged body, so a retried run or answer is charged once\n3. Poll a run with `GET /v1/runs/{id}` about once a minute, or stream its events. A Light run takes about 30 to 40 minutes\n4. If a response has `retryable: false`, change the request rather than retrying. Branch on `error.code`, never on the message\n5. Use a key that starts `hr_test_` to build and test an integration without spending\n\n## Questions\n\n### Which is better for AI agents, Grounding with Bing Search or Hyperresearch?\n\nHyperresearch scores 68.1 (B) on agent readiness against Grounding with Bing Search's 64.9 (B), and leads in 5 of 7 scored categories. Grounding with Bing Search leads on reliability.\n\n### Do Grounding with Bing Search and Hyperresearch need an API key?\n\nGrounding with Bing Search uses an OAuth sign-in. Hyperresearch takes an API key or an OAuth sign-in.\n\n### Can an agent call Grounding with Bing Search and Hyperresearch 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 Hyperresearch at https://answers.hyperresearch.ai/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bing-grounding\", \"b\": \"hyperresearch\"}`. From a terminal: `anchor compare bing-grounding hyperresearch`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bing-grounding.json and https://www.anchorterminal.com/api/v1/tools/hyperresearch.json\n\n## Other comparisons with Grounding with Bing Search or Hyperresearch\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 Hyperresearch](https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.md)\n- [Arcmira vs Grounding with Bing Search](https://www.anchorterminal.com/compare/arcmira-vs-bing-grounding.md)\n- [Grounding with Bing Search vs Brave Search API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-brave-search-mcp.md)\n- [Grounding with Bing Search vs Cloudflare Web Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-cloudflare-web-search.md)\n- [Grounding with Bing Search vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/bing-grounding-vs-deepseek-search-api.md)\n- [Grounding with Bing Search vs Exa API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-exa-mcp.md)\n- [Grounding with Bing Search vs Firecrawl MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-firecrawl-mcp.md)\n- [Grounding with Bing Search vs Kagi Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-kagi-search.md)\n- [Grounding with Bing Search vs Linkup](https://www.anchorterminal.com/compare/bing-grounding-vs-linkup.md)\n- [Grounding with Bing Search vs Mojeek Web Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-mojeek.md)\n- [Grounding with Bing Search vs NewsCatcher](https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.md)\n- [Grounding with Bing Search vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.md)\n- [Grounding with Bing Search vs Perplexity Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.md)\n- [Grounding with Bing Search vs SearchAPI.io](https://www.anchorterminal.com/compare/bing-grounding-vs-searchapi-io.md)\n- [Grounding with Bing Search vs SerpApi](https://www.anchorterminal.com/compare/bing-grounding-vs-serpapi.md)\n- [Grounding with Bing Search vs Serper](https://www.anchorterminal.com/compare/bing-grounding-vs-serper.md)\n- [Grounding with Bing Search vs SERPHouse](https://www.anchorterminal.com/compare/bing-grounding-vs-serphouse.md)\n- [Grounding with Bing Search vs SerpKite](https://www.anchorterminal.com/compare/bing-grounding-vs-serpkite.md)\n- [Grounding with Bing Search vs SpecStream](https://www.anchorterminal.com/compare/bing-grounding-vs-specstream.md)\n- [Grounding with Bing Search vs Tavily API + MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-tavily-mcp.md)\n- [Grounding with Bing Search vs TinyFish Search](https://www.anchorterminal.com/compare/bing-grounding-vs-tinyfish-search.md)\n- [Grounding with Bing Search vs Valyu](https://www.anchorterminal.com/compare/bing-grounding-vs-valyu.md)\n- [Grounding with Bing Search vs You.com APIs](https://www.anchorterminal.com/compare/bing-grounding-vs-you-com-api.md)\n- [Brave Search API + MCP vs Hyperresearch](https://www.anchorterminal.com/compare/brave-search-mcp-vs-hyperresearch.md)\n- [Cloudflare Web Search API vs Hyperresearch](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch.md)\n- [DeepSeek Search and Fetch API vs Hyperresearch](https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch.md)\n- [Exa API + MCP vs Hyperresearch](https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch.md)\n- [Firecrawl MCP vs Hyperresearch](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch.md)\n- [Hyperresearch vs Kagi Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-kagi-search.md)\n- [Hyperresearch vs Mojeek Web Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek.md)\n- [Hyperresearch vs SearchAPI.io](https://www.anchorterminal.com/compare/hyperresearch-vs-searchapi-io.md)\n- [Hyperresearch vs SerpApi](https://www.anchorterminal.com/compare/hyperresearch-vs-serpapi.md)\n- [Hyperresearch vs Serper](https://www.anchorterminal.com/compare/hyperresearch-vs-serper.md)\n- [Hyperresearch vs SERPHouse](https://www.anchorterminal.com/compare/hyperresearch-vs-serphouse.md)\n- [Hyperresearch vs SerpKite](https://www.anchorterminal.com/compare/hyperresearch-vs-serpkite.md)\n- [Arcmira vs Hyperresearch](https://www.anchorterminal.com/compare/arcmira-vs-hyperresearch.md)\n- [Grep AI vs Hyperresearch](https://www.anchorterminal.com/compare/grep-ai-vs-hyperresearch.md)\n- [Hyperresearch vs Liner Search MCP](https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp.md)\n- [Hyperresearch vs Linkup](https://www.anchorterminal.com/compare/hyperresearch-vs-linkup.md)\n- [Hyperresearch vs NewsCatcher](https://www.anchorterminal.com/compare/hyperresearch-vs-newscatcher.md)\n- [Hyperresearch vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/hyperresearch-vs-parallel-search-api.md)\n- [Hyperresearch vs Perplexity Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-perplexity-search-api.md)\n- [Hyperresearch vs SpecStream](https://www.anchorterminal.com/compare/hyperresearch-vs-specstream.md)\n- [Hyperresearch vs Tavily API + MCP](https://www.anchorterminal.com/compare/hyperresearch-vs-tavily-mcp.md)\n- [Hyperresearch vs TinyFish Search](https://www.anchorterminal.com/compare/hyperresearch-vs-tinyfish-search.md)\n- [Hyperresearch vs Valyu](https://www.anchorterminal.com/compare/hyperresearch-vs-valyu.md)\n- [Hyperresearch vs You.com APIs](https://www.anchorterminal.com/compare/hyperresearch-vs-you-com-api.md)\n- [Fetch (MCP reference server) vs Hyperresearch](https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch.md)\n- [Grounding with Bing Search vs Grep AI](https://www.anchorterminal.com/compare/bing-grounding-vs-grep-ai.md)\n- [Grounding with Bing Search vs Liner Search MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-liner-mcp.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-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "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 Hyperresearch",
        "url": ""
      }
    ],
    "description": "Hyperresearch scores 68.1 (B) to Grounding with Bing Search's 64.9 (B) for web search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Grounding with Bing Search B 64.9",
      "Hyperresearch B 68.1",
      "scores"
    ],
    "h1": "Grounding with Bing Search vs Hyperresearch",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/bing-grounding-vs-hyperresearch",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Grounding with Bing Search vs Hyperresearch for AI agents (2026)",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch"
  },
  "tokens": {
    "markdown": 6350,
    "slim": 1130
  },
  "version": 1
}
