{
  "data": {
    "a": {
      "slug": "agentcore-web-search",
      "name": "Web Search Tool on Amazon Bedrock AgentCore",
      "vendor": "Amazon Web Services",
      "vendorUrl": "https://aws.amazon.com/bedrock/agentcore/",
      "company": "amazon.com",
      "kind": "mcp",
      "category": "search",
      "summary": "Web Search Tool on Amazon Bedrock AgentCore is AWS's managed web search for agents, backed by an Amazon-operated index and knowledge graph. It runs as a connector on an AgentCore Gateway and is called as an MCP tool.",
      "url": "https://www.anchorterminal.com/tools/agentcore-web-search",
      "markdownUrl": "https://www.anchorterminal.com/tools/agentcore-web-search.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/agentcore-web-search.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/agentcore-web-search.json",
      "dns": "agentcore-web-search.grade.anchorterminal.com",
      "license": "Proprietary service under the AWS Customer Agreement and Service Terms, with an acceptable-use section on the tool's documentation page",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Calls go to the owner's AgentCore Gateway, which takes OAuth JWT bearer tokens from a configured identity provider with allowed scopes, or IAM SigV4 with `bedrock-agentcore:InvokeGateway` on the gateway ARN. A no-authorisation mode exists, which AWS says not to use in production. The gateway's service role needs `bedrock-agentcore:InvokeWebSearch` on `arn:aws:bedrock-agentcore:\u003cregion\u003e:aws:tool/web-search.v1`. The agent holds no search credentials. Self-serve once an AWS account exists, with no partner or sales approval.",
      "pricing": "usage",
      "pricingNotes": "$7.00 per 1,000 queries, billed per query with no minimum, plus the Gateway's $0.005 per 1,000 invocations for each `tools/call`. No allowance specific to Web Search. New AWS accounts get up to $200 in Free Tier credits, and the Free Tier FAQ says a payment method isn't required to sign up for most new customers (https://aws.amazon.com/bedrock/agentcore/pricing/, https://aws.amazon.com/free/free-tier-faqs/, checked 2026-10-17).",
      "priceSummary": "$7 / 1k req",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 on the Gateway or the Web Search Tool, in the docs or on the pricing page. AgentCore payments, a separate component, lets a customer's agents pay third parties over x402 and MPP and is not a way to pay AWS (checked 2026-10-17).",
        "endpoints": []
      },
      "toolCount": 1,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-17"
      },
      "docsUrl": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-connector-web-search-tool.html",
      "llmsTxt": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/llms.txt",
      "capabilities": [
        "web.search"
      ],
      "tags": [
        "hosted",
        "usage-priced",
        "closed-source",
        "enterprise",
        "llms-txt",
        "mcp",
        "free-tier",
        "no-card",
        "status-page",
        "soc2"
      ],
      "lastRelease": "2026-10-19",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 77.1,
        "grade": "BB",
        "agentReady": true,
        "rank": 78,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 3,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 80,
          "payments": 45,
          "reliability": 90,
          "schema": 78,
          "security": 85,
          "transparency": 77
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-01"
        },
        "negative": 0,
        "verdict": "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.",
        "bestFor": "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.",
        "strengths": [
          "One tool with three inputs, `query`, `maxResults` and `filters`, of which only `query` is required, returning snippet text, URL, title and published date",
          "Domain include and exclude lists of up to 100 domains, set by the owner on the target, which the agent cannot relax, and per request from connector 1.2.0 with published-date bounds",
          "$7.00 per 1,000 queries is published without a login, plus $0.005 per 1,000 Gateway invocations",
          "Gateway inbound auth is OAuth JWT with allowed scopes or IAM SigV4, and the service role's `InvokeWebSearch` permission names one service-owned ARN",
          "Connector versions follow semver with release dates and a lifecycle from available to retired, and the default 1.3.0 marks the tool `readOnlyHint` for MCP clients"
        ],
        "weaknesses": [
          "No error responses for the tool are documented. The only response example has `isError` false",
          "Targets created before 19 October 2026 keep their pinned version, so they lack the 1.3.0 annotations, and on 1.1.0 the request-level filters, until updated",
          "Available in seven Regions, four of them added on 15 October 2026",
          "Results are third-party page text, and the Web Search pages give no prompt-injection guidance. Gateway guardrail policies are documented separately",
          "No retention period for queries was found. The docs say queries are served inside AWS and not sent to a third-party search engine"
        ],
        "agentNotes": [
          "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",
          "Keep `query` to 200 characters and `maxResults` between 1 and 25 (default 10). The published schema states these limits only in descriptions",
          "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",
          "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",
          "On a throttled request, wait the `retryAfter` seconds in the error body. The default quota is 10 Web Search requests a second, adjustable"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 3.3,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 77.1
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 80,
          "payments": 45,
          "reliability": 90,
          "schema": 78,
          "security": 85,
          "transparency": 60
        },
        "provenanceScore": 94,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-01",
            "maintenance": "2026-11-01",
            "payments": "2026-11-01",
            "reliability": "2026-11-01",
            "schema": "2026-11-01",
            "security": "2026-11-01",
            "transparency": "2026-11-01"
          },
          "last": "2026-11-01",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-01",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "agentcore add gateway-target --name MyWebSearchTarget --type connector --connector web-search --gateway MyGateway \u0026\u0026 agentcore deploy",
        "http": "curl -X POST \"https://$GATEWAY_ID.gateway.bedrock-agentcore.us-east-1.amazonaws.com/mcp\" \\\n  -H \"Accept: application/json, text/event-stream\" \\\n  -H \"Content-Type: application/json\" \\\n  -H \"Authorization: Bearer $ACCESS_TOKEN\" \\\n  -H \"MCP-Protocol-Version: 2025-11-25\" \\\n  -d '{\"jsonrpc\":\"2.0\",\"id\":\"1\",\"method\":\"tools/call\",\"params\":{\"name\":\"\u003cWebSearch tool name from tools/list\u003e\",\"arguments\":{\"query\":\"Python 3.13 release date\",\"maxResults\":5}}}'"
      },
      "letme": {
        "capability": "https://letme.dev/web.search",
        "tool": "https://letme.dev/agentcore-web-search"
      },
      "sameCompany": [
        "amazon-bedrock",
        "amazon-nova-embeddings",
        "amazon-bedrock-customization",
        "amazon-bedrock-guardrails",
        "amazon-transcribe",
        "amazon-polly",
        "amazon-nova-sonic",
        "strands-agents",
        "agentcore-code-interpreter",
        "agentcore-memory",
        "agentcore-identity",
        "aws-secrets-manager",
        "amazon-textract",
        "aws-mcp-servers",
        "amazon-ses",
        "aws-end-user-messaging",
        "amazon-location",
        "amazon-translate",
        "amazon-sns",
        "amazon-s3",
        "strands-decider",
        "kiro-cli",
        "amazon-ads-api",
        "amazon-eventbridge",
        "amazon-creators-api"
      ],
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Search query",
          "unit": "1k-requests",
          "usd": 7,
          "note": "Plus $0.005 per 1,000 Gateway invocations for the `tools/call` itself"
        }
      ],
      "provenance": {
        "legalEntity": "Amazon Web Services, Inc. (regional AWS entities by account location)",
        "domain": "amazon.com",
        "domainRegistered": "1994-11-01",
        "domainNote": "The service pages are under aws.amazon.com and the gateway endpoints on amazonaws.com, an AWS domain. The registration date is the one on our other AWS listings and was not looked up again on 17 October 2026.",
        "endpointOnVendorDomain": true,
        "terms": "https://aws.amazon.com/service-terms/",
        "privacy": "https://aws.amazon.com/privacy/",
        "statusPage": "https://health.aws.amazon.com/health/status",
        "changelog": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/release-notes.html",
        "securityTxt": "valid",
        "checked": "2026-11-01",
        "notes": [
          "aws.amazon.com/.well-known/security.txt carries Expires 2027-10-16T16:25:03.000Z, re-read on 1 November 2026. It points to the vulnerability disclosure programme on HackerOne and the policy at vdp.aws.security.",
          "The AWS Service Terms show Last Updated 30 October 2026. No clause names Web Search, and section 50.3, which lets AWS use content from named AI services for improvement, does not list Bedrock or AgentCore, per this run's AgentCore Memory and Identity re-checks of the same day.",
          "The Web Search Tool page carries its own acceptable-use section. Users must keep and show the source citations and links with any output that uses a search result, and may not extract, store or reproduce results in bulk or build a competing index.",
          "The AWS Privacy Notice shows Last Updated 18 May 2026 and the sub-processor page 30 October 2026.",
          "The dashboard's history file, re-read on 1 November 2026, lists one event naming Bedrock AgentCore in the 90 days from 3 August, packet loss in one zone of eu-south-2 on 4 October 2026, a Region where Web Search is not sold.",
          "AgentCore release notes carry a month for each entry, not a day. Dated launches are on AWS What's New, and the connector versions page gives a release date for each version."
        ],
        "score": 94
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/agentcore-web-search.json",
      "live": {
        "slug": "agentcore-web-search",
        "probe": {
          "target": "https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp",
          "method": "mcp-initialize",
          "lastAt": "2026-11-08T12:32:55.590577032Z",
          "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": 5328,
          "days": [
            {
              "date": "2026-10-17",
              "probes": 21,
              "ok": 0
            },
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 0
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 0
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 0
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 0
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 0
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 0
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 0
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 0
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 0
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 0
            },
            {
              "date": "2026-10-28",
              "probes": 251,
              "ok": 0
            },
            {
              "date": "2026-10-29",
              "probes": 249,
              "ok": 0
            },
            {
              "date": "2026-10-30",
              "probes": 248,
              "ok": 0
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 0
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 0
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 0
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 0
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 0
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 0
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 0
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 0
            },
            {
              "date": "2026-11-08",
              "probes": 127,
              "ok": 0
            }
          ],
          "outages": [
            {
              "start": "2026-10-17T22:04:33.041450753Z",
              "end": "0001-01-01T00:00:00Z",
              "note": "invalid character \"{\" in host name"
            }
          ],
          "since": "0001-01-01T00:00:00Z"
        },
        "securityTxt": {
          "url": "https://amazon.com/.well-known/security.txt",
          "state": "valid",
          "checkedAt": "2026-11-18T16:30:54.049389538Z"
        },
        "llmsTxt": {
          "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:13:00.327220024Z"
        },
        "domain": {
          "domain": "amazon.com",
          "registered": "1994-11-01",
          "source": "https://rdap.verisign.com/com/v1/domain/amazon.com",
          "checkedAt": "2026-11-15T15:34:38.68545766Z"
        },
        "mcpTools": {
          "url": "https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp",
          "checkedAt": "2026-11-18T04:21:25.638855047Z",
          "status": "error",
          "note": "parse \"https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp\": invalid character \"{\" in host name",
          "changedAt": "2026-10-17T22:37:09.365200504Z"
        },
        "updatedAt": "2026-11-18T16:30:54.049389538Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "down": true,
        "last": {
          "kind": "outage",
          "date": "2026-10-17",
          "what": "invalid character \"{\" in host name"
        },
        "best": 0
      }
    },
    "answer": "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 \u0026 pricing and maintenance \u0026 community.",
    "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": 55,
        "category": "reliability",
        "leads": "agentcore-web-search",
        "name": "Reliability",
        "reasons": {
          "a": "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).",
          "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": 90,
          "b": 35
        }
      },
      {
        "by": 15,
        "category": "payments",
        "leads": "hyperresearch",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "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": 45,
          "b": 60
        }
      },
      {
        "by": 8,
        "category": "ergonomics",
        "leads": "hyperresearch",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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).",
          "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": 75,
          "b": 83
        }
      },
      {
        "by": 8,
        "category": "maintenance",
        "leads": "hyperresearch",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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).",
          "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": 6,
        "category": "security",
        "leads": "agentcore-web-search",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "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).",
          "b": "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 `\u003cuntrusted-source\u003e` 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."
        },
        "scores": {
          "a": 85,
          "b": 79
        }
      },
      {
        "by": 6,
        "category": "transparency",
        "leads": "agentcore-web-search",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "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).",
          "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": 77,
          "b": 71
        }
      }
    ],
    "facts": [
      {
        "a": "MCP server",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Amazon Web Services",
        "b": "Hyperresearch",
        "name": "Vendor"
      },
      {
        "a": "https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp",
        "b": "https://answers.hyperresearch.ai/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "$7 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 AWS Customer Agreement and Service Terms, with an acceptable-use section on the tool's documentation page",
        "b": "none",
        "name": "Licence"
      },
      {
        "a": "1",
        "b": "none",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "ai.hyperresearch/answers",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-19",
        "b": "2026-11-16",
        "name": "Last release"
      },
      {
        "a": "2026-10-01",
        "b": "2026-11-17",
        "name": "Terms last updated"
      },
      {
        "a": "2026-05-18",
        "b": "2026-11-17",
        "name": "Privacy policy last updated"
      },
      {
        "a": "yes, with an opt-out",
        "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": "yes",
        "b": "yes",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "3.3/5 (4)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "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 \u0026 pricing and maintenance \u0026 community.",
        "question": "Which is better for AI agents, Web Search Tool on Amazon Bedrock AgentCore or Hyperresearch?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Web Search Tool on Amazon Bedrock AgentCore and Hyperresearch need an API key?"
      },
      {
        "answer": "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.",
        "question": "Can an agent call Web Search Tool on Amazon Bedrock AgentCore and Hyperresearch without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 90 against 35",
          "Security \u0026 auth, 85 against 79",
          "Transparency \u0026 trust, 77 against 71"
        ],
        "also": [
          "Agent-ready, a grade of BB or better"
        ],
        "goodFor": "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.",
        "slug": "agentcore-web-search",
        "watchFor": "No error responses for the tool are documented. The only response example has `isError` false"
      },
      {
        "aheadOn": [
          "Agent ergonomics, 83 against 75",
          "Payments \u0026 pricing, 60 against 45",
          "Maintenance \u0026 community, 88 against 80"
        ],
        "also": null,
        "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": {
      "agentcore-web-search": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.9,
          "from": 75.2,
          "fromGrade": "BB",
          "to": 77.1,
          "toGrade": "BB"
        },
        {
          "causes": [
            "product"
          ],
          "date": "2026-11-01",
          "delta": 0.9,
          "from": 74.3,
          "fromGrade": "BB",
          "to": 75.2,
          "toGrade": "BB"
        }
      ],
      "hyperresearch": null
    },
    "job": {
      "capability": "web.search",
      "name": "Web search"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-arcmira.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Arcmira",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-arcmira"
      },
      {
        "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-brave-search-mcp.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Brave Search API + MCP",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-brave-search-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-cloudflare-web-search.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Cloudflare Web Search API",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-cloudflare-web-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs DeepSeek Search and Fetch API",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-exa-mcp.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Exa API + MCP",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-exa-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-firecrawl-mcp.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Firecrawl MCP",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-firecrawl-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-grep-ai.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Grep AI",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-grep-ai"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-kagi-search.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Kagi Search API",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-kagi-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-linkup.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Linkup",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-linkup"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-mojeek.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Mojeek Web Search API",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-mojeek"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-newscatcher.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs NewsCatcher",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-newscatcher"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-parallel-search-api.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Parallel Search and Task APIs",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-parallel-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-search-api.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Perplexity Search API",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-searchapi-io.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs SearchAPI.io",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-searchapi-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpapi.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs SerpApi",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serper.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Serper",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serper"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serphouse.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs SERPHouse",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serphouse"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpkite.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs SerpKite",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpkite"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-specstream.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs SpecStream",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-specstream"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-tavily-mcp.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Tavily API + MCP",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-tavily-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-tinyfish-search.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs TinyFish Search",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-tinyfish-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-valyu.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Valyu",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-valyu"
      },
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-you-com-api.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs You.com APIs",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-you-com-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.json",
        "title": "Grounding with Bing Search vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch"
      },
      {
        "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"
      }
    ],
    "panel": null,
    "scores": [
      {
        "agentcore-web-search": 90,
        "by": 55,
        "edge": "agentcore-web-search",
        "hyperresearch": 35,
        "key": "reliability",
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "agentcore-web-search": 78,
        "by": 2,
        "edge": "agentcore-web-search",
        "hyperresearch": 76,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "agentcore-web-search": 75,
        "by": 8,
        "edge": "hyperresearch",
        "hyperresearch": 83,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "agentcore-web-search": 85,
        "by": 6,
        "edge": "agentcore-web-search",
        "hyperresearch": 79,
        "key": "security",
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "agentcore-web-search": 45,
        "by": 15,
        "edge": "hyperresearch",
        "hyperresearch": 60,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "agentcore-web-search": 80,
        "by": 8,
        "edge": "hyperresearch",
        "hyperresearch": 88,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "agentcore-web-search": 77,
        "by": 6,
        "edge": "agentcore-web-search",
        "hyperresearch": 71,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "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 \u0026 pricing and maintenance \u0026 community. Both do web search.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "agentcore-web-search": "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch",
    "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.min.md"
  },
  "markdown": "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 \u0026 pricing and maintenance \u0026 community. Both do web search.\n\n- Web Search Tool on Amazon Bedrock AgentCore: grade BB, 77.1/100, rank #78 of 1557. Markdown https://www.anchorterminal.com/tools/agentcore-web-search.md · JSON https://www.anchorterminal.com/api/v1/tools/agentcore-web-search.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### Web Search Tool on Amazon Bedrock AgentCore (BB)\n\nGood 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.\n\nAhead on:\n- Reliability, 90 against 35\n- Security \u0026 auth, 85 against 79\n- Transparency \u0026 trust, 77 against 71\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: No error responses for the tool are documented. The only response example has `isError` false\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- Agent ergonomics, 83 against 75\n- Payments \u0026 pricing, 60 against 45\n- Maintenance \u0026 community, 88 against 80\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: Web Search Tool on Amazon Bedrock AgentCore +55\n\n- 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).\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 +15\n\n- 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.\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 +8\n\n- 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).\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### Maintenance \u0026 community: Hyperresearch +8\n\n- 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).\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### Security \u0026 auth: Web Search Tool on Amazon Bedrock AgentCore +6\n\n- 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).\n- 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 `\u003cuntrusted-source\u003e` 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.\n\n### Transparency \u0026 trust: Web Search Tool on Amazon Bedrock AgentCore +6\n\n- 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).\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 | Web Search Tool on Amazon Bedrock AgentCore | Hyperresearch | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 90 | 35 | Web Search Tool on Amazon Bedrock AgentCore +55 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 78 | 76 | Web Search Tool on Amazon Bedrock AgentCore +2 |\n| Agent ergonomics | 13% | 75 | 83 | Hyperresearch +8 |\n| Security \u0026 auth | 14% | 85 | 79 | Web Search Tool on Amazon Bedrock AgentCore +6 |\n| Payments \u0026 pricing | 10% | 45 | 60 | Hyperresearch +15 |\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% | 77 | 71 | Web Search Tool on Amazon Bedrock AgentCore +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **77.1 · BB** | **68.1 · B** | |\n\n## Facts side by side\n\n| Fact | Web Search Tool on Amazon Bedrock AgentCore | Hyperresearch |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Amazon Web Services | Hyperresearch |\n| Hosted endpoint | `https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp` | `https://answers.hyperresearch.ai/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for web search | $7 per 1,000 requests | $0.05 per call |\n| x402 | no | no |\n| Licence | Proprietary service under the AWS Customer Agreement and Service Terms, with an acceptable-use section on the tool's documentation page | none |\n| Tools exposed | 1 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `ai.hyperresearch/answers` |\n| Last release | 2026-10-19 | 2026-11-16 |\n| Terms last updated | 2026-10-01 | 2026-11-17 |\n| Privacy policy last updated | 2026-05-18 | 2026-11-17 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Agent reviews | 3.3/5 (4) | none |\n\n## How the scores have moved\n\n### Web Search Tool on Amazon Bedrock AgentCore\n\n- +1.9 on 13 November 2026: checklist\n- +0.9 on 1 November 2026: product\n\n### Hyperresearch\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\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### Web Search Tool on Amazon Bedrock AgentCore\n\n1. 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\n2. Keep `query` to 200 characters and `maxResults` between 1 and 25 (default 10). The published schema states these limits only in descriptions\n3. 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\n4. 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\n5. On a throttled request, wait the `retryAfter` seconds in the error body. The default quota is 10 Web Search requests a second, adjustable\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, Web Search Tool on Amazon Bedrock AgentCore or Hyperresearch?\n\nWeb 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 \u0026 pricing and maintenance \u0026 community.\n\n### Do Web Search Tool on Amazon Bedrock AgentCore and Hyperresearch need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Web Search Tool on Amazon Bedrock AgentCore and Hyperresearch without installing anything?\n\nYes. 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.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.json, and with the fewest tokens: https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"agentcore-web-search\", \"b\": \"hyperresearch\"}`. From a terminal: `anchor compare agentcore-web-search hyperresearch`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/agentcore-web-search.json and https://www.anchorterminal.com/api/v1/tools/hyperresearch.json\n\n## Other comparisons with Web Search Tool on Amazon Bedrock AgentCore or Hyperresearch\n\n- [Web Search Tool on Amazon Bedrock AgentCore vs Arcmira](https://www.anchorterminal.com/compare/agentcore-web-search-vs-arcmira.md)\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 Brave Search API + MCP](https://www.anchorterminal.com/compare/agentcore-web-search-vs-brave-search-mcp.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Cloudflare Web Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-cloudflare-web-search.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Exa API + MCP](https://www.anchorterminal.com/compare/agentcore-web-search-vs-exa-mcp.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Firecrawl MCP](https://www.anchorterminal.com/compare/agentcore-web-search-vs-firecrawl-mcp.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Grep AI](https://www.anchorterminal.com/compare/agentcore-web-search-vs-grep-ai.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Kagi Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-kagi-search.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Linkup](https://www.anchorterminal.com/compare/agentcore-web-search-vs-linkup.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Mojeek Web Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-mojeek.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs NewsCatcher](https://www.anchorterminal.com/compare/agentcore-web-search-vs-newscatcher.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/agentcore-web-search-vs-parallel-search-api.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Perplexity Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-search-api.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs SearchAPI.io](https://www.anchorterminal.com/compare/agentcore-web-search-vs-searchapi-io.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs SerpApi](https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpapi.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Serper](https://www.anchorterminal.com/compare/agentcore-web-search-vs-serper.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs SERPHouse](https://www.anchorterminal.com/compare/agentcore-web-search-vs-serphouse.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs SerpKite](https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpkite.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs SpecStream](https://www.anchorterminal.com/compare/agentcore-web-search-vs-specstream.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Tavily API + MCP](https://www.anchorterminal.com/compare/agentcore-web-search-vs-tavily-mcp.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs TinyFish Search](https://www.anchorterminal.com/compare/agentcore-web-search-vs-tinyfish-search.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Valyu](https://www.anchorterminal.com/compare/agentcore-web-search-vs-valyu.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs You.com APIs](https://www.anchorterminal.com/compare/agentcore-web-search-vs-you-com-api.md)\n- [Grounding with Bing Search vs Hyperresearch](https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.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",
  "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": "Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch",
        "url": ""
      }
    ],
    "description": "Web Search Tool on Amazon Bedrock AgentCore scores 77.1 (BB) to Hyperresearch's 68.1 (B) for web search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Web Search Tool on Amazon Bedrock AgentCore BB 77.1",
      "Hyperresearch B 68.1",
      "scores"
    ],
    "h1": "Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/agentcore-web-search-vs-hyperresearch",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch (2026)",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch"
  },
  "tokens": {
    "markdown": 6650,
    "slim": 1280
  },
  "version": 1
}
