Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Web Search returns ranked search results for your model to synthesize; Web Answer runs an AWS-managed search and answer flow and returns a cited response.
- The connector is currently available in us-east-1 and launches in English. Cross-Region inference observes geographic boundaries, but does not guarantee processing only in us-east-1.
- Web Answer costs $10 per 1,000 tool calls; account separately for Gateway and other billable services in your architecture.
- Read citations from every structuredContent.answer block and retain and display the supplied source links in end-user output.
Choose the answer mode: Web Answer and Web Search solve different tasks
AWS announced general availability of Web Answer on November 5, 2026. An agent submits a natural-language question and receives a finished answer with citations to current web sources in one tool call. Amazon Bedrock manages the search, reading and answer flow. Web Search returns ranked results for your own model to synthesize, leaving the retrieval pipeline and source mapping to your application.
Use Web Search when you need control over how an answer is composed or want to pass search results to your own model. Consider Web Answer when a question is one step in a larger agent workflow and you do not want to maintain a retrieval and synthesis pipeline for that step. The tools can complement each other. Web Answer is a developer tool called over MCP, not a question-answering interface for end users.
Check availability and understand the pricing boundary
As of November 6, 2026, the Web Answer connector is available in US East (N. Virginia), or us-east-1, and launches in English only. The connector's available Region and the inference processing location are different commitments: Web Answer uses geographic cross-Region inference, keeping processing within supported AWS geographic boundaries, but this does not guarantee that all data is processed only in us-east-1. Do not infer a single-Region processing guarantee from the connector's Region.
The current AWS product page lists Web Answer at $10 per 1,000 tool calls. This is the Web Answer tool-call rate, not the total price of an agent. AgentCore Gateway API invocations and other services used by your architecture may be billed separately. Check current Amazon Bedrock AgentCore pricing and the services you actually use before launch.
Configure a Gateway target, then call it over MCP
A Gateway administrator adds a Web Answer target to an Amazon Bedrock AgentCore Gateway using the connector identifier connectorId: "web-answer". Access is authorized with IAM; you do not create a separate Web Answer API key. The Gateway service role still needs to be configured according to AWS's target setup guide. With an AgentCore harness, attach the Gateway as an agentcore_gateway tool and grant the harness execution role bedrock-agentcore:InvokeGateway on the relevant Gateway ARN.
The agent sends MCP tools/list to the Gateway endpoint and then invokes the target with tools/call. The list can also contain x_amz_bedrock_agentcore_search, which may appear before Web Answer. Do not select by array position; choose the tool whose name ends with ___WebAnswer. A call requires a natural-language query. The filters and userLocation fields are available only with connector version 1.1.0 or later; version 1.0.0 accepts only query.
Keep request filters within administrator policy
Starting with connector version 1.1.0, an administrator can set domain boundaries on the Gateway target through parameterValues.domainFilter.include and parameterValues.domainFilter.exclude, with up to 50 domains in each list. The agent cannot see these target-level lists, and the limits apply to every request through that target.
A request can also send filters.domainFilter with up to 50 include and 50 exclude entries. The target and request exclude lists combine as a union, and a root domain also matches its subdomains. If both include lists are set, their intersection applies; an empty intersection returns a validation error. A request cannot remove a target-level exclusion or expand beyond the target include list. filters.publishedDateFilter.from and to are inclusive bounds interpreted in UTC. Use an ISO 8601 date or date-time; a date-only to covers the whole day. The optional userLocation.country field accepts an ISO 3166-1 alpha-2 country code.
Map and display citations from every answer block
An MCP response can include Markdown in content[].text, structured data in structuredContent.answer, isError, and other metadata. Read every block in structuredContent.answer. Each block has its own text and optional citations; a [[N](url)] marker in that block's text refers to citations[N-1] from the same block, not a citation list from another block. Do not stop at the first answer block or merge citation numbers across blocks.
When isError is true, handle the result as an error rather than presenting it as an answer. Any end-user output that uses a Web Answer Result must retain and display the source citations and links supplied with it. AWS terms prohibit extracting, storing, or reproducing result content in bulk, and prohibit building or populating a competing index or database. Citations let readers inspect sources; they do not prove that an answer is correct or complete. Review the original sources for important or regulated decisions. Web Answer is not a substitute for professional advice.
Sources
Frequently Asked Questions
Is there a length limit for query?
Yes. The current developer guide allows 1 to 30,000 characters. Your application can check length before sending a question. Keep credentials and unredacted private records out of it.
What happens if the start date is later than the end date?
A publishedDateFilter.from later than to returns a validation error. Correct the date range first; changing network egress does not resolve an invalid range.
Does _meta.latencyMs measure the total user wait?
No. The documentation defines it as server-side latency. Client connections, Gateway handling and interface rendering can affect the actual wait, so do not treat this value as end-to-end latency.