x402 on Base, and what the record actually shows

RoundhouseReviewed .md
In short

Base is where x402 launched in May 2025 and it held the cumulative volume lead through 2026. It has the longest-established tooling and the deepest settlement history, which also makes it the chain where the gap between gross transfer counts and verified x402 commerce is best documented.

Contents
  1. Why Base first?
  2. What the numbers look like
  3. The gap between gross and verified
  4. What is it like to build on?
  5. Should a new seller choose Base or Solana?
  6. Frequently asked questions
  7. Where to check this yourself

Why Base first?#

Because x402 came out of Coinbase, and Base is Coinbase's chain. The protocol launched in May 2025 with Base as the natural first target, and the facilitator, client libraries and tutorials all grew up there.

That origin produced three durable advantages: the most mature tooling, the deepest history, and the best indexer coverage. It also produced one disadvantage worth naming, which is concentration. A protocol that launched on one chain with one facilitator, both from one company, had to grow out of that to be credible as a standard, and the Linux Foundation move in April 2026 was part of doing so.

What the numbers look like#

Base held the cumulative lead through 2026 while Solana took the larger share of recent transaction activity. Both statements are true and they describe different windows, which is the usual source of confusion. One tracker reported Base's weekly transfer share falling to 48% as Solana rose to 38%; other trackers using different methods reported different splits.

More useful than the share is the like-for-like check. Over a 90-day window in 2026, Roundhouse's Base settlement count landed within about 1% of Token Terminal's figure for the same chain and the same window. That is close agreement between two independent indexers, and it is the kind of comparison worth making.

Important

The same comparison against a blended, all-evidence figure was off by a huge margin. The agreement appears when both sides count the same population on the same chain over the same window, and vanishes otherwise. Why counts disagree covers the six specific reasons.

The gap between gross and verified#

Base is the chain where this is best documented, and it is large.

A count of every gasless authorised transfer on Base is much bigger than a count of those a named facilitator relayed. The marker that x402 produces is shared with unrelated systems and predates the protocol, so the gross figure includes activity that has nothing to do with x402. What proves a transfer was an x402 payment sets out the evidence ladder.

For a seller the practical consequence is this: if someone quotes you a Base x402 figure, the first question is which band it is. The verified band and the gross band on Base differ by enough to change what you would conclude.

What is it like to build on?#

Straightforward, and this is the main argument for choosing it.

  • Facilitator coverage is the best of any chain. Every major facilitator settles on Base.
  • Client libraries target it first, so examples work without adaptation.
  • USDC is natively issued and implements EIP-3009, so the gasless path works with no special handling.
  • Gas is low enough that sub-cent payments are economic, which is the binding constraint on whether the business exists at all.
  • Indexer coverage is the deepest, so your activity is visible to buyers evaluating you.

That last point is underrated by sellers and matters commercially. A settlement nobody indexes is public and invisible at once, and a buyer screening you cannot see a history it cannot query.

Should a new seller choose Base or Solana?#

By buyer, then by tooling.

Base if your buyers are EVM-native, if you want the most mature libraries, or if you want your history to be maximally visible to the indexers buyers actually use.

Solana if your buyers hold balances there, which a growing number do, or if your volume is high enough that per-settlement cost matters at the margin.

Both, eventually, by listing two entries in your accepts array. The cost is a second reconciliation rather than a second integration, and it removes the case where a buyer cannot pay you because its money is on the other chain.

What should not drive the decision is a share figure. Shares in this market move by tens of points in weeks, and the figure you are shown is usually older than it looks.

Frequently asked questions#

Is Base controlled by Coinbase?#

Base is operated by Coinbase as a layer 2 on Ethereum, with a published decentralisation roadmap. For a seller the practical question is whether that operational concentration is acceptable, and for most sub-cent payment flows it is.

Does Base have its own x402 facilitator requirement?#

No. Any facilitator that supports the chain works, and most do. You are not tied to Coinbase's facilitator by choosing its chain.

What asset should I accept on Base?#

USDC, in almost every case. It is natively issued, widely held by the buyers you want, and implements the authorisation path the gasless flow needs. Stablecoin choice covers why that last property is the constraint.

How fast do Base settlements confirm?#

Seconds. For an interactive agent call this is usually acceptable, and sellers that cannot absorb it serve on verification and settle after, which is a real trade with a real small loss rate.

Can I see Base x402 activity without an account?#

Yes. It is on a public chain, and several indexers publish it. The thing to check is which band each one is showing.

Where to check this yourself#

/stats publishes the Base record with its window, basis and evidence grade stated, so the verified band is visible separately from the total. /transactions is the raw settlement record filterable by chain and route, and /status says how far behind the chain tip the index currently is.

Reading this as an agent?

Every page here has a markdown twin at the same URL plus .md. Same words, no navigation, no markup to strip. And the settlement record this article describes is a live index you can query rather than a claim you have to take on trust.

  • GET https://roundhouseai.io/resources/x402-on-base.mdthis page, as markdown
  • GET https://roundhouseai.io/llms.txtevery surface on roundhouseai.io
  • GET https://api.roundhouseai.io/v0the index: endpoints and schema
  • GET https://api.roundhouseai.io/v0/test/x402$0.01 over x402, and it mints your own key with no account

/docs/api has the limits and the SQL surface. /v0/account, /v0/endpoints and the capability layer answer without a key.

Read next