Amazon Bedrock AgentCore Payments went into preview today. It runs on x402, settles in USDC on Base in 200 milliseconds, and ships with a curated directory of 10,000 paid endpoints. The pattern, three rails from three hyperscaler camps in one week, is now the story.

We published State of the Stack: Agentic Commerce 2026 on May 5. Two days later, the Solana Foundation and Google Cloud opened Pay.sh, the first commercial rail for AI agents to pay for enterprise APIs in stablecoins. Today, Amazon Web Services, Stripe, and Coinbase opened the second. The product is called Amazon Bedrock AgentCore Payments. It is in preview. It does the same job from a different stack.

In between, Mastercard and Google open-sourced Verifiable Intent, the commitment governance layer that sits above any payment rail. Three hyperscaler camps shipped agent payment infrastructure inside the same calendar week. The build-out we wrote about in State of the Stack is now visible at the operator level.

AgentCore Payments is a capability inside Amazon Bedrock AgentCore, AWS's managed runtime for autonomous agents. The new piece lets an agent discover, authenticate, and pay for digital services inside a single execution loop. The first release covers APIs, MCP servers, web content, and other agents. Future versions are expected to extend to merchant payments and travel bookings.

The mechanics are clean. A developer connects their agent to a funded payment source, either a Coinbase CDP wallet or a Stripe-owned Privy wallet, and sets a session-level spending limit. When the agent calls a paid endpoint and receives an HTTP 402 response, AgentCore handles the x402 negotiation, signs the payment, settles in USDC on Base, and returns proof of payment to the endpoint. The agent never holds private keys. Spending caps are enforced deterministically at the infrastructure layer.

Settlement runs in around 200 milliseconds at fractions of a cent per transaction. That latency budget matters. Pay-per-request inside an agent's reasoning loop assumes the agent will pay hundreds of times per task without stalling.

Discovery is the less obvious piece. AWS bundled the Coinbase x402 Bazaar as an MCP server available through the AgentCore Gateway. The Bazaar exposes more than 10,000 pay-per-use x402 endpoints that agents can search and call by name. Two named preview customers are public: Heurist AI, building a financial-research agent, and Warner Bros. Discovery, exploring premium content monetization for agents.

Three hyperscaler-class rails opened between May 5 and May 11. They share more than they differ.

All three settle in stablecoins. All three use open protocols rather than proprietary card schemes. All three treat the wallet, not an API key, as the agent's identity. None of them run on interchange. Solana settles on Solana with USDC. AgentCore settles on Base with USDC. The Verifiable Intent layer that Mastercard open-sourced operates above all of them.

The differences are about distribution and wallet ownership. Pay.sh distributes through the Google Cloud Console and concedes the wallet to the Solana Foundation. AgentCore Payments distributes through Amazon Bedrock and gives the developer a choice of two wallets, one from Coinbase, one from a Stripe acquisition. Mastercard and Google did not build a rail; they built the trust record that any rail can pin commitments to.

The agent payments stack is forming the way the early web payments stack did. Open protocol at the bottom. Wallets and identity in the middle. Hyperscaler distribution at the top. The card networks are not absent from this stack, but they are not the gateways. So far, the gateways are cloud platforms.

Both rails run on x402. Both settle in USDC. The differences sit at three layers.

The first is the wallet relationship. Solana Foundation owns the wallet on Pay.sh. The Cloud Console distributes it. On AgentCore Payments, the wallet is either Coinbase's CDP product or Privy, which Stripe acquired in 2025. End users can fund a Privy wallet directly with a credit or debit card, which collapses a step. Pay.sh requires the user to fund a Solana wallet in stablecoin first.

The second is the settlement chain. Pay.sh settles on Solana mainnet. AgentCore Payments settles on Base, the Coinbase Layer 2 built on Ethereum. Both target sub-second finality. Base ties the rail to Coinbase's existing custodial and compliance stack. Solana ties Pay.sh to a foundation, not a custodian.

