Head to head · Web search · October 2026 research run

Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch

Web Search Tool on Amazon Bedrock AgentCore scores 77.1 (BB) on agent readiness against Hyperresearch's 68.1 (B), and leads in 4 of 7 scored categories. Hyperresearch leads on agent ergonomics, payments & pricing and maintenance & community. Both do web search.

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

Which one, for what

Web Search Tool on Amazon Bedrock AgentCore BB

Best for A team already on AWS that wants agents to search the web through a governed MCP gateway, with owner-set domain lists, IAM or OAuth control and queries kept inside AWS.

Ahead on

  • Reliability, 90 against 35
  • Security & auth, 85 against 79
  • Transparency & trust, 77 against 71

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No error responses for the tool are documented. The only response example has isError false

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

  • Agent ergonomics, 83 against 75
  • Payments & pricing, 60 against 45
  • Maintenance & community, 88 against 80

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 Web Search Tool on Amazon Bedrock AgentCore +55

Web Search Tool on Amazon Bedrock AgentCore 90

Graded on the hosted lines, for the Gateway endpoint and the connector agents call. AWS Health Dashboard with per-service, per-Region history (20). The dashboard's history file, re-read on 1 November 2026, names AgentCore in one event in the 90 days from 3 August, 2 hours 40 minutes of packet loss in one zone of eu-south-2 on 4 October 2026, marked informational and in a Region where Web Search is not sold. The us-west-2 events of 3 September and 30 October (API Gateway HTTP API) don't name AgentCore. Read as clean, as on the Memory listing (30). Quotas published and re-read on 1 November, 10 Web Search requests a second and 200 tool calls a second per gateway and per account (15). Owner-set gateway rate limits return an error body with retryAfter in seconds and searches have no side effects, but the response to the service's own Web Search quota is not documented (10 of 15). The AgentCore FAQ says the Amazon Bedrock SLA applies, but that SLA, last updated 4 October 2023, does not name AgentCore (5 of 10, as on the Code Interpreter listing). Generally available since 16 June 2026 (10).

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 +15

Web Search Tool on Amazon Bedrock AgentCore 45

