AWS launches AgentCore Web Search API
Understand this story
AWS has launched the Web Search API in Amazon Bedrock AgentCore: developers can call InvokeWebSearch once to get ranked results from Amazon's own-operated web index, without first creating a gateway or managing an API key. AWS says queries are processed by Amazon's self-built index and do not go through third-party search engines. The API is currently available in US East (N. Virginia, Ohio), US West (Oregon), Europe (Ireland), and Asia Pacific (Tokyo, Sydney) regions. Pricing is $7 per 1,000 queries, using the same usage type as gateway connectors; interface endpoints are priced per AWS PrivateLink standard rates. By default, each account can send up to 10 requests per second per region, and increases can be requested. AWS has also published a LangGraph dependency monitoring tutorial: a single monitoring run executes at most 12 searches, and the first 6 steps of the tutorial do not create AWS resources.
AI overview based on source reports · Updated 3 days ago
Coverage timeline
Follow the coverage to explore different perspectives.
- AWS Machine Learning BlogIntroducing the Web Search API on Amazon Bedrock AgentCore
AWS announced the Web Search API on Amazon Bedrock AgentCore, which lets developers call the InvokeWebSearch operation directly from AWS SDKs or the AWS CLI with SigV4-signed IAM credentials, without creating a gateway or other resources. It returns up to 25 ranked results from an Amazon-operated web index, each with a text extract and, when available, title, URL, and publication time, and supports domain and publication-date filtering. It is available in six Regions and billed at $7 per 1,000 queries, complementing the existing AgentCore Gateway path.
- AWS Machine Learning BlogBuild a daily dependency watcher with LangGraph and Amazon Bedrock AgentCore web search
The Web Search API in Amazon Bedrock AgentCore is now available, returning current web results with title, URL, publication date and query-relevant extract, signed with existing AWS credentials and served from an Amazon-operated index. The post walks through building a LangGraph dependency watch that researches npm, PyPI and container base images in parallel, keeping the date window, domain blocklist and search budget in code and checking each finding against its cited sources. In the test run, three branches made 12 searches and finished in 36 seconds versus 99 seconds sequentially, and the watch can be hosted on AgentCore runtime or offered through AgentCore Gateway.
Activity for this story
- Current comparable activity
- 3
- Peak comparable activity
- 10Nov 11 08:00
- Change in the past 24 hours
- -50%
Trends compare the same fully observed participants, which may cover fewer participants than current activity. Move the pointer or tap the chart to inspect hourly activity; use the left and right arrow keys with a keyboard.