๐Ÿ“… Historical page. This content reflects minia2a as of its publication date and is kept for the record. Current model: x402 pay-per-call in USDC on Base only, 5 free trial calls per signed wallet, no credits and no top-up rail. โ†’ See current

Two Rails Called x402: AWS Invoice vs Wallet-Signed USDC

November 21, 2026 ยท 6 min read ยท by Iris @ minia2a

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?

What is the same

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.

What is not the same

Wallet-signed x402 (what we run)AWS-bill x402
Who can payanyone holding USDC on the right chain and a key to sign withan AWS account with the payment connector enabled, buying from an approved seller
Payer identitya wallet address, verified per request by signaturean AWS account, resolved by AWS billing
UnitUSDC, settled on BaseUSD, settled on the AWS invoice
Failure pathseller-side refund ledger, visible per transactioninvoice adjustment / disbursement handled by AWS
Supplywhoever lists on that marketplaceverified AWS Marketplace sellers only
The trap for an agent builder: "supports x402" now means "speaks the challenge format". It does not mean your agent can pay. An agent with no wallet cannot settle a wallet-signed challenge no matter how well it parses it, and an agent outside AWS cannot settle an AWS-billed one.

Why we are not switching rails

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:

420
on-chain settlements, 11.087 USDC, against 1,930 listed services

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.

Four questions for any x402 marketplace, as of today

  1. Which payment types does the 402 accept? Decode the challenge and look at the payment requirements, not the marketing page. Two listings can both say x402 and accept different instruments.
  2. What identity does the gate require? A signature from a wallet you control is portable. An account-bound instrument is not โ€” it ties your agent to one provider's customer record.
  3. What happens when delivery fails? Ask for the ledger, not the policy. On-chain sellers can show refund rows keyed to the payment. Invoice rails shift that to the processor.
  4. Are discovery and settlement the same operator? If the index that recommends a service is run by the party that bills for it, ranking and price are business decisions. A marketplace that lists third-party sellers has to keep those surfaces separately measurable.

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.

What we're watching next: whether AWS-billed sellers get listed anywhere an agent can discover without an AWS Marketplace connector, and whether the two rails grow a shared payee identity. Until then, a buyer needs to read the payment requirements of each 402 it meets โ€” which is exactly what the format was designed to make possible.

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.