AgentCore Payments Goes to Preview: AWS Hands Agents a Wallet With Coinbase and Stripe
- Jun 11
- 2 min read
On May 7, 2026, AWS opened Amazon Bedrock AgentCore Payments in preview. The capability lets an autonomous agent access and pay for APIs, MCP servers, web content, and other agents without a hand-built billing integration.
Launch partners
Two partners ship at preview. Coinbase provides CDP wallets and the x402 Bazaar MCP server, which exposes over ten thousand monetizable endpoints. Stripe integrates the Privy wallet. The two paths give developers a choice between a crypto-native wallet flow and a Stripe-grounded flow without changing the agent code.
What the payment lifecycle looks like
Wallet authentication using either Coinbase CDP or Stripe Privy
Session-level spending limit configuration so the agent cannot exceed a budget you set
Autonomous transaction execution that negotiates payment over the x402 protocol
Spending limit enforcement at the infrastructure layer, not just in the agent prompt
Full observability through the existing AgentCore logs, metrics, and traces stack
Preview regions
The preview is available in US East (N. Virginia), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Sydney). If your agent runs outside those regions, you need to either deploy in one of them or wait for broader availability.
The wider May AWS push
AgentCore Payments did not land alone. The same window also brought AgentCore Runtime supporting bring-your-own file system from Amazon S3 Files and Amazon EFS, AgentCore Browser adding OS-level interaction capabilities, AgentCore landing in AWS GovCloud (US-West), and AgentCore expanding to the South America (Sao Paulo) Region.
Why this is the missing primitive
Until AgentCore Payments, paid tool use meant either passing API keys through the agent (which makes spending hard to control), or building a custom billing service per agent. Neither scales to an agent that needs to dynamically discover and pay for new tools at runtime. Programmable wallets with infrastructure-level spending limits change that, and they are the precondition for paid MCP servers and agent-to-agent compensation to actually work in production.



