Every payment that flows through our rails - both wires, x402 and MPP, plus card purchases through Stripe, one page. Refreshed from public RPCs (60s cache), every figure verifiable at its explorer link.
Machine-readable: /api/revenue · /api/revenue/mpp.
2 settled transactions through our pay rails - x402 + MPP, all-time · ours included: we run ~200 Tempo MPP settles/day plus a daily canary on every rail, so the plumbing is exercised continuously · ledger backfilling - total still rising
2 distinct agents have paid us - unique external wallets across all rails · top 5 = 100% of external payments
2 external payments - $0.0117 real revenue settled on-chain, each linked to its explorer proof
as of 2026-08-30T09:30:32.384Z · external in recent window $0.0117 the big number is total throughput (ours included - the rail-stability signal); every revenue figure is external only - our own canary/test/funding money is never counted as earnings (wallet balances are float, not shown)
Revenue over time · by chain · from the settlement ledgerraw data →
MPP-wire settlements are identified by tx hash from the sales ledger, which began recording the wire on 2026-07-24 - earlier days read as x402 because the wire was not recorded, not because no MPP traffic existed. The teal Tempo lane is always MPP-wire (it's never x402-settleable) and drops out under the x402 filter.
SOR = revenue settled on-chain to the dedicated spending wallet that pays external sellers and upstream data (route-execute tiers + the Blockscout kit) - the self-funding loop. Direct = everything settled to the treasury. The split is by receiving wallet, so revenue from before a tool joined the self-funding set reads as Direct - that is what the chain says, not a gap. The wire split is not tracked within this lane, so selecting it resets the wire filter.
view as table
Rail throughput · every settled on-chain transaction, ours includedthroughput proves the rails · the revenue figure up top counts only money from others
2
settled transactions all-time
across 12 rails + the MPP wire
2
distinct agents have paid
unique external wallets - the adoption number
2
on-chain (x402 + evm MPP)
USDC transfers to our rail wallets, ours incl.
0
native MPP on Tempo
~200/day volume + daily canaries
We run our own money through the same gates buyers use, continuously: a daily paid canary on every rail, ~200 Tempo MPP settlements a day, and weekly full-catalog sweeps. Those are real on-chain transactions - that is the point - but they are ours, so they live here and never in a revenue number. The chart above splits External / Internal explicitly.
One card per chain we accept x402 on. The headline is the number of transactions settled on that rail (ours included - the adoption/liveness signal), with external revenue underneath; the rows are the newest external buys in the recent scan window, each linked to its explorer proof.
Base · USDClive
2transactions on this rail (ours incl.) · 2 external$0.011665 external revenue · window $0.011665
Settlements whose credential arrived over the MPP wire rather than x402's PAYMENT-SIGNATURE. On Base and Celo that is the same on-chain USDC settlement as x402 (the shim translates the credential); on Tempo it is native USDC.e (PathUSD accepted) through Tempo's relay. These counts are throughput, not revenue - the bulk is our own volume + canary runs exercising the rails continuously; the external column is money from others. Recorded from the sales ledger, which began attributing the wire on 2026-07-24.
Base · USDClive
0through the rail (ours incl.) · 0 external
evm/charge via the shim → x402 settle
offered on every 402 - no MPP-wire settlement on this rail yet
Celo · USDClive
0through the rail (ours incl.) · 0 external
evm/charge via the shim → x402 settle
offered on every 402 - no MPP-wire settlement on this rail yet
Tempo · PathUSDlive
0through the rail (ours incl.) · 0 external
native tempo/charge via Tempo's relay
offered on every 402 - no MPP-wire settlement on this rail yet
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".