AWS: Bedrock AgentCore Payments brings x402 protocol and stablecoins for AI agents

Amazon Web Services introduced on May 7, 2026, Amazon Bedrock AgentCore Payments — the first managed infrastructure enabling AI agents to autonomously pay for and access external resources. The service is in preview and available in four AWS regions: US East (N. Virginia), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Sydney).

How does the x402 protocol work inside the agent loop?

AgentCore Payments uses the open x402 protocol, an HTTP-native standard for stablecoin micropayments. When an agent accesses a resource and receives an HTTP 402 “Payment Required” response, the payment processor inside AgentCore authenticates the configured wallet address and executes the transaction — all within the same agent execution cycle. The key consequence is that agent reasoning is not interrupted and the agent can in a single pass pay for an API, MCP server, or paywalled article. AWS states that x402 is the first supported protocol in preview, with plans to add others.

Who are the Coinbase and Stripe partners?

Coinbase provides the CDP wallet infrastructure and authored the x402 specification; it covers stablecoin payments as the primary mechanism. Stripe participates through its acquired partner Privy and offers an alternative wallet infrastructure, positioned toward future fiat currency support. The partnership of two major payment players gives AgentCore Payments both a crypto and a traditional path simultaneously. The end user must explicitly authorize agent wallet access before the agent can execute any transaction.

What are the security and operational controls?

AWS has built in per-session spending limits that enforce budget constraints for each individual agent session. All transactions are visible through the AgentCore console and metric logs, providing full observability and auditability. AWS describes three user categories in the announcement: financial research agents paying for paywalled publications, coding agents calling specialized APIs and MCP servers, and future commercial scenarios such as booking flights and hotels. This step defines a new category of agent economy in which payment is embedded at the infrastructure level.