Skip to content
DrCompsSignal / computer news
Menu

AWS turns AgentCore web search into a direct billed API

AWS now exposes AgentCore Web Search through a direct IAM-authorized API priced at $7 per 1,000 queries, without requiring an MCP gateway.

AWS has made Amazon Bedrock AgentCore Web Search available as a direct API, giving applications, custom agent loops, and data pipelines a way to retrieve ranked web results without first creating an AgentCore Gateway or exposing the search function as an MCP tool.

What changed

The new InvokeWebSearch operation returns ranked results from Amazon’s web index. Results include a text extract and, when available, a title, URL, and publication time. Each request can restrict results by domain and publication window, and callers authenticate with AWS Identity and Access Management.

The practical architectural change is that teams can now call the search data plane from ordinary application code, AWS SDKs, or the AWS CLI. The existing Gateway connector remains the better fit when an MCP client should discover and invoke search as a tool. The API can also run through AWS PrivateLink, while CloudTrail data events can record requests for auditing.

Cost and operating limits

AWS lists the price as $7 per 1,000 searches, with no additional Gateway charge for direct API calls. That is a vendor-published list price, not an independently measured total cost. Model inference, network transfer, storage, logging, and the rest of an agent stack can add separate charges.

The default quota is 10 API requests per second per account in each supported region, with increases available through AWS Support. Launch coverage is limited to six commercial regions: Northern Virginia, Ohio, Oregon, Sydney, Tokyo, and Ireland. The direct API is not available in AWS GovCloud; AWS directs GovCloud users to the Gateway connector instead.

What it does not establish

AWS has not published independent relevance, freshness, recall, latency, or adversarial-resilience benchmarks for the search index. A managed search API also does not eliminate source verification, prompt-injection defenses, citation checks, or application-level authorization. AWS’s acceptable-use terms require applications to retain and display the source citations and links returned with results.