Skip to content
NewsProduct launch

AWS ships AgentCore payments so AI agents can pay x402 paywalls without a private key

· by Pondero Newsdesk

The short version

Amazon Bedrock AgentCore payments now pairs with Anchor Browser to detect HTTP 402 Payment Required responses and pay them automatically, signing the transaction outside the agent's own runtime.

AWS ships AgentCore payments so AI agents can pay x402 paywalls without a private key

When an AI agent hits a metered API or a paywalled page, the server can return HTTP 402 Payment Required, and until now that has meant the task stops and a human has to step in. AWS published a guide on October 13 showing a fix: Amazon Bedrock AgentCore payments paired with Anchor Browser, a cloud browser-automation vendor, completes the 402 payment and resumes the task without a human, and without ever handing a wallet's private key to the agent's own code, according to AWS's own walkthrough.

What AWS built

Anchor Browser runs each agent session inside a managed cloud browser, which AWS says it developed with the AWS Generative AI Innovation Center's Partner Agent Factory and now lists on AWS Marketplace, per the AWS post. A developer flips one session flag, session.x402, to true. From there, when a site responds with a 402 challenge under the open x402 protocol, AgentCore payments checks the request against a configured spending limit, signs a cryptographic payment proof through a connected wallet provider (Coinbase Developer Platform or Stripe Privy), and the browser retries the original request with that proof attached as a PAYMENT-SIGNATURE or X-PAYMENT header, per AWS's payment-flow description. The merchant settles the transaction and serves the content; the agent never sees a key.

The split matters because of where the signing happens. AWS's own writeup frames the risk directly: a private key inside the same runtime as an agent that is also parsing untrusted web pages and calling third-party tools is a key that can leak. Moving the signing step into AgentCore's managed layer, per the AgentCore payments developer guide, means the agent only ever holds a budget session and a built-in x402 tool, not a wallet.

A 402 response no longer has to stop a pipeline

For teams building agents that scrape research reports, pull from metered data APIs, or call paid Model Context Protocol servers, this closes a specific gap: a per-request paywall used to force either a pre-negotiated subscription or a human in the loop. AWS also built in a discovery layer, a Coinbase x402 Bazaar MCP server surfaced through AgentCore Gateway, so an agent can find x402-payable endpoints programmatically rather than hardcoding them. The guardrail that makes unattended operation defensible is the spending limit enforced at the infrastructure layer, not inside the agent, which AWS says blocks the failure mode where a retry loop or a prompt injection racks up charges before anyone notices.

The tradeoff is that this ties a team's autonomous-payment capability to AWS's own AgentCore stack and to one of two supported wallet providers. A team already running agents outside Bedrock, or that wants a different wallet provider, does not get this integration for free.

What to watch next

Watch whether other browser-automation vendors beyond Anchor Browser pick up the same AgentCore payments integration, and whether AWS extends support for x402 payment schemes or wallet providers beyond Coinbase CDP and Stripe Privy. This also lands squarely in the broader contest between x402 and competing agent-payment approaches like ACP and AP2; a concrete, shipping integration from a major cloud gives x402 a usage data point the rival specs do not yet have.

Sources