Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the AWS edition of November 10, 2026

Vendor claimEmergingNew this fortnight

AWS makes AgentCore Web Search available as a direct API at $7 per 1,000 queries, in six commercial Regions

Amazon Web Services · Cross-SLED agent platforms · Six commercial AWS Regions (US, Sydney, Tokyo, Ireland)

AWS
Publisher
AWS What's New
Original publication
2026-11-10
Source retrieved
2026-11-11
Event date
2026-11-10
Read original source

What happened

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.

Why it matters

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 and measured results

Vendor announcement plus AWS developer guide. No customer outcomes or quality measures of the search index.

Limitations and uncertainty

Vendor claim; no index quality or freshness data. GovCloud limitation is from the AWS developer guide opened alongside.

Cross-source patterns this evidence supports

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-11; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Agency and university agents need current, trusted web grounding without custom scraping.
Stakeholders
  • Digital services lead
  • University research office
  • CISO
Discovery questions
  • Does the workload run in GovCloud or commercial Regions?
  • Which domains are trusted for grounding?
  • What query budget is acceptable?
Value hypothesis
Simpler, auditable web grounding for commercial-Region agents; answer quality is unmeasured.
Potential engagement
A pilot grounding one monitoring agent on allow-listed government domains.
Unsupported claims
  • Availability in GovCloud via the API
  • Search quality or freshness
  • Total cost for agent workloads

Pre-sales engineering

Role takeaway
Fit
Commercial-Region agent workloads; GovCloud must use the Gateway connector.
Architecture and integration
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.
Proof of value
  • Compare grounded answers to a reference set
  • Measure off-list domain leakage
  • Track cost per completed task

Delivery

Role takeaway
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.
Skills and adoption
Developers learn filter design and citation display.
Governance checkpoints
  • Domain list approval
  • Citation display review
  • Cost review
Acceptance criteria
  • 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

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

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.

Governance

Who approves, reviews and stays accountable for outcomes?

Domain filters let agencies restrict grounding to trusted sources such as .gov sites; the acceptable-use terms require retaining and displaying citations.

Security and privacy

What data, permissions and controls need testing?

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.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Citation display requirement may support transparency for residents.

Procurement

What should contracts, pricing and exit terms secure?

Usage-based pricing at $7 per 1,000 queries; agent loops can generate many queries, so budget caps matter.

Operating model

Which teams own the service once it runs?

Teams must choose between API and Gateway connector by Region, which can split architectures between GovCloud and commercial accounts.

Publication history

  1. 2026-11-10AWS · Issue 128 resources
Read preserved resource versions (JSON)

Stable resource ID: aws-agentcore-web-search-api-ga-no-govcloud-20261110