What is Amazon Bedrock AgentCore payments?

It is a managed AWS service that lets an AI agent autonomously pay for paid APIs, MCP servers, web content and other agents. AWS launched it in preview in collaboration with Coinbase and Stripe, and announced general availability on 18 August 2026. The agent spends from a Coinbase or Stripe Privy stablecoin wallet that the end user funds and delegates authority over, and AgentCore handles the payment lifecycle from wallet authentication through transaction execution to spending governance and observability.

Which payment protocols does AgentCore payments support?

At preview it supported x402 only. At general availability AWS added the Machine Payment Protocol (MPP), which AWS describes as co-authored by Stripe and Tempo, so a developer can pay any MPP-compatible service without an additional line of code. AWS describes the service as protocol-agnostic: developers integrate once and work with merchants regardless of which protocol the merchant uses. AWS also added support for the 'upto' scheme within x402, which lets an agent set a spending ceiling rather than commit to a fixed price, enabling pay-per-inference and usage-metered pricing.

How does AgentCore payments stop an agent overspending?

Transactions run inside a payment session, which AWS describes as a scoped payment context for a single agent interaction with two configurable caps: a maximum spend amount in a specified currency, and an expiry time. Before signing a payment, AgentCore checks the request against the session budget and rejects requests that would push the session past its cap. AWS states that this check is deterministic and runs at the infrastructure layer, which is the design response to the fact that agents themselves are non-deterministic and can misread a response as authorisation to spend, or repeat a payment on an unexpected retry.

What does this mean for businesses that sell APIs, data or content?

It is the buying half of a market whose selling half is already being built. In the same announcement AWS quotes Nishit Sawhney, General Manager of AWS Edge Services, on Amazon CloudFront and AWS WAF giving content owners a control plane to decide which agents access what content and at what price, with payment verified at the edge over x402, and Stephanie Cohen, Chief Strategy Officer at Cloudflare, on Cloudflare's Monetization Gateway letting asset owners charge agents directly per request at a price they set. Agent traffic that a business currently blocks becomes traffic it can price.

AWS Makes Bedrock AgentCore Payments Generally Available, with x402 and MPP Support

On 18 August 2026 AWS announced that Amazon Bedrock AgentCore payments is generally available, moving a managed agent-payment service from preview into production. Agents built on AWS can autonomously pay for paid APIs, MCP servers and web content, spending from a Coinbase or Stripe Privy wallet the end user funds and delegates authority over, inside a payment session whose spend cap and expiry are enforced deterministically at the infrastructure layer. At general availability AWS added Machine Payment Protocol support alongside x402, positioning the service as protocol-agnostic.

Editor’s note: this page is built from the AWS announcement and documentation linked in the sources. AWS’s own GA post describes the preview as launching “in May” 2026, while the AWS What’s New entry for the preview sits at a 2026/04 URL. The preview date is reported here as AWS describes it. Regional availability changes over time and should be checked against the AWS documentation.

What was announced

AgentCore payments entered preview in collaboration with Coinbase and Stripe, letting agent developers equip agents to pay for paid APIs, MCP servers and content in a few lines of code. General availability adds production-oriented capability rather than a new premise.

Four changes are worth recording:

Protocol support widened. Preview supported x402. GA adds the Machine Payment Protocol, which AWS describes as “another standard for machine payments co-authored by Stripe and Tempo”, so a developer can pay any MPP-compatible service without an additional line of code. AWS frames the service as protocol-agnostic, “abstracting away the complexity so developers can integrate once and work with merchants regardless of which protocol they use”.
A spending ceiling instead of a fixed price. AWS added support for the “upto” scheme within x402, which lets an agent set a ceiling rather than commit to a fixed price. AWS describes this as unlocking pay-per-inference and dynamic pricing: a merchant serving LLM tokens, compute, or a usage-metered API can charge for what was consumed at the end of a call rather than requiring a fixed price per request. The existing “exact” scheme remains.
Credential provisioning moved in-product. A “Quick Create” option for Coinbase in the AgentCore console and CLI provisions credentials without leaving AgentCore. Stripe Privy credentials are still obtained from the Privy dashboard.
Endpoint discovery curated. AgentCore exposes Coinbase’s pay-per-use x402 endpoints as an MCP server through AgentCore Gateway. At GA that MCP server was updated to a curated list, selected by AWS on social proof, metadata richness, description quality and availability.

The controls are the substance of the release

The design problem AWS names is worth quoting directly, because it is the one every buyer-side agent deployment runs into: “Agents are inherently non-deterministic, so they can misinterpret a response as authorization to spend or repeat a payment because of an unexpected retry.”

