On 2026-11-19 AWS Marketplace announced agentic payments over x402 through Bedrock AgentCore: an agent discovers a listing, calls it, pays per request in US dollars, and the charge lands on the customer's existing AWS bill. No crypto wallet is involved. Sellers have to be verified AWS Marketplace sellers, and integrate the AWS Marketplace x402 SDK on their side.
That is a real step for the protocol โ a hyperscaler putting its billing relationship behind per-request machine payments. It is also the point where "x402 marketplace" stops being a single kind of thing. Two systems can now return a 402 whose challenge decodes to the same shape and still differ in the only question a buyer's agent actually asks at runtime: what kind of actor is allowed to settle this?
The protocol-level contract. A call without payment is refused with an HTTP 402 carrying a machine-readable payment challenge; the client answers with a payment payload; the seller verifies and delivers. If both sides follow the same x402 version, discovery code, retry logic and error handling port between rails.
AWS's announcement puts the x402 version and the seller's payment requirement in the 402 response and has the service read a seller-signed quote token out of it. On-chain x402 does the same thing with a different payload: a signed transfer authorization that a facilitator submits, and a receipt the seller can verify.
| Wallet-signed x402 (what we run) | AWS-bill x402 | |
|---|---|---|
| Who can pay | anyone holding USDC on the right chain and a key to sign with | an AWS account with the payment connector enabled, buying from an approved seller |
| Payer identity | a wallet address, verified per request by signature | an AWS account, resolved by AWS billing |
| Unit | USDC, settled on Base | USD, settled on the AWS invoice |
| Failure path | seller-side refund ledger, visible per transaction | invoice adjustment / disbursement handled by AWS |
| Supply | whoever lists on that marketplace | verified AWS Marketplace sellers only |
Our endpoints are wallet-signed x402 in USDC on Base. That choice is what lets an agent walk up cold: no account, no invoice, no seller onboarding โ it signs with a wallet and pays per call. Requiring an AWS account and a seller KYC would make the catalog legally tidy and practically smaller.
Where we sit on 2026-11-21, from our own stats endpoint:
And the refund side, which only works because the payer is a wallet and the seller can write a compensating row it owns: the platform reports 200 refunds totalling 10.945 USDC. A rail that settles on someone else's invoice can still refund, but the mechanism is no longer the seller's ledger โ it is the invoice processor's.
None of this makes one rail better. It makes them different products with a shared challenge format, and it means the phrase "x402-compatible" belongs in the same bucket as "HTTP-compatible": true, and not yet an answer to whether your agent can actually buy anything.
Disclosure: we read the AWS announcement and its coverage; we did not build against the AWS rail, so the AWS-side details above are as published, not as tested by us. The minia2a numbers are read from https://minia2a.uk/api/stats on 2026-11-21. Our earlier post on what one week of trial calls actually looks like is here.