AgentCore Web Search API: Pricing, Regions and How to Use AWS's New InvokeWebSearch

Amazon Bedrock AgentCore's InvokeWebSearch API: $7 per 1,000 queries, six Regions, 10 RPS default. API vs Gateway connector, IAM policy and Boto3 code.

Sanchana Charles11 November 202610 min read0 viewsAWS
AgentCore Web Search API: Pricing, Regions and How to Use AWS's New InvokeWebSearch

AWS now lets you search the web with a single API call: the new InvokeWebSearch API on Amazon Bedrock AgentCore returns ranked web results, with text extracts, titles, URLs and publication dates, for $7 per 1,000 queries. It went generally available on 10 November 2026 in six AWS Regions. You don't need a gateway or an MCP setup: you need IAM permission and a current AWS SDK or CLI.

Until now, AgentCore's web search was only available as an MCP tool behind an AgentCore Gateway. The new API is meant for your own code (a custom agent loop, a RAG pipeline, a fact-checking job) that wants search results directly (AWS What's New). Here's what it does, what it costs, and how to call it.

What is the AgentCore Web Search API?

It's a managed web search endpoint from AWS, backed by an Amazon-operated web index rather than a resold third-party search engine. AWS says the index spans "tens of billions of documents" and reflects new and changed content "within minutes" (AgentCore Developer Guide, Web Search Tool).

Each call returns a ranked list. Every result includes a text extract chosen to be relevant to your query (not raw HTML), plus the page title, URL and publication time when available (AgentCore Developer Guide, Web Search). You can narrow each request by:

  • Domain: an include list, for example only your own docs site and a trusted news source.
  • Publication time: publishedAfter and publishedBefore, both inclusive.

There are no resources to create. You don't provision a gateway, a search index or an API key. Calls are authorised with IAM, can be made privately from a VPC through AWS PrivateLink, and can be logged as CloudTrail data events.

AWS also says that for the Gateway version, customer queries "are not sent to a third-party search engine or routed outside AWS". For teams that worry about where agent queries go, that answers a common security review question.

How much does AgentCore Web Search cost?

$7.00 per 1,000 queries, with no minimum fee and no upfront commitment (AgentCore pricing). The API is billed at the same per-query rate as Web Search through AgentCore Gateway, but with no gateway charges.

Estimates at list price, before any data transfer:

Monthly queries Web Search API Same queries via Gateway (adds InvokeTool at $0.005 per 1,000)
1,000 $7 about $7.01
10,000 $70 about $70.05
100,000 $700 about $700.50
1,000,000 $7,000 about $7,005

Our own arithmetic from AWS's published rates; the Gateway column assumes one InvokeTool call per search and ignores other Gateway calls such as ListTools. These are estimates, not quotes.

As the table shows, the Gateway overhead is small. The real reason to choose the API is architectural, not price (see the decision table below). If your agent needs a finished, cited answer rather than a list of results, AWS also offers Web Answer on AgentCore at $10 per 1,000 tool calls, according to the same pricing page.

Which AWS Regions support the Web Search API?

Six, per the developer guide:

Region Code
US East (N. Virginia) us-east-1
US East (Ohio) us-east-2
US West (Oregon) us-west-2
Asia Pacific (Sydney) ap-southeast-2
Asia Pacific (Tokyo) ap-northeast-1
Europe (Ireland) eu-west-1

The Gateway connector is also available in AWS GovCloud (US-West), but the API isn't, so GovCloud users should stay on the connector for now. If you have in-country data rules, compare this list against your requirements. Our Bedrock data residency explainer covers how AWS handles that for model inference.

Quota: by default, each account can send 10 InvokeWebSearch requests per second per Region. You can ask AWS Support for an increase.

API vs Gateway connector: which should you use?

This is the decision most teams will face. AWS's own guidance is simple: use the API when your code consumes the results, and use the connector when agents discover and call tools over MCP. The details from the developer guide:

InvokeWebSearch API Web Search Tool via AgentCore Gateway
How it's called Your code calls the AgentCore data plane endpoint Agents call an MCP tool through a gateway
Setup None beyond IAM Create a gateway, add the web-search connector target
Auth IAM only IAM or JSON Web Token (JWT)
Domain lists Per request Per request, plus target-level lists the agent can't see
Search text field searchQuery query (up to 200 characters)
Default results Up to 25 Up to 10
Date range fields publishedAfter / publishedBefore from / to
GovCloud (US-West) No Yes
Price $7 per 1,000 queries $7 per 1,000 queries + Gateway invocation fees

Pick the API for data pipelines, scheduled research jobs, your own agent loop (for example one built directly on a Bedrock model such as Claude Fable 5.2 on Bedrock), or anywhere MCP is extra plumbing you don't need.

Pick the Gateway if your agents already discover tools over MCP, if you need JWT auth for external callers, or if security teams want domain lists enforced centrally where an agent's prompt can't override them. That last point matters for prompt-injection risk. Our Step Functions and AgentCore Gateway explainer covers how Gateway tools fit into larger workflows.

One subtle difference worth knowing: with the SDKs and CLI, a publishedBefore value given as a date without a time is sent as midnight UTC at the start of that day. The MCP tool's to date includes the whole day. If you port a filter from one to the other, add T23:59:59Z to keep the same range.

