On August 18, 2026, AWS took Amazon Bedrock AgentCore payments from preview to general availability — a managed service that lets any developer wire autonomous payment into an AI agent “with a few lines of code.” For merchants, the news isn’t the wallet plumbing. It’s who AWS says will use it: browser agents built to get past your paywall, and shopping agents that expect to pay through your MCP server the way Travala already lets them book hotels inside a Claude chat.

What actually shipped

AgentCore payments launched in preview in May 2026 with Coinbase-only, x402-only support. At GA, per AWS’s own devguide, it adds:

  • A second wallet provider — Stripe (via Privy), alongside Coinbase — both stablecoin wallets purpose-built for microtransactions “often in cents.”
  • A second protocol — the Machine Payments Protocol (MPP), alongside x402. Both ride HTTP’s 402 Payment Required status code, so AgentCore now abstracts either one behind a single integration.
  • An “upto” x402 scheme — an agent commits to a spending ceiling instead of a fixed price, unlocking pay-per-inference and metered pricing rather than only flat per-call charges.
  • A discovery layer — a “Coinbase x402 Bazaar” MCP server, reachable through AgentCore Gateway, that the devguide says exposes “10,000+ pay-per-use x402 endpoints” developers can browse and wire up directly.

The guardrail merchants should understand

Every transaction runs inside a PaymentSession — AWS’s term for a scoped payment context with a configurable budget cap (maxSpendAmount, a currency) and an expiry. The check happens “at the infrastructure layer,” before signing: once a session hits its cap or expires, AWS says further payment requests are simply denied. That’s the same bounded-mandate shape showing up across the industry’s other agentic-payment rails this year (Binance’s agentic sub-accounts, Cloudflare Wallets’ per-purchase caps, Mastercard’s Agent Pay) — a spending limit an agent cannot exceed, set by whoever funds the wallet, not by the agent itself.

Why this is a merchant story, not just a wallet story

AWS’s own “Get started” section names the use cases customers are already shipping, and two are squarely about access, not novelty payment tech. Nishit Sawhney, AWS Edge Services’ GM, put it plainly in the announcement: “Publishers spent years building paywalls. Now AI agents need to get through them.” AWS is positioning CloudFront and AWS WAF as the control plane that lets a publisher decide “which agents can access what content, at what price” — verified with x402 at the edge. Cloudflare’s Stephanie Cohen makes the same pitch for its Monetization Gateway in the same post.

That’s the paywall side. The storefront side is Travala: the travel marketplace integrated AgentCore payments directly into its Travala Travel MCP server, so an agent inside Claude can resolve availability and pay for a hotel booking in one conversational flow — no browser handoff. That is the shape of the transaction AgentReady exists to check: not whether your product page reads well to a crawler, but whether an agent that shows up funded and ready to buy can actually complete the purchase against your catalog and checkout.

FAQ

What is Amazon Bedrock AgentCore payments?

It’s a fully managed AWS service that lets AI agents pay for paid APIs, MCP servers and web content using stablecoin wallets (Coinbase or Stripe/Privy), with spending caps enforced automatically before any payment is signed. It reached general availability on August 18, 2026, after launching in preview in May 2026 with Coinbase-only support.

Does AgentCore payments replace x402 or MPP?

No — it’s a client-side orchestration layer that speaks both. AgentCore payments supported only x402 in preview; at GA it added the Machine Payments Protocol (MPP), so a developer integrates once and the service handles whichever HTTP 402 challenge a merchant’s server returns.

Do I need to integrate with AWS to accept these payments?

No. AgentCore payments is the buyer-agent side of the transaction. A merchant only needs to speak the underlying open protocol — a standard x402 or MPP 402 challenge-response, as covered in our MPP breakdown — or expose an MCP server an agent can pay through directly, the pattern Travala already shipped.

Sources

An agent that shows up pre-funded and ready to pay is only a sale if your catalog and checkout can actually resolve one — which is exactly what a free AgentReady scan checks.