Live revenue.
Every rail's wallet, one page - refreshed from public RPCs (60s cache), every figure verifiable at its explorer link. Machine-readable: /api/revenue.
4,816 verifiable external payments all-time - $67.4870 settled on-chain, each linked to its explorer proof · ledger backfilling - total still rising
as of 2026-08-17T12:55:50.583Z · external in recent window $0.1190
every figure is external revenue only - our own canary/test/funding money never counts (wallet balances are float, not earnings, and are not shown)
Recent-window transfers are the last few hours of inbound stablecoin on each rail, classified with the same rule as the daily revenue digest: a payment is external only if it comes from a wallet that isn't ours (canary/test burners are excluded) and is per-call-sized (≤ $0.75); bigger inbound is funding or tests, not a buy. Rails read best-effort: a flaky public RPC marks that rail unavailable without hiding the others.
Don't take our word for it: x402scan indexes our on-chain settlements independently → Their totals count all traffic to our wallets - including our own canary and test buys - so they read higher than the external-only figures above. Their seller row also groups our upstream spending wallet in with the treasury, and that wallet receives the revenue from the tools that fund external purchases, so part of what appears there as demand is our own self-funding loop rather than a third party paying us. Both figures are correct; they measure different things, and the external-only series above is the one that answers "did someone else pay for this".
MPP transactions (30) ›
Settlements whose credential arrived over the MPP wire (Authorization: Payment) rather than x402's PAYMENT-SIGNATURE. Same on-chain USDC settlement either way - this just filters to the MPP dialect. Machine-readable: /api/revenue/mpp.