How to use the AgentCore Web Search API: step by step

  1. Update your tooling. You need a current version of Boto3 or the AWS CLI. AWS says earlier versions don't include the InvokeWebSearch operation.
  2. Grant IAM permission. The principal needs bedrock-agentcore:InvokeWebSearch on the AWS-owned tool ARN. Note that the account field is the literal word aws, not your account ID (Get started guide):
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowInvokeWebSearch",
            "Effect": "Allow",
            "Action": "bedrock-agentcore:InvokeWebSearch",
            "Resource": "arn:aws:bedrock-agentcore:<Region>:aws:tool/web-search.v1"
        }
    ]
}
  1. Call the API. Only webSearchId (always web-search.v1) and searchQuery are required. This is AWS's own Boto3 example, which returns up to five results from two domains published in January 2026:
import boto3
from botocore.exceptions import ClientError

client = boto3.client("bedrock-agentcore", region_name="us-east-1")

try:
    response = client.invoke_web_search(
        webSearchId="web-search.v1",
        searchQuery="Amazon Bedrock AgentCore release announcements",
        maxResults=5,
        filters={
            "domainFilter": {
                "include": ["example.net", "example.org"]
            },
            "publishedDateFilter": {
                "publishedAfter": "2026-01-01T00:00:00Z",
                "publishedBefore": "2026-01-31T23:59:59Z"
            }
        }
    )
except ClientError as error:
    print(error.response["Error"]["Code"], error.response["Error"]["Message"])
    raise

for result in response["results"]:
    print(result.get("title"), result.get("url"))
    print(result["text"])

The same call from the AWS CLI:

aws bedrock-agentcore invoke-web-search \
  --region us-east-1 \
  --web-search-id web-search.v1 \
  --search-query "Amazon Bedrock AgentCore release announcements" \
  --max-results 5 \
  --filters '{
    "domainFilter": {"include": ["example.net", "example.org"]},
    "publishedDateFilter": {
      "publishedAfter": "2026-01-01T00:00:00Z",
      "publishedBefore": "2026-01-31T23:59:59Z"
    }
  }'
  1. Show your sources. AWS's acceptable-use terms for Web Search also apply to the API, and they require you to retain and display the source citations and links that come with each result. If you feed results into a chatbot, show the links to users.
  2. Turn on logging if you need it. To log calls in CloudTrail, enable data events with an advanced event selector. AWS notes CloudTrail doesn't record the search text or the filters, which helps with privacy but means you'll need your own logs if you want to audit what was searched.

What are developers saying?

The API is a day old, and we didn't find any developer discussion of it in our web searches on 11 November 2026. The questions people are searching for line up with the points above: pricing, Regions, whether it works with Claude Code and other MCP clients (that's the Gateway connector; AWS has a guide to adding it to Claude Desktop), and how it compares with the MCP connector. We'll add real-world reactions as they appear.

Editor's take

This is a small launch with a clear purpose. AWS already had a web search tool, but only for teams that bought into Gateway and MCP. Exposing the same Amazon-built index as a plain API makes it usable from a Lambda function, a Step Functions state or a cron job, which is where a lot of retrieval work actually happens.

The trade-offs to weigh: at $7 per 1,000 queries it isn't the cheapest way to get search results, and six Regions (no Frankfurt, London, Mumbai or São Paulo yet) will rule it out for some data-residency setups. In its favour are IAM-only auth, PrivateLink, queries that stay inside AWS and no extra vendor contract. For teams already on AWS, that cuts procurement and security review down to almost nothing, and for many enterprises that's worth more than the per-query price.

For a consumer-side view of Amazon's AI this week, see how Alexa for Shopping's price history and Auto Buy work ahead of Black Friday.

FAQ

It's a managed web search capability on Amazon Bedrock AgentCore, backed by an Amazon-operated web index. You can use it through the new InvokeWebSearch API or as an MCP tool behind AgentCore Gateway.

How much does AgentCore Web Search cost?

$7 per 1,000 queries. The API has no gateway charges. The Gateway route adds a small InvokeTool fee of $0.005 per 1,000 invocations.

Which regions is the AgentCore Web Search API available in?

US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo) and Europe (Ireland). The Gateway connector is also in AWS GovCloud (US-West).

Does AgentCore Web Search use Google or Bing?

No. AWS says it's backed by a web index that Amazon builds and operates, and that queries aren't sent to a third-party search engine.

What's the difference between InvokeWebSearch and the Web Search Tool connector?

The API is called directly by your code with IAM auth and returns up to 25 results by default. The connector is an MCP tool behind AgentCore Gateway, supports JWT auth and central domain lists, and returns up to 10 results by default.

Can I use AgentCore Web Search with Claude Code or Claude Desktop?

Through the Gateway connector, yes, as an MCP tool. AWS has published a guide for Claude Desktop. The InvokeWebSearch API itself isn't an MCP endpoint.

What is the rate limit for InvokeWebSearch?

10 requests per second per account per Region by default. You can request an increase through AWS Support.

No. Web Search returns ranked results. Web Answer returns a finished answer with citations and costs $10 per 1,000 tool calls.

Sources

Featured image: Servers inside an AWS data center in eastern Oregon (a general AWS data center photo, not specific to AgentCore Web Search), via About Amazon. Source

Share:

Comments

Leave a comment