Amazon Web Services has launched a standalone Web Search API for Amazon Bedrock AgentCore, letting applications and AI agents search the web with a single API call instead of building a gateway first. AWS announced the new capability on 11 November 2026.

Until now, web search on AgentCore was delivered through AgentCore Gateway, which required a gateway, a web search target and a Model Context Protocol (MCP) client. The new InvokeWebSearch operation removes that setup: developers call it from the AWS software development kits or the AWS command line, signed with their standard AWS Identity and Access Management credentials. There is no separate API key to manage and no resource to create first.

What the API returns

Each call returns ranked results from a web index that Amazon operates, with a text extract and, where available, the page title, URL and publication time. Queries can be up to 200 characters long, and callers can ask for between one and 25 results. Results can be filtered by domain and by publication date, so an agent can restrict itself to trusted sources or to pages published within a chosen window.

AWS says queries are served inside AWS rather than sent to a third-party search engine, and that the API runs on the same search infrastructure behind Alexa+, Kiro, Quick and other Amazon products. It is intended for custom agent loops and frameworks such as LangChain or LlamaIndex, as well as non-agent workloads including dashboards, fact-checking pipelines, content enrichment and monitoring systems.

Pricing, limits and availability

Searches are billed at $7 per 1,000 queries, the same rate as web search through AgentCore Gateway, but with no gateway charges on the direct path. By default each account can send up to 10 requests per second in each region, and higher limits can be requested. Python callers need Boto3 1.43.127 or later, and support is also included in langchain-aws 1.9.3 and the AgentCore Python SDK 1.26.0.

At launch the API is available in six regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), Asia Pacific (Tokyo) and Asia Pacific (Sydney). AWS still recommends AgentCore Gateway for most agentic workloads, particularly deployments that combine several MCP-compatible tools behind one endpoint or apply one administrator-controlled source policy across teams. Source: Amazon Web Services.; Unite.AI