Head to head · Web search · October 2026 research run

Grounding with Bing Search vs Hyperresearch

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.

Best web search APIs for AI agents · All 353 search comparisons

Which one, for what

Grounding with Bing Search B

Best for Teams already building on Foundry Agent Service who want cited answers from Bing without handling a search key.

Ahead on

  • Reliability, 68 against 35

Watch for

The Bing tools never return raw results to developers, only a model-written answer with citation links

Hyperresearch B

Best for Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.

Ahead on

  • Schema & documentation, 76 against 68
  • Agent ergonomics, 83 against 61
  • Payments & pricing, 60 against 30
  • Maintenance & community, 88 against 80
  • Transparency & trust, 71 against 66

Also in its favour

  • Free to start without a card

Watch for

No status page, and the terms say there is no SLA and no uptime figure

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Grounding with Bing Search +33

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.

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.

Payments & pricing Hyperresearch +30

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.

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.

Agent ergonomics Hyperresearch +22

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.

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.

Schema & documentation Hyperresearch +8

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.

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.

Maintenance & community Hyperresearch +8

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&A 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.

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.

Transparency & trust Hyperresearch +5

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.

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.

Score by category

CategoryWeightGrounding with Bing SearchHyperresearchEdge
Reliability16%6835Grounding with Bing Search +33
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6876Hyperresearch +8
Agent ergonomics13%6183Hyperresearch +22
Security & auth14%7979even
Payments & pricing10%3060Hyperresearch +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8088Hyperresearch +8
Transparency & trust7%6671Hyperresearch +5
Negative events≤1500
TotalB 64.9/100B 68.1/100

Facts side by side

FactGrounding with Bing SearchHyperresearch
KindHTTP APIHTTP API
VendorMicrosoftHyperresearch
Hosted endpointhttps://{account}.services.ai.azure.com/api/projects/{project}/openai/v1/responseshttps://answers.hyperresearch.ai/mcp
TransportsStreamable HTTPStreamable HTTP
AuthOAuthOAuth or key
PricingPay per usePay per use
Price for web search$14 per 1,000 requests$0.05 per call
x402nono
LicenceProprietary service under the customer's Microsoft agreement and the separate Grounding with Bing terms of use, which exclude it from the Microsoft Data Protection Addendumnone
Tools exposed3none
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedai.hyperresearch/answers
Last release2026-11-022026-11-16
Terms last updated2025-11-012026-11-17
Privacy policy last updated2026-09-012026-11-17
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text

How the scores have moved

Verdicts

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.

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.

Before you call either

Grounding with Bing Search

  1. 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
  2. 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
  3. Treat cited page text as untrusted input and don't put secrets or personal data in prompts, since queries leave the Azure compliance boundary
  4. On 429 back off exponentially; no Retry-After header is documented for the tool

Hyperresearch

  1. 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
  2. Send an Idempotency-Key on every write and reuse it only with an unchanged body, so a retried run or answer is charged once
  3. 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
  4. If a response has retryable: false, change the request rather than retrying. Branch on error.code, never on the message
  5. Use a key that starts hr_test_ to build and test an integration without spending

Questions

Which is better for AI agents, Grounding with Bing Search or Hyperresearch?

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.

Do Grounding with Bing Search and Hyperresearch need an API key?

Grounding with Bing Search uses an OAuth sign-in. Hyperresearch takes an API key or an OAuth sign-in.

Can an agent call Grounding with Bing Search and Hyperresearch without installing anything?

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.

Other comparisons with Grounding with Bing Search or Hyperresearch

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.