0x3c1a…8d6f
1 relayer wallet · relayer observed on-chain
Settles most often for
| Counterparty | Paid via it | Received via it | Settlements | Last | |
|---|---|---|---|---|---|
| 0x8bf5…db75 | $0.58 | $0.00 | 1 | 2d ago | Graph |
| 0x3c1a…8d6f | $0.00 | $0.58 | 1 | 2d ago | Graph |
The wallets this facilitator most often relays settlements for, over its recent attributed window.
Settlements relayed
Open in the ledger, filtered| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x8bf5…db750x3c1a…8d6f | Base | $0.58 | 70% | 0x3c1a…8d6f | 2d ago | 0x013f0d…bda9d8 |
This section carries the recent record. The ledger pages the whole history, with every filter available.
Relayer wallets (gas sponsors)
| Wallet | Txs relayed | Gas float (ETH) | Payers | Payees |
|---|---|---|---|---|
| 0x3c1a…8d6f | 5 | 0.0004 | — | — |
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 0x3c1a…8d6f's settlement record over the free read API. No key, no account.
GET api.roundhouseai.io/v0/transactions?via=0x3c1a1e01e790cd326495631b3b38bd7068f08d6f
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: 0x3c1a…8d6f curl -s 'https://api.roundhouseai.io/v0/transactions?via=0x3c1a1e01e790cd326495631b3b38bd7068f08d6f&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.