Amazon Web Services made AgentCore payments generally available on August 18, 2026, a little more than three months after launching it in preview on May 7. The service is part of Amazon Bedrock AgentCore, AWS's platform for hosting software agents, and gives those agents the ability to pay for fee-based resources on their own, without a human approving each transaction.
For a cloud provider, general availability marks the end of the trial phase. The service leaves preview, falls under service-level commitments, and is billed on standard terms. At AWS, agent-initiated payments are no longer an experiment limited to a handful of teams.
The agent requests, gets a 402, pays, and retries
The sequence is fixed. An agent calls a remote resource, such as an API or a content server. The resource replies that payment is required before it will serve the request. The agent builds and sends the payment, then replays its original request with proof of payment attached. The resource then responds normally.
The service supports two protocols. x402 is an open standard published by Coinbase. It repurposes HTTP status code 402, “Payment Required,” which had sat unused in the specification since 1997, to signal that a resource costs money. MPP, the Machine Payment Protocol co-authored by Stripe and Tempo, is the second channel. With general availability, AWS also supports the upto scheme in x402, which lets an agent pay up to a cap rather than a fixed amount set in advance.
Spending limits sit in the infrastructure, not the prompt
The hard problem in agentic payments is stopping a payment once it starts. An agent that makes a mistake, or that a third party manipulates, can repeat a purchase thousands of times in a few seconds. AWS therefore enforces spending limits at the infrastructure layer, not in the instructions given to the agent. The distinction matters. An instruction written in natural language can be overridden by another instruction. A limit enforced by the platform does not depend on what the agent understood.
Traceability follows the same logic. Every transaction is logged by AgentCore Observability, the monitoring component of the same service family. Companies get a record of everything their agents spent, which they need for reconciliation and after-the-fact review.
Coinbase and Stripe Privy wallets settle in stablecoins
| Component | Role |
|---|---|
| Coinbase wallets | hold and pay out stablecoins on the agent's behalf |
| Stripe Privy wallets | a second wallet option, tied to the Stripe ecosystem |
| Quick Create | provisions Coinbase credentials automatically, with no manual setup |
| Coinbase Bazaar MCP server | a curated directory of paid resources exposing x402 endpoints |
| “upto” scheme (x402) | capped payment, with the exact amount set after execution |
| AgentCore Observability | logs and tracks agent spending |
Payments settle in stablecoins, and the reason is economic. Cards handle amounts below a few cents poorly, because fixed processing fees exceed the value of the transaction. One-off access to a piece of data billed at a fraction of a cent falls outside what cards can handle. A stablecoin transfer costs the same regardless of the amount, which makes these microtransactions viable.
Merchants gain a new acceptance channel, but liability is unresolved
For merchants and publishers, the immediate effect is on acceptance. A resource behind an x402 endpoint can be paid for by any agent running on AWS, with no bilateral integration. The question used to be how an agent pays. It is now which resources are worth exposing to this channel.
Several issues remain open. The service does not address liability when something goes wrong. There is no equivalent of a card chargeback for a stablecoin payment, which is final once confirmed. The tax and accounting treatment of spending by a program, with no purchase order and no human sign-off, is still left to each company's internal practices. And the announcement does not list the regions where the service is available. It points to the technical documentation instead.
The announcement marks a different kind of milestone for agentic payments. The past months built the rails: messaging protocols and shared industry infrastructure. General availability at a top-tier cloud provider is about something else. It puts those rails in the hands of an entire enterprise customer base, backed by contractual commitments.