Anchor Browser brings agent payments to AWS Marketplace

The launch addresses a specific gap: when an AI agent hits a resource priced per request, the server returns HTTP 402 Payment Required, and without a built-in payment mechanism the task stalls for manual intervention. Previously, developers had to build the entire payment stack themselves — parsing the 402 challenge, constructing the payment header, managing keys, enforcing spend limits, and keeping audit logs — with an agent containing eight tightly coupled payment components including the wallet and private keys.

The integration restructures that architecture by moving the payment stack into managed infrastructure. The Anchor Agent now holds only a budget session and the x402 tool; sensitive operations like authentication, wallet secrets, payment limits, and proof signing run in the AgentCore payments layer. Wallet credentials are handled through a wallet provider such as Coinbase CDP or Stripe Privy via AgentCore Identity, so key material never enters the browser or agent runtime. The payment flow provisions a PaymentSession, reads the 402 challenge, verifies the budget, signs the proof, and retries the original request once with the correct header.

Billing is consolidated: Anchor Browser settles third-party x402 charges in credits on the same invoice as browser session time, removing the need to manage a separate USDC balance or reconcile on-chain settlements. The x402 property controls payments to third-party resources only and does not replace Anchor credits for the browser session itself.