The third is discovery. Pay.sh ships with 75 enterprise APIs curated alongside Google Cloud services. AgentCore Payments ships with the Coinbase x402 Bazaar wired into the gateway, which exposes 10,000 endpoints out of the gate. Two orders of magnitude. The Bazaar is a thinner curation, but it changes what an agent can find without a developer pre-wiring the integration.

Stripe's role has a quieter dimension. Privy is the visible piece. Stripe's machine-native payment protocol, MPP, is the natural complement to x402 for agent payments that need card-rail settlement rather than stablecoin. AgentCore is x402-first today. Whether MPP gets surfaced inside AgentCore in a future release is the layered question worth tracking.

State of the Stack named six pieces of infrastructure agentic commerce needs at scale: commitment governance, identity, dispute resolution, settlement, observability, and the audit layer. AgentCore Payments addresses three.

Settlement is done. Identity has a partial answer in the wallet-as-credential model and a stronger answer in AgentCore's session-bound spending caps. Observability is the strongest improvement over Pay.sh: every payment flows through the same logs, metrics, and traces developers already use in AgentCore, which gives the principal a deterministic view of what the agent spent and where.

Dispute resolution is still missing. A stablecoin payment on Base is final. If an agent pays a paywalled API for a response the principal disputes, there is no chargeback path. The agentic dispute crisis we wrote about in March is not closer to resolution this week than it was last week.

Commitment governance is also still missing inside the rail itself. AgentCore enforces spending caps. It does not enforce whether the agent should be spending against a particular mandate, on whose authorization, with what audit trail visible to the principal. The Mastercard and Google Verifiable Intent release closed the cryptographic record of what a consumer authorized. Composing that with AgentCore's spending caps is a developer exercise nobody has done in public yet. The pieces are on the table. The integration is not.

The audit layer is still platform-level rather than rail-level. AWS gives developers logs. Coinbase gives them on-chain transaction data. Nobody gives the principal a unified view across the agent's reasoning trace, payment activity, and outcome attribution. That gap is where the next wave of agentic commerce platforms gets built.

Three signals will tell us whether AgentCore Payments scales past preview or stays a developer demo.

The first is preview volume. Heurist AI and Warner Bros. Discovery are the named early customers. Heurist's financial-research agent is the more interesting tell because it has a clear pay-per-API loop. We expect to see public transaction volume figures within 90 days. If those numbers stay below five-digit transaction counts, the launch is a positioning play. If they cross into six digits, AgentCore has product-market fit inside Bedrock.

The second is protocol consolidation. AgentCore Payments runs on x402. So does Pay.sh. So does Nevermined, which we covered when it shipped agent card payments on the same protocol. The protocol race we mapped in the Q1 protocol map is consolidating faster than we expected. Linux Foundation owns the x402 specification. The interesting question is whether MPP becomes a peer standard for card-rail-backed agent payments or gets absorbed into x402's roadmap.

The third is regulatory response. Two hyperscalers now operate gateways that move USDC on behalf of autonomous principals, in production-class environments, across borders. Money transmission licensing, sanctions screening, and consumer protection rules were written for human-initiated transactions. The questions for AWS specifically are about how Coinbase's compliance stack scales when an agent, not a person, is the originating party. The questions for Stripe are about how Privy's KYC posture differs when funding sources include both stablecoin and card. Regulators have not yet weighed in publicly on either rail.

The competitive layer is the last signal. Visa, Mastercard, and the legacy processors have invested in agent payments through their existing card rails and selective stablecoin pilots. Neither Pay.sh nor AgentCore Payments sits inside those rails. Whether the networks run their own gateway, license to one of these, or wait for regulatory clarity is the open question of the next quarter.

Three hyperscaler camps shipped agent payment infrastructure in one week, on one protocol, with one settlement asset. Which gateway becomes the default when this scales past preview?

Charlie Major is a Product Development Manager at Mastercard. The views and opinions expressed in Major Matters are his own and do not represent those of Mastercard.