The settlement rail is proven, not promised.
39 paid endpoints settled real USDC on Base mainnet in a single sweep of the priced catalogue — $10.26 moved across 39 distinct transactions, zero reverted. The sweep was funded by our own test payer to prove the rail end-to-end. Separately, external addresses have paid $0.0202 in genuinely third-party transfers. Every row below is a real transaction you can open and check yourself. Nothing on this page asks you to take our word for anything.
Every settlement, individually checkable.
A sweep re-checked the recipient, the asset, the amount and the receipt status of each settlement. The receive address was 0xc8fF67FA…1113c8 on every row.
- network
- eip155:8453 · Base mainnet
- asset
- USDC · 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
- scheme
- exact (EIP-3009 transferWithAuthorization)
- receive address
- 0xc8fF67FAE72596478599EAAcfad8656fAe1113c8
- timeout
- 60s
What this evidence does and does not prove.
- Each transaction exists on Base mainnet and its receipt succeeded.
- The USDC transfer matches the amount advertised for that endpoint.
- The recipient is the published receive address, on every row.
- The hash in the ledger is the hash of that transaction.
- That these are the only settlements — this is the sweep of the priced catalogue.
- That the $10.26 sweep total is revenue. It is value moved in a rail test funded by our own test payer ($9.82 on Oct 1, plus $0.44 of governor + bureau settlements on Oct 6); the figures block also shows what external payers sent.
- That a registry listing implies endorsement. We are listed on payapi.market, x402-list.com and 402index.io — and not elsewhere.
- Anything about performance, returns or trading. That is a different company.
The rail exists so a machine can be paid for work it can prove it did. This page is the same idea applied to us: the claim is only worth as much as a third party’s ability to check it.