0x1e24…bfbb
Paid $201.25 of the $3105.41M Roundhouse has indexed across 1,406,887 wallets — less than 0.0001% of it.
Chains (from the recent scan): Ethereum (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 |
|---|---|---|---|---|
| Web & Content | 100% | $201.25 | 2 | 1 |
Every merchant paid publishes at least one catalogued endpoint.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x480c…846a · last paid 46d ago$201.252 calls
▸8 catalogued endpoints, none priced at an amount this agent paid
- /x402/gift-cards/searchWeb search$0.002 listed
- /x402/checkout/info$0.001 listed
- /x402/invoice/create$0.002 listed
- /x402/topups/searchWeb search$0.002 listed
- /x402/invoice/pay$1,000.00 listed
- /x402/esims/searchWeb search$0.002 listed
- /x402/products/detail$0.001 listed
- /x402/invoice/status$0.001 listed
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x480c…846a | $201.25 | $0.00 | 2 | 46d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 2 observed settlements.
Organic volume $201.25 of $201.25 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x1e24…bfbb0x480c…846a | Ethereum | $133.25 | 70% | 0x480c…846a | 46d ago | 0x4ac6e4…6e59de |
| 0x1e24…bfbb0x480c…846a | Ethereum | $68.00 | 50% | 0x480c…846a | 46d ago | 0x2d9ec7…c5943e |
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 0x1e24…bfbb has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x1e24fec0f1c2039cb8b360ad6ea43b265877bfbb
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: 0x1e24…bfbb curl -s 'https://api.roundhouseai.io/v0/agents/0x1e24fec0f1c2039cb8b360ad6ea43b265877bfbb' curl -s 'https://api.roundhouseai.io/v0/entities/0x1e24fec0f1c2039cb8b360ad6ea43b265877bfbb/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.