Anchor Browser with Agentic Payments lets agents automatically pay for x402-protected pages and APIs, according to AWS. Developed with the AWS Generative AI Innovation Center Partner Agent Factory, the offering is available on AWS Marketplace and integrates with Amazon Bedrock AgentCore payments. These capabilities are described in the single supplied AWS article.

When access requires payment

AWS describes x402 as an open standard for machine-to-machine payments over HTTP. A protected resource returns HTTP 402 Payment Required with a challenge specifying the amount, accepted payment methods and payment address. Without a way to pay, an agent's task can stall and require human intervention.

Anchor Browser supplies managed cloud browser sessions that preserve authentication state and support navigation, network capture, recordings and live views. Payment stays within the same session, with recordings covering the initial request, the 402 challenge, payment and content delivery. AWS says the built-in x402 tool requires no changes to existing Playwright, Puppeteer or Chrome DevTools Protocol workflows.

Budgets and credentials in a managed layer

AgentCore payments is described as a fully managed capability for discovering, accessing and paying for APIs, MCP servers and web content. It handles wallet connectivity, processes x402 payments and enforces configurable spending limits at the infrastructure layer. Attempts, approvals, denials and settlements are observable through Amazon CloudWatch. Payments are denied once a session reaches its spending limit.

The article identifies several burdens of building a payment stack: parsing challenges, constructing proof headers, handling merchant variations, managing credentials, preserving request context during retries, ensuring idempotency and tracking budgets across concurrent executions. Inadequate spending controls or runtime isolation can expose credentials or allow unintended spending. In the described architecture, the agent retains a budget session and x402 tool, while authentication, wallet secrets, signing, limits and observability move into the managed layer.

From configuration to content delivery

A Payment Manager coordinates operations for an AWS account. Creating it requires an authorizer type and IAM role; AgentCore then provisions a workload identity in AgentCore Identity. A PaymentConnector links Coinbase Developer Platform or Stripe Privy, a PaymentCredentialProvider stores provider credentials, and a PaymentInstrument identifies the funding wallet address. AgentCore also exposes a curated Coinbase x402 Bazaar MCP server through Gateway for endpoint discovery.

Starting a browser session with x402 enabled creates a dedicated AgentCore PaymentSession tied to a payment instrument and budget. When a 402 challenge arrives, the browser selects a compatible payment method. AgentCore checks the spending limit, obtains a signature through Coinbase CDP or Stripe Privy and returns cryptographic proof. Key material is not exposed to the browser or agent runtime; wallet credentials remain with AgentCore and the configured wallet provider.

The browser adds the proof in PAYMENT-SIGNATURE for x402 v2 or X-PAYMENT for x402 v1, then retries the original request exactly once. In the article's step-by-step account, the merchant validates the proof, settles the transaction on-chain and returns the content. A later passage attributes settlement to AgentCore payments, leaving the precise division of settlement responsibility unclear.

Activation, failures and billing

Setup requires a valid Anchor Browser API key. The session.x402 property defaults to false; setting it to true authorizes real payments from the configured payment instrument. Session spending and expiration limits still apply. The supplied article does not specify their numerical values or durations.

Automatic challenge handling covers document navigation, fetch and XMLHttpRequest. The x402 tool also supports paid API calls using POST, PUT and other methods without application code constructing payment headers, managing wallets or implementing payment retries. A malformed merchant response, no compatible network, an exhausted budget or an AgentCore rejection causes the original 402 response to be returned unchanged for automation code to handle.

The x402 property covers third-party resources only: it neither replaces Anchor credits nor pays for browser session time. Separately, AWS says Anchor Browser bills third-party x402 charges in credits on the same invoice as browser time. The article presents this consolidation as removing the customer's need to manage separate crypto custody, monitor a USDC balance or reconcile on-chain settlements for finance.

Source: AWS article on Anchor Browser and AgentCore payments.