{"resourceId":"aws-agentcore-web-search-api-ga-no-govcloud-20261110","versions":[{"version":"external-68342420a81c71ffacec2dc3f16dca75a5abb78c99a08b31a6ab3dc78c9986fb","resource":{"id":"aws-agentcore-web-search-api-ga-no-govcloud-20261110","title":"AWS makes AgentCore Web Search available as a direct API at $7 per 1,000 queries, in six commercial Regions","organization":"Amazon Web Services","sector":"Cross-SLED agent platforms","geography":"Six commercial AWS Regions (US, Sydney, Tokyo, Ireland)","publishedAt":"2026-11-10","publicationDate":"2026-11-10","eventDate":"2026-11-10","sourceName":"AWS What's New","sourceLabel":"Amazon Bedrock AgentCore now offers a Web Search API","sourceUrl":"https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-bedrock-agentcore-web-search-api/","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["developers-agents","infrastructure","data-security"],"finding":"On November 10, 2026 AWS announced general availability of the InvokeWebSearch API on Bedrock AgentCore, returning ranked results from an Amazon-operated web index with text extracts, titles, URLs and publication times, filterable by domain and date. Calls are IAM-authorized, can run over PrivateLink and can be logged as CloudTrail data events, billed at $7 per 1,000 queries. The API is available in six commercial Regions; AWS's developer guide states it is not available in GovCloud (US-West), where the earlier Gateway connector must be used.","sledRelevance":"Agencies and universities building research, policy-monitoring or resident-service agents need current web grounding with domain allow-lists. The API simplifies this for commercial-Region workloads, but GovCloud tenants must stay on the Gateway connector.","evidence":"Vendor announcement plus AWS developer guide. No customer outcomes or quality measures of the search index.","architectureImplications":"Direct data-plane API with no resources to create; domain and date filters per request; PrivateLink and CloudTrail support. GovCloud workloads use the MCP-based Gateway Web Search Tool instead.","governanceImplications":"Domain filters let agencies restrict grounding to trusted sources such as .gov sites; the acceptable-use terms require retaining and displaying citations.","securityPrivacyImplications":"IAM-only authorization and CloudTrail data events support audit. Prompts and queries leaving the agent still reveal intent; agencies should review what queries may contain.","caveats":"Vendor claim; no index quality or freshness data. GovCloud limitation is from the AWS developer guide opened alongside.","streamIds":["aws"],"roles":{"sales":"Interpretation: position this for commercial-Region research and monitoring agents, such as legislative tracking or grant scanning. The customer problem is grounding agents in current, trusted web content without building a scraper. Stakeholders are digital services leads, research offices and the CISO. Discovery should ask which Region the workload runs in and which domains are trusted. Do not promise GovCloud availability or answer quality; neither is supported by the source.","engineering":"Interpretation: fit is good for commercial-Region custom agent loops and pipelines. Engineers call InvokeWebSearch with domain and date filters, over PrivateLink, with CloudTrail data events on. Prerequisites are IAM roles and a trusted-domain list. Constraints: not in GovCloud (US-West), 10 requests per second default quota, citation-retention terms. Proof of value should compare answers grounded on allow-listed domains against a known reference set and track query volume costs.","delivery":"Interpretation: delivery work is a bounded grounding pilot. Dependencies are an approved domain list and a cost budget. Ownership sits with the agent product owner, with security reviewing query logging. Governance checkpoints include domain list approval and citation display review. Proposed acceptance criteria: every answer shows source links, queries stay within budget, and off-list domains never appear. Risks include runaway query costs in agent loops and architecture divergence between GovCloud and commercial accounts."},"roleDetails":{"sales":{"customerProblem":"Agency and university agents need current, trusted web grounding without custom scraping.","stakeholders":["Digital services lead","University research office","CISO"],"discoveryQuestions":["Does the workload run in GovCloud or commercial Regions?","Which domains are trusted for grounding?","What query budget is acceptable?"],"valueHypothesis":"Simpler, auditable web grounding for commercial-Region agents; answer quality is unmeasured.","potentialEngagement":"A pilot grounding one monitoring agent on allow-listed government domains.","unsupportedClaims":["Availability in GovCloud via the API","Search quality or freshness","Total cost for agent workloads"]},"engineering":{"fit":"Commercial-Region agent workloads; GovCloud must use the Gateway connector.","architectureIntegration":"Direct data-plane API with domain/date filters, PrivateLink and CloudTrail data events.","prerequisites":["IAM roles","Trusted-domain list","CloudTrail data events enabled"],"constraints":["Not available in GovCloud (US-West)","Default 10 requests per second quota","Citation retention required"],"security":"IAM-only auth and CloudTrail logging; review what agent-generated queries reveal.","proofOfValue":["Compare grounded answers to a reference set","Measure off-list domain leakage","Track cost per completed task"]},"delivery":{"work":"Pilot web grounding for one agent with domain filters and cost monitoring.","dependencies":["Approved domain list","Budget","Logging setup"],"ownership":"Agent product owner; security reviews logs.","skillsAdoption":"Developers learn filter design and citation display.","governanceCheckpoints":["Domain list approval","Citation display review","Cost review"],"acceptanceCriteria":["Proposed: 100% of answers show source links","Proposed: zero off-list domains returned","Proposed: monthly query cost within budget"],"risks":["Runaway query costs","GovCloud/commercial architecture split","Over-reliance on unverified web content"]}},"retrievedAt":"2026-11-11T03:59:58Z","enrichedAt":"2026-11-11T04:05:52Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Citation display requirement may support transparency for residents.","procurementImplications":"Usage-based pricing at $7 per 1,000 queries; agent loops can generate many queries, so budget caps matter.","operatingModelImplications":"Teams must choose between API and Gateway connector by Region, which can split architectures between GovCloud and commercial accounts.","sourceVerification":{"openedUrl":"https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-bedrock-agentcore-web-search-api/","referenceExcerpt":"Web Search API queries are billed at $7 per 1,000 queries, the same rate as Web Search through AgentCore Gateway, with no gateway charges.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}