Every x402 payment DimeBox accepts settles in USDC, on Base. Both choices are specific and deliberate — not "any stablecoin on any chain would do." Here's what each one buys.
DimeBox's prices are fixed in dollar terms: a draft currently costs $0.02, a send $0.01, a priority receive $0.03, and claiming a custom inbox name $1.00 (these are read live from config, so check the API reference for the current numbers rather than treating any figure here as fixed forever). Pricing in a volatile asset would mean either the dollar price drifts with the market every time the asset moves, or the server has to re-quote the asset amount on every single request just to keep the dollar price fixed. USDC removes that problem by being pegged to the dollar in the first place — the amount quoted in a PAYMENT-REQUIRED header is, to a close approximation, the price in cents.
x402 charges work at the level of individual API calls — cents, not dollars. That only makes sense on a network where the cost of actually moving the money is a small fraction of the amount being moved. A chain with high gas fees would make a $0.01 payment absurd: the fee to execute the transfer could exceed the amount transferred many times over. Base is a low-fee network built on Ethereum's security model via an optimistic rollup, which keeps the cost of settling a few-cent payment low enough that per-call pricing is actually viable rather than theoretical. This is the same economic gap discussed in why HTTP 402 sat unused for thirty years — a settlement rail cheap enough for micropayments is one of the pieces that had to exist before 402 could do real work.
DimeBox runs on two Base networks depending on environment: Base mainnet (eip155:8453) in production, where real USDC moves and real email gets sent, and Base Sepolia (eip155:84532) for testing, where the same exact flow runs against test tokens with no financial risk. The PAYMENT-REQUIRED header tells a client which network a given deployment expects — see Base Sepolia vs Base mainnet for how to point a test client at the right one and what changes, and what doesn't, between them.
From the caller's side, settling on Base doesn't mean running a node or holding ETH for gas. Under the exact scheme, the client signs an EIP-3009 authorization rather than submitting a transaction directly — the actual on-chain submission happens later, handled by a facilitator, and the signer never needs ETH sitting in the wallet just to pay for gas. See what EIP-3009 actually does for that mechanism, and x402 facilitators explained for who's doing the on-chain submission on the caller's behalf.
A card payment can be disputed and reversed weeks after the fact — chargebacks exist precisely because card settlement isn't actually final at the moment of purchase. An on-chain USDC transfer, once confirmed, is final in a much stronger sense: there's no issuing bank to call and reverse it. That's part of why DimeBox's charging rule only cares about one thing — did the route's own response come back under 400 — rather than building in any later reversal logic. The payment settling on Base and the route succeeding happen together, deliberately, so there's nothing left to unwind afterward.
An agent deciding whether to send a follow-up email, or whether a given inbound message is worth paying to prioritize, is making that decision against a fixed cost it needs to reason about in advance — not a cost that could be a different number of dollars depending on what an underlying asset did in the last hour. A stablecoin is what makes "this costs $0.01" a statement an agent's own budgeting logic can actually rely on from one call to the next, rather than a number that needs re-checking before every decision. That predictability is a prerequisite for the kind of per-call budgeting discussed in budgeting for a fleet of autonomous agents that pay their own way, not an incidental nice-to-have.
Not every caller wants to manage a wallet, fund it with USDC, and sign payments — some would rather pay with a card the way they'd pay for anything else online. DimeBox supports that too: a card-funded wallet, topped up via Stripe Checkout, authenticates with a bearer secret instead of a signed payment and is charged the same per-call prices with no 402 round trip. See no crypto wallet? how to pay AI agent APIs with a card instead for that path in detail. USDC on Base is the settlement layer underneath either way — the wallet balance itself is backed by it — but a caller using the card-funded path never has to think about networks, gas, or signatures directly.