The answer is a payment session, which AWS describes as a scoped payment context for a single agent interaction, carrying a maximum spend amount in a specified currency and an expiry time. Before signing a payment, AgentCore checks the request against the session budget and rejects anything that would push the session past its cap. AWS states plainly that “the check is deterministic and runs at the infrastructure layer”. A spend limit that lives outside the model is a materially different control from one expressed as an instruction to the model, and it is the part a finance or risk function will ask about first.

Credential handling follows the same pattern. Developer credentials sit in AgentCore Identity Secrets Manager, and AWS states that the agent does not see the raw credentials: AgentCore derives short-lived tokens from them to instruct the wallet provider to perform wallet operations such as transaction signing.

The third piece is the audit trail. AgentCore payments emits vended logs to Amazon CloudWatch and spans to AgentCore Observability, with prebuilt dashboards covering transaction success rate and average transaction value across agents, payment sessions and time periods.

Delegation, a hard spend cap, an expiry, no raw credential exposure, and a transaction log. That is recognisably the same control set a business already applies to a corporate card, expressed for an agent.

The named deployments

AWS names customers across three use cases, each with an attributed quotation in the announcement:

Paying for paywalled web content. Anchor Browser, a cloud browser automation platform for AI agents, integrated AgentCore payments so its customers can reach paid web content inside agentic workflows. Its CEO and co-founder Idan Raman is quoted on the integration and its built-in payment limits.
Pay per inference. SpreadX used AgentCore payments in its Incarna product to pay for inference through BlockRun, described as a routing and payment layer where agents pay per call over x402. BlockRun founder and CEO Vicky Fu is quoted.
Consumer booking and research. Travala integrated AgentCore payments into its travel MCP servers so end customers on agentic platforms such as Claude can book hotels conversationally in a single chat. Travala CEO Juan Otero puts the catalogue at 2.2 million properties, which is Travala’s own figure. Elsa AI and Heurist AI use the service to reach pay-per-use APIs over x402 for financial research and advisory.

Framework coverage is broad enough to matter for adoption: plugins and middleware for Strands Agents, LangGraph and OpenClaw, an AWS Agent Toolkit plugin, an AgentCore CLI, and a coding-assistant skill AWS points at Claude Code, Kiro and Codex.

The selling side is in the same announcement

The part of this release with the widest commercial reach is not the buyer-side SDK. It is that AWS published it alongside two quotations about charging agents.

Nishit Sawhney, General Manager of AWS Edge Services, describes Amazon CloudFront and AWS WAF as giving content owners “a single control plane for AI traffic, which agents can access what content, at what price, and for what use, with payment verified at the edge over the open x402 protocol”, and characterises the effect as changing the conversation “from defense to commerce”. Stephanie Cohen, Chief Strategy Officer at Cloudflare, describes Cloudflare’s Monetization Gateway letting owners of content, APIs and MCP servers charge agents directly, per request, at a price they set over x402.

Read the two halves together and the shape is a two-sided market being assembled from both ends at once: a managed way for agents to pay, and CDN-level infrastructure for merchants and publishers to charge. Both sides settle over the same protocol. For any business whose product is an API, a dataset or professional content, the practical question moves from whether to block agent traffic to what to charge it, and that is a pricing decision rather than a security one.

What it does not cover

This is machine-to-machine commerce, and it should not be read as retail agentic checkout. The transactions in scope are an agent paying for an API call, an inference, a piece of content or another agent’s service, typically at cent-level amounts, funded through stablecoin wallets. It is a different layer from a shopper’s agent completing a card purchase at a merchant, which is where the Agentic Commerce Protocol, the Universal Commerce Protocol and AP2 sit.

Two further limits are worth stating. Wallet choice is currently Coinbase or Stripe Privy, so funding runs through stablecoin rails even where the end user tops up by card. And the protocol-agnostic claim covers x402 and MPP; it is not a claim about the retail checkout protocols.

Why it matters

A hyperscaler taking an agent-payment service to general availability is a production-readiness signal rather than a pilot, and it lands the argument about protocol choice in a specific place. If the cloud platform abstracts x402 and MPP behind one integration, the question of which machine-payment protocol to back becomes less of a commitment for the developer and more of a question for the merchant on the other side. That is worth watching as more protocols reach the same abstraction.

For a business evaluating agent deployments, the useful test from this release is the one the controls imply: whether a hard spend cap, a session expiry, a delegation record and a transaction log would satisfy your own finance and risk people before an agent is given a budget. See How AI Agents Pay for the payment layer in full, x402 vs MPP for the two protocols AgentCore now spans, and The Agentic Commerce Protocol Stack for where machine-to-machine payment sits relative to retail checkout.