Building Agents That Transact With Anchor Browser and AgentCore Payments

What happened

The guide explains how Anchor Browser integrates with Amazon Bedrock AgentCore payments to handle x402-protected pages and APIs within the same browser session. Setting session.x402 to true enables automatic payments subject to configured spending and expiration limits, while wallet credentials remain outside the agent runtime. Existing browser automation code can continue unchanged; rejected payments or unsupported challenges leave the original HTTP 402 response intact.

The story so far

Anchor Browser has integrated Amazon Bedrock AgentCore payments to let agents pay for x402-protected pages and APIs within the same browser session, and AWS says the offering is now available on AWS Marketplace. It was developed in collaboration with the AWS Generative AI Innovation Center Partner Agent Factory. Automatic payments require session.x402 to be set to true and are subject to configured spending and expiration limits. Wallet credentials stay outside the agent runtime, and existing browser automation code can continue unchanged. If a payment is rejected or a challenge is unsupported, the original HTTP 402 response remains intact. The x402 setting covers payments to third-party resources only; it neither replaces Anchor credits nor pays for the browser session. Anchor Browser settles third-party x402 charges in credits on the same invoice as browser session time.

Keep reading

Trending now

1. 1Meta Releases Muse Spark Open With Mac and Cloud Support, Topping US Open-Weight Index
2. 2Google Launches Gemini 4 Argon Globally, Expands Paid Access as Benchmark Results Vary
3. 3OpenAI Updates GPT-6 Astra Pro in ChatGPT With Parallel Agents and Faster Responses
4. 4Meta’s New Business Terms Raise Dispute Over Website Crawling and AI Training Rights