You’re reading an issue of “The AI Economy,” my newsletter exploring the forces shaping the AI era—tracking how AI is rewriting business, work, technology, and culture. Subscribe to get expert insights and curated updates delivered straight to your inbox.
Amazon Web Services (AWS) is building the infrastructure that lets AI agents transact on behalf of humans—with their consent, of course. At its Financial Services Symposium on Thursday, the company unveiled AgentCore Payments, a set of features within Amazon Bedrock that lets AI agents access and pay for the resources they use. Built with Coinbase and Stripe, the capability is available in preview today.
“Services, tools, and content must be designed for humans and agents,” Preethi CN, AWS’s director of AgentCore, wrote in a blog post. “Agents will discover, evaluate, and pay for resources when they need, all within a single execution loop. The services that support them must be priced and consumed in that way: fractions of a cent per call, billed in real time.”
End-to-End Payment Capabilities for Agents
She acknowledged that x402, ACP, MPP, and AP2 are among the earliest protocols to explore solving this problem, yet “the infrastructure to support it at scale doesn’t exist yet.” Prior to today, developers would need to establish billing relationships with service providers, securely manage credentials, enforce spending governance, address compliance requirements, and determine the necessary orchestration logic across a fragmented landscape. “That’s months of engineering effort, and the stakes are high,” CN said. “A misconfigured payment flow doesn’t produce a bad answer; it moves real money.”
Described as “the first managed end-to-end payment capabilities for agents,” AgentCore Payments gives AI agents the…agency to transact without needing to pause and have a human provide payment information. It’s the elimination of the human-in-the-loop checkout. Still, developers don’t have to worry about agents making expensive purchases. Initially, AWS is focusing on instant micropayments that provide access to APIs, MCP servers, web content, and other agents.
“Services are rapidly shifting to pay-per-use models, AI agent web crawling surged rapidly in the past year, and these transactions are typically under $1 or fractions of a cent,” CN explained.
Some of the specific use cases AWS has in mind include agents doing research, financial analysis, browsing websites, paying for data feeds, and provisioning temporary storage resources on demand.
She emphasized that AgentCore Payments isn’t a “bolted-on module.” Rather, it’s native to Amazon Bedrock, the fully managed service for building and scaling generative AI applications, which means this payments infrastructure will be governed similarly to other actions an agent takes—same identity, gateway, and observability governance.
And micropayments are only the first type of transaction AWS is targeting. CN revealed her team is looking at “broader commerce flows where agents act on behalf of buyers, not just other agents,” such as booking flights, making hotel reservations, and completing purchases across merchant platforms on behalf of customers. This would certainly be useful with the rise of OpenClaw, NemoClaw, and the other Claw variants. That said, getting there won’t necessarily be easy, as CN says it requires “deeper integration with payment ecosystems, support for additional protocols, stronger buyer intent verification, and end-to-end observability across the full transaction lifecycle.”
Using AgentCore Payments
Developers enable AgentCore Payments through the SDK or console, then connect their agent to either a Coinbase wallet or a Stripe Privy wallet as the funding source. End users can fund those wallets with stablecoin or with fiat through a credit or debit card. The agent transacts within the spending limits the user authorizes for each session. At no point will the agent have “open-ended access” to funds, only operating with “explicit permission and within defined limits.”
Giving agents payment authority is one thing, but how will they find places to exercise it? AWS is also integrating Coinbase’s x402 Bazaar MCP server into its AgentCore gateway. Agents can use this curated list of x402 endpoints to search for, discover, and pay for services and content relevant to their tasks.
The choice of Coinbase and Stripe is itself a signal. Rather than picking a winner, AWS is hedging between two theories of how agent commerce will settle: Coinbase’s stablecoin infrastructure and the x402 protocol on one side, Stripe’s fiat-and-card rails on the other. Both companies also share something that Visa, Mastercard, and the major banks don’t—deep developer adoption. That matters because the agent economy is being built by software engineers, not by procurement teams, and those engineers already trust Stripe and Coinbase.
“There will soon be more AI agents transacting than humans, and they need money that’s built for the internet—programmable, always on, and global,” Brian Foster, Coinbase’s head of infrastructure growth and strategy, said in a statement. “We’re giving developers the full stack to build agents that move money at software speed, with the trust and compliance enterprises expect.”
That said, AWS isn’t the only one chasing agentic payments—though it’s positioning differently than most. Visa’s Intelligent Commerce Connect, unveiled last month, helps merchants accept agent-initiated transactions across multiple card networks and protocols. Mastercard’s Agent Pay, built around its Agentic Tokens, has integration partners including Microsoft Copilot and PayPal’s wallet. PayPal itself launched Agent Ready last fall to plug merchants directly into ChatGPT, Copilot, and Perplexity. Lastly, Google has its Universal Commerce Protocol and Agent Payments Protocol.
While Visa, Mastercard, and PayPal are building infrastructure for merchants to accept agent payments, AWS’s approach is to create infrastructure for AI agents to make those purchases.
Amazon Bedrock AgentCore Payments is available today in preview in the following regions: US East (N. Virginia), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Sydney). The company cautions that features and APIs could change before AgentCore Payments becomes generally available.
