AWS says Anchor Browser and Amazon Bedrock AgentCore payments can let AI agents access paid web pages and APIs by completing x402 payments inside the browser session. AWS made the integration available on AWS Marketplace after developing it with the AWS Generative AI Innovation Center Partner Agent Factory. The x402 open standard lets a server return an HTTP 402 Payment Required challenge with the price, accepted payment methods and payment address. Without payment handling, an agent’s task can stall for manual intervention.

Anchor Browser is a managed cloud browser for agents that preserves authentication and session context while navigating and recording page activity. AgentCore payments manages wallet connections, configurable spending limits and x402 transactions; Amazon CloudWatch records payment attempts, approvals, denials and settlements. When a browser session receives a 402 response, the service checks its budget, obtains a cryptographic payment proof through the configured wallet provider, and lets the browser retry the original request once. The merchant verifies and settles the payment before returning the protected content.

AWS says the integration moves payment handling out of agent code, where developers otherwise would need to parse 402 challenges, construct payment headers, manage keys and wallets, enforce budgets, retry requests and log outcomes. Keeping private keys in an agent runtime can expose them to untrusted web pages, tools or dependencies; uncontrolled retry loops can also trigger unintended payments. The browser session must retain the same context so recordings and live views reflect the actions actually taken.

The managed setup centers on an AgentCore Payment Manager, created with an authorizer type and IAM role and linked to a workload identity in Amazon Bedrock AgentCore Identity. A PaymentConnector links it to Coinbase Developer Platform or Stripe Privy; a PaymentCredentialProvider stores wallet credentials securely, and a PaymentInstrument identifies the wallet address used for funds. AgentCore also provides a Coinbase x402 Bazaar MCP server through AgentCore Gateway for discovering pay-per-use endpoints. Wallet secrets and signing stay outside the agent runtime.

To enable automatic payments, developers set Anchor Browser’s session.x402 property to true; it defaults to false. This allows real payments from the configured instrument, subject to session spending and time limits. If a challenge is malformed, no compatible payment method is available, the budget is exhausted or AgentCore rejects payment, the browser returns the original 402 response unchanged. The setting pays third-party resources, not Anchor Browser session credits. Existing Playwright, Puppeteer and Chrome DevTools Protocol workflows need no payment-specific code; requests can use page navigation, fetch or XMLHttpRequest (XHR). For x402 v2 the browser sends PAYMENT-SIGNATURE; for v1 it sends X-PAYMENT. The built-in x402 tool also supports paid API calls, including POST and PUT requests. The article’s final sentence is cut off after saying key material cannot move funds from the agent runtime.

AWS says Anchor Browser and Amazon Bedrock AgentCore payments can let AI agents access paid web pages and APIs by completing x402 payments inside the browser session. AWS made the integration available on AWS Marketplace after developing it with the AWS Generative AI Innovation Center Partner Agent Factory. The x402 open standard lets a server return an HTTP 402 Payment Required challenge with the price, accepted payment methods and payment address. Without payment handling, an agent’s task can stall for manual intervention.

Anchor Browser is a managed cloud browser for agents that preserves authentication and session context while navigating and recording page activity. AgentCore payments manages wallet connections, configurable spending limits and x402 transactions; Amazon CloudWatch records payment attempts, approvals, denials and settlements. When a browser session receives a 402 response, the service checks its budget, obtains a cryptographic payment proof through the configured wallet provider, and lets the browser retry the original request once. The merchant verifies and settles the payment before returning the protected content.

AWS says the integration moves payment handling out of agent code, where developers otherwise would need to parse 402 challenges, construct payment headers, manage keys and wallets, enforce budgets, retry requests and log outcomes. Keeping private keys in an agent runtime can expose them to untrusted web pages, tools or dependencies; uncontrolled retry loops can also trigger unintended payments. The browser session must retain the same context so recordings and live views reflect the actions actually taken.

The managed setup centers on an AgentCore Payment Manager, created with an authorizer type and IAM role and linked to a workload identity in Amazon Bedrock AgentCore Identity. A PaymentConnector links it to Coinbase Developer Platform or Stripe Privy; a PaymentCredentialProvider stores wallet credentials securely, and a PaymentInstrument identifies the wallet address used for funds. AgentCore also provides a Coinbase x402 Bazaar MCP server through AgentCore Gateway for discovering pay-per-use endpoints. Wallet secrets and signing stay outside the agent runtime.

To enable automatic payments, developers set Anchor Browser’s session.x402 property to true; it defaults to false. This allows real payments from the configured instrument, subject to session spending and time limits. If a challenge is malformed, no compatible payment method is available, the budget is exhausted or AgentCore rejects payment, the browser returns the original 402 response unchanged. The setting pays third-party resources, not Anchor Browser session credits. Existing Playwright, Puppeteer and Chrome DevTools Protocol workflows need no payment-specific code; requests can use page navigation, fetch or XMLHttpRequest (XHR). For x402 v2 the browser sends PAYMENT-SIGNATURE; for v1 it sends X-PAYMENT. The built-in x402 tool also supports paid API calls, including POST and PUT requests. The article’s final sentence is cut off after saying key material cannot move funds from the agent runtime.