All listed chains.
0x0659…ae24
1 relayer wallet · relayer observed on-chain
Settled volume, last 182 days
$0.53 totalSettlements relayed, last 182 days
53 totalSettlement activity
182 days, every settlement countedEvery settlement attributed to this facilitator, per day, across its whole relayer pool. Click a day to see them in the ledger.
Settles most often for
| Counterparty | Paid via it | Received via it | Settlements | Last | |
|---|---|---|---|---|---|
| 0xcf17…c3dd | $0.53 | $0.00 | 53 | 10d ago | Graph |
| 0xc4fc…d1a6 | $0.00 | $0.53 | 53 | 10d ago | Graph |
The wallets this facilitator most often relays settlements for, over its recent attributed window.
Settlements relayedAll listed chains
Open in the ledger, filteredRelayer wallets (gas sponsors)
| Wallet | Txs relayed | Gas float | Payers | Payees |
|---|---|---|---|---|
| 0x0659…ae24 | 524 | 0.0000 ETH | — | — |
Txs relayed = the wallet's on-chain transaction count (fact). Settled volume is an exact sum of the settlements we hold for this operator over 182 days. Payers/payees and share are from sampled 30-day discovery windows (estimates) — a share needs a site-wide denominator, which lives only on /stats. A facilitator typically rotates settlements across a wallet pool and keeps each on a thin, topped-up gas float. Every figure on this page covers the 1 attribution value that resolve to this operator, not just its group key.
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will read 0x0659…ae24's settlement record over the free read API. No key, no account.
GET api.roundhouseai.io/v0/transactions?via=0x0659868257cc019fdf430eab2d3566e0b9a1ae24
This relayer has no named operator in the facilitator registry yet, so it is identified by its wallet.
Show the promptHide the prompt
Using Roundhouse, tell me what this x402 facilitator actually relays: volume, who it settles for, and how steady it has been. Facilitator: 0x0659…ae24 curl -s 'https://api.roundhouseai.io/v0/transactions?via=0x0659868257cc019fdf430eab2d3566e0b9a1ae24&limit=100' curl -s 'https://api.roundhouseai.io/v0/facilitators' The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.