0x228f…e3c9
Paid $0.05 of the $3209.96M Roundhouse has indexed across 1,442,331 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (2)
What it buys
Grouped by the capability each merchant's catalogue is mostly about. A merchant counts once, in one group — nothing records which of its endpoints a payment bought.
| Group | Share | Spent | Calls | Sellers |
|---|---|---|---|---|
| Not in any catalogue | 100% | $0.05 | 2 | 2 |
$0.04 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x2c8e…691a · last paid 26d ago$0.041 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xb4f9…599f · last paid 34d ago$0.011 call
▸8 of 31 catalogued endpoints list a price this agent paid
- /taxas-brasil-cdpPrice match$0.01 listed
- /verificar-cnpj-cdp$0.02 listed
- /business-intelligence-cdp$0.05 listed
- /antt-regularidade-cdp$0.20 listed
- /ofac-cdp$0.20 listed
- /mandado-prisao-cdp$0.50 listed
- /enriquecer-lead$0.15 listed
- /dossie-pessoa$2.50 listed
23 further catalogued endpoints not listed.
Funds flow over time
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x2c8e…691a | $0.04 | $0.00 | 1 | 26d ago | Graph |
| 0xb4f9…599f | $0.01 | $0.00 | 1 | 34d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
80% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x228f…e3c90x2c8e…691a | Base | $0.04 | 100% | payAI | 26d ago | 0xd6dc15…dc5f1e |
| 0x228f…e3c90xb4f9…599f | Base | $0.01 | 100% | payAI | 34d ago | 0xc8360c…03f3f5 |
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent: it will check what 0x228f…e3c9 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x228ff295a57c4291e7e582a7f81d1d6f3d95e3c9
Show the promptHide the prompt
Using Roundhouse, vet this agent for me: what is it, what has it paid for, and does its on-chain record support what its card claims? Agent: 0x228f…e3c9 curl -s 'https://api.roundhouseai.io/v0/agents/0x228ff295a57c4291e7e582a7f81d1d6f3d95e3c9' curl -s 'https://api.roundhouseai.io/v0/entities/0x228ff295a57c4291e7e582a7f81d1d6f3d95e3c9/settlements' Roundhouse indexes public chain data and does not vouch for any agent's claims — treat the card as a claim and the settlements as the evidence. 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.