No x402, MPP or L402 on the Gateway or the tool. AgentCore payments is a separate component for an agent paying third parties (0). Per-query price published without a login, $7.00 per 1,000, with a worked example that adds Gateway invocations at $0.005 per 1,000 (20). No Web Search allowance, but new AWS accounts get up to $200 in Free Tier credits and the Free Tier FAQ says most new customers need no payment method, so half, as on the other AWS listings (10). A person signs up in a browser and sets up a gateway, a target and IAM (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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 +8

Web Search Tool on Amazon Bedrock AgentCore 75

One tool with a compact schema, and results are snippets AWS says are extracted for model context. Each result comes as a JSON string in a text block and again as structuredContent (22 of 25). maxResults 1 to 25, per-request domain include and exclude lists and published-date bounds from 1.2.0. No pagination, offset, country or language controls (15 of 20). JWT failures return 401 or 403 with a WWW-Authenticate header naming the scopes, and throttling returns retryAfter, but no error codes for the tool itself are documented (10 of 20). Searches only read, so retries are safe apart from the per-query charge. Connector 1.3.0 (19 October 2026, now the default) adds a title and readOnlyHint: true and openWorldHint: true to tools/list, per the connector versions page read on 1 November. No idempotentHint, and older pinned targets don't carry the annotations until updated (16 of 20, up from 12 when annotations were unconfirmed). Only query is required, and since the default moved from 1.1.0 to 1.3.0 a target created without a version gets the filters. A first call still needs a gateway, a target, a service role and inbound auth. Any MCP client calls it, and set-up runs through AWS SDKs in many languages (12 of 15, up from 10).

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.

Maintenance & community Hyperresearch +8

Web Search Tool on Amazon Bedrock AgentCore 80

Read for a closed service, from the connector versions page, release notes and What's New, with the control-plane model checked as the other AWS listings are. The newest change is connector 1.3.0 on 19 October 2026, which adds MCP tool annotations, 13 days before 1 November (30). Three dated changes in the 90 days from 3 August, filters and two Regions announced on 19 August, four Regions on 15 October and connector 1.3.0 on 19 October. Connector 1.2.0 (20 July) has left the window, and no bedrock-agentcore-control model commit since then changes the connector shapes (20). Public release notes with RSS, What's New, re:Post and AWS Support. Reply times were not checked (10 of 15). Set-up is in the current AWS SDKs and the AgentCore CLI, which reached 1.0 on 28 October, and the call itself is plain MCP (15). Nothing package-specific to measure for a hosted connector (5 of 10).

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.

Security & auth Web Search Tool on Amazon Bedrock AgentCore +6

Web Search Tool on Amazon Bedrock AgentCore 85

Gateway inbound auth is OAuth JWT from the owner's identity provider with allowed scopes advertised in the 401 challenge, or IAM SigV4 scoped to one gateway ARN, and the agent never holds a search credential (30). The tool only reads. The owner's target-level include and exclude lists cannot be relaxed by the agent, the service role's InvokeWebSearch names one service-owned ARN, and Cedar policies on the gateway can forbid the tool per caller. A no-authorisation gateway mode exists, with AWS's warning against production use (17 of 20). Results are third-party page text and the Web Search pages give no guidance on treating them as untrusted. Gateway guardrail policies can screen inputs for prompt attacks and suppress outputs, documented in general and not for this tool (7 of 15). CloudWatch metrics by method and tool name, and CloudTrail data events for InvokeGateway when the owner turns them on, at extra cost (13 of 15). A vulnerability disclosure programme on HackerOne, a security.txt that expires on 16 October 2027 (re-read on 1 November), and SOC and ISO 27001 among the programmes the AgentCore FAQ lists. No paid bounty found, so 2 held back as on every AWS listing (18 of 20).

Hyperresearch 79

Bearer keys of 32 random bytes stored as salted hashes, shown once, scoped to runs:read, runs:write, vault:read, vault:write, verify, mcp and admin, with a last-used time, rotation with a 24-hour overlap and instant revocation, plus an IP allowlist. MCP uses OAuth with PKCE and a consent screen that lists each scope. The docs say never to put keys in URLs (30). A client that requests no scopes gets read-only access, billed scopes are marked on the consent screen, and every workspace has a spend cap. No confirmation step for deletes was found (16 of 20). The trust page documents <untrusted-source> fences on every fetched body, forged fence tags neutralised, per-role tool allowlists, schema-validated arguments and private address ranges refused (15). A workspace audit log exportable as NDJSON, a 365-day default window, and a list of agent connections that can be revoked (15). No security.txt (404), no formal disclosure policy and no bug bounty, and the trust page says there is no SOC 2 report. Vulnerabilities go to support@hyperresearch.ai (3 of 20). 30+16+15+15+3 = 79.

Transparency & trust Web Search Tool on Amazon Bedrock AgentCore +6

Web Search Tool on Amazon Bedrock AgentCore 77

Closed service under the AWS Customer Agreement and Service Terms, updated 30 October 2026, with an acceptable-use section on the docs page (15 of 30). The docs say queries are served inside AWS and not sent to a third-party engine, the Gateway data protection notes say data is encrypted with a service key or a customer managed key, and section 50.3 of the Service Terms does not list AgentCore for content use. No retention period for queries was found (15 of 30). The connector versions page sets out stages from available to deprecated and retired and promises a migration guide for a major version, without a notice period (12 of 20). A sub-processor list updated 30 October 2026 and a per-Region availability list, and the August release note says queries stay in their Region (18 of 20).

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

CategoryWeightWeb Search Tool on Amazon Bedrock AgentCoreHyperresearchEdge
Reliability16%9035Web Search Tool on Amazon Bedrock AgentCore +55
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7876Web Search Tool on Amazon Bedrock AgentCore +2
Agent ergonomics13%7583Hyperresearch +8
Security & auth14%8579Web Search Tool on Amazon Bedrock AgentCore +6
Payments & pricing10%4560Hyperresearch +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8088Hyperresearch +8
Transparency & trust7%7771Web Search Tool on Amazon Bedrock AgentCore +6
Negative events≤1500
TotalBB 77.1/100B 68.1/100

Facts side by side

FactWeb Search Tool on Amazon Bedrock AgentCoreHyperresearch
KindMCP serverHTTP API
VendorAmazon Web ServicesHyperresearch
Hosted endpointhttps://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcphttps://answers.hyperresearch.ai/mcp
TransportsStreamable HTTPStreamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
Price for web search$7 per 1,000 requests$0.05 per call
x402nono
LicenceProprietary service under the AWS Customer Agreement and Service Terms, with an acceptable-use section on the tool's documentation pagenone
Tools exposed1none
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedai.hyperresearch/answers
Last release2026-10-192026-11-16
Terms last updated2026-10-012026-11-17
Privacy policy last updated2026-05-182026-11-17
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews3.3/5 (4)none

How the scores have moved

Verdicts

Web Search Tool on Amazon Bedrock AgentCore

One compact MCP tool returns ranked snippets with URLs, titles and published dates from an Amazon-operated index, with domain and date filters and a read-only annotation on the default connector, at $7 per 1,000 queries. A first call needs an AWS account, a Gateway with inbound auth, a target and a service role, and tool errors are not documented.

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

Web Search Tool on Amazon Bedrock AgentCore

  1. Call tools/list on the gateway and take the tool's name from it. AWS's call examples name gateway tools by target and tool
  2. Keep query to 200 characters and maxResults between 1 and 25 (default 10). The published schema states these limits only in descriptions
  3. Check the target's connector version before sending filters. Version 1.1.0 exposes only query and maxResults; 1.2.0 and the default 1.3.0 take filters
  4. Keep each result's URL and title with any answer built from it. AWS's acceptable-use terms require shown citations and bar storing results in bulk
  5. On a throttled request, wait the retryAfter seconds in the error body. The default quota is 10 Web Search requests a second, adjustable

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, Web Search Tool on Amazon Bedrock AgentCore or Hyperresearch?

Web Search Tool on Amazon Bedrock AgentCore scores 77.1 (BB) on agent readiness against Hyperresearch's 68.1 (B), and leads in 4 of 7 scored categories. Hyperresearch leads on agent ergonomics, payments & pricing and maintenance & community.

Do Web Search Tool on Amazon Bedrock AgentCore and Hyperresearch need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Web Search Tool on Amazon Bedrock AgentCore and Hyperresearch without installing anything?

Yes. Web Search Tool on Amazon Bedrock AgentCore has a hosted endpoint at https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp and Hyperresearch at https://answers.hyperresearch.ai/mcp.

Other comparisons with Web Search Tool on Amazon Bedrock AgentCore 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.