AWS separates web search from the agent gateway, not from the need to verify results
AWS separates web search from the agent gateway, not from the need to verify results
AWS has made AgentCore web search callable directly from application code, without first creating an agent gateway. The general-availability notice is dated November10; the more detailed walkthrough appeared November11. This is newly discovered coverage of that release, not a November13 launch. GA announcement
The InvokeWebSearch operation uses ordinary AWS authentication and permissions. It returns ranked results from an Amazon-operated index, supports domain and publication-time filters, and can be used in applications or data pipelines as well as agents. The announcement lists $7 per 1,000 queries without gateway charges. Technical introduction
A useful caveat appears in the walkthrough: results have text extracts, but titles, URLs and publication times are returned when the index has them. Developers should not assume that every result arrives with a complete citation or reliable event date. AWS also presents the direct API as complementary to Gateway, not its replacement.
Analysis: fewer moving parts, the same evidence problem
This matters for developers who want retrieval without adopting an entire agent orchestration layer. A custom application can own its retry, caching and source-selection behavior rather than wrapping every search behind a gateway.
But a simpler request does not make its answer verified. Publication time is not necessarily the date the underlying event occurred, and a ranked excerpt is not the full source. A research agent still needs to inspect the relevant material, distinguish updates from old stories and keep track of missing metadata.
There is a separate security boundary too: approving access to a search API does not authorize a model to obey instructions it discovers on a web page. Search results should remain evidence to evaluate, not instructions controlling subsequent tools.
Evidence and limits
The detailed AWS blog was directly read. The November10 notice was available as substantial indexed official text; its direct extraction exposed navigation rather than the announcement body. Both are vendor sources. A November11 Unite.AI article was found, but the accessible extraction did not expose substantive reporting beyond the headline, so it is not cited as corroboration.
No API call, billing measurement, latency test or independent index-quality comparison was performed. The listed price is the announcement’s search-query price, not a complete application cost estimate. Exact launch time is unknown.
Cited primary sources
- AWS general availability announcement: 2026-11-10. Substantial indexed official text; direct extraction exposed navigation only; establishes GA date and quoted service price.
- AWS technical introduction: 2026-11-11. Directly read; API operation, IAM, optional metadata and gateway distinction.
Independent evidence
No independently tested search-quality or performance evidence verified. No additional background sources cited.
Sources and citations
Revision history
Published .