Verified facilitators
Who says which address is theirs.
Both of these publish the address they settle from, and the chain shows that same address relaying. The receipts are further down.
Aeronscan indexes the signature-authorised transfers x402 runs on — through USDG's own EIP-3009 and through the x402 gateway. No facilitator has to report anything. Ours is one row among the rest.
Both of these publish the address they settle from, and the chain shows that same address relaying. The receipts are further down.
The receiving side of the same evidence. A facilitator publishes the address it settles from; a merchant publishes the address it is paid at — in the 402 that asks strangers to send money there. Follow the link on any card and the address below it is in the response. What each of them earned is further down.
Inference across 100+ models and the signed RWA listings, priced per call in USDG.
paid at 0x1b8e…80bd
The MeshGateway team’s own services — launch feeds, DEX intelligence, RWA prices. The largest seller in this index.
paid at 0xbb81…b5c9
Blocks generated per request over x402, mintable by the wallet that paid. Settles through Mesh.
paid at 0x92ae…b686
Text and images written permanently into chain calldata, priced by the byte. Settles through Aeron.
paid at 0xdb53…4fd7
An agent fleet for tokenized stocks: it watches, drafts moves, and never acts without approval. Metered in USDG. Settles through Aeron.
paid at 0x9c08…22b3Settlements in USDG on Robinhood Chain, by the time the block was mined.
Same rows an agent gets from GET /api/transactions.
Attribution is the relayer address that paid the gas. A name is a claim you can check — anyone unnamed keeps their address and their volume.
The other half of attribution. The chain proves an address was paid; it cannot say whose address it is. A name here is one the merchant publishes itself — in the 402 that asks to be paid at that very address — so it is a claim you can go and check, not a favour this page does. A seller nobody has named keeps its address, its volume and its place in the feed.
Running an x402 service on this chain? If your 402 publishes the address it is paid at, that is all a name here needs.
Open, no key, CORS on. The explorer's own page uses nothing else.
curl https://scan.aeron.sh/api/stats?window=24 curl https://scan.aeron.sh/api/transactions?limit=25 curl https://scan.aeron.sh/api/address/0x… # both sides of one wallet curl https://scan.aeron.sh/api/tx/0x… # one settlement
GET /api/stats: totals, per-facilitator split, and a time series — ?window=1|24|168|720GET /api/transactions: the feed — filter with ?buyer=, ?seller=, ?facilitator=, page with ?before=GET /api/address/{address}: what one wallet spent and earnedGET /api/tx/{hash}: every settlement in one transactionGET /api/facilitators: known relayers and their shareGET /api/merchants: named sellers, what they earned, and where each name is published — ?verified=1GET /icon/{payTo}: that merchant's mark, served from here rather than from its own siteGET /api/leaderboard: top sellers and buyers for a windowGET /healthz: index cursor and row countAuthorizationUsed, and the x402 gateway's Settled beside the transfer it just made. Both are payments somebody else paid the gas for; an index that watched only the token would miss a facilitator entirely.