Home / Blog / why-usdc-on-base-for-ai-billing
Why USDC on Base is the right primitive for AI billing
Three things have to be true at once: settlement faster than the call, fees smaller than the call, and the rails accessible to a process (not just a person). USDC on Base hits all three.
What we actually need
Billing for AI tools is not "billing" in the SaaS sense. The thing being billed is a single LLM call, a single scrape, a single TTS render. Three properties matter:
1. Settlement faster than the call itself. A $0.001 inference call that takes 300ms to execute cannot wait 2 days for funds to clear. The settlement step has to be in the same order of magnitude as the call. 2. Fees smaller than the call itself. If the payment rail charges $0.30 minimum, you cannot price the call at $0.001. The fees have to scale down to fractions of a cent. 3. The rail has to be reachable by a process, not just by a person. No human pressing "approve" on every call. No card form. No 2FA challenge. The agent decides, the agent pays, the call returns.
USDC on Base hits all three.
Settlement speed
Base is an L2 — block times are ~2 seconds. A transfer of USDC settles in one block in the happy case. For internal-ledger settlement (which is what Spawnpay does for sub-cent calls), it is instantaneous because the on-chain settlement is batched at deposit/withdraw boundaries.
Fees
Base gas is fractions of a cent. USDC is a stablecoin so the unit is human-currency. The economic floor of a "real" on-chain Base transaction is around $0.001. For sub-cent ledger writes, Spawnpay batches and the unit cost approaches zero.
Programmable, agent-reachable
Wallets are HD-derived. Signing is a key operation. No card form, no 3DS challenge, no IP gating, no chargeback. An agent process can authenticate to a Spawnpay key the same way it authenticates to any other API — with a bearer token in a header.
What about other chains
- Ethereum mainnet — gas too high. Sub-cent calls dissolve into gas.
- Polygon — fine, but USDC liquidity on Base is now bigger and more accessible.
- Solana — fine, but EVM tooling has a wider developer base.
- Arbitrum — fine, similar profile to Base, Spawnpay may add as a second-chain option later.
Base wins for the AI-billing use case because the L2 has a credibly-tied L1 (Ethereum), it is operated by Coinbase (institutional comfort + USDC native), and Spawnpay's existing tooling targets EVM.
What about non-crypto
The honest answer: nothing else fits.
Cards have a floor charge. ACH has multi-day settlement. PayPal has a card-form UX. Wire is over $5 per. Card-not-present at scale has a chargeback rate that wipes the unit economics. None of those work for the workload.
If a non-crypto rail with sub-cent fees and sub-second settlement and process-grade access ever ships, Spawnpay will adopt it. So far, nothing has.
What to try
Open https://spawnpay.ai/playground, pick fxtwitter, click RUN. You will see the live envelope: which provider, which path, how much it cost, what was returned, with the upstream response inline. No signup, no key. The full mechanic is visible.
For paid calls, https://spawnpay.ai/quickstart ships a config block. $7 free credit on first wallet creation.