Skip to content

AWS adds a direct Web Search API to Bedrock AgentCore, skipping the Gateway hop

· by

The short version

AWS shipped general availability of a Web Search API on Amazon Bedrock AgentCore on November 10, 2026, letting agents query the web with one IAM-authorized call instead of routing through the AgentCore Gateway's MCP tool.

AWS adds a direct Web Search API to Bedrock AgentCore, skipping the Gateway hop

AWS shipped general availability of a Web Search API on Amazon Bedrock AgentCore on November 10, 2026, letting agents query the web with a single InvokeWebSearch call instead of routing through the AgentCore Gateway's MCP tool layer, per AWS's announcement.

What AWS shipped

The new API returns ranked results from an Amazon-operated web index. Each result carries a text extract and, when available, a page title, URL, and publication time, per AWS. Developers can filter results by domain and by publication time, which matters for agents that need only recent coverage or only a defined set of sites. Calls run under standard AWS IAM authorization, can be routed through a VPC via AWS PrivateLink, and log as CloudTrail data events for audit trails. AWS priced the API at $7 per 1,000 queries, the same rate it already charges for Gateway-routed web search, with no separate gateway fee layered on top. It is live now in six regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Europe (Ireland).

Before this release, an AgentCore agent that needed web search had to call the Gateway, which wraps tools behind the Model Context Protocol and adds its own request handling on top of the underlying search call. The new API removes that wrapper for this one tool: an agent invokes InvokeWebSearch directly and gets results back without a Gateway round trip in between.

One fewer hop changes the default choice for agent builders

For teams already running Bedrock AgentCore, this removes a reason to keep web search behind Gateway. A direct IAM-authorized call is simpler to wire into an existing AWS permissions model than a Gateway-mediated MCP tool, and it carries no price premium over the path it replaces. That makes the direct API the more obvious default for any agent whose only Gateway dependency was web search; those teams can drop the Gateway hop for that tool without a cost tradeoff to weigh. Agents that still need other MCP tools, custom connectors or tools from a different vendor, for instance, keep using Gateway for those; AWS has not extended the bypass pattern beyond web search yet, so Gateway remains the integration point for everything else.

What to watch next

The open question is whether AWS applies the same direct-API pattern to other tools currently locked behind the Gateway's MCP layer, which would gradually shrink Gateway's role to tools with no first-party AWS equivalent. AWS has not indicated a timeline for that, nor whether the $7-per-1,000-query rate will hold as the feature moves past initial GA.

Sources