0xd67e…1c71
Paid $0.01 of the $3060.46M Roundhouse has indexed across 1,398,118 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1)
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% | $0.01 | 1 | 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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0xf990…dca5 · last paid 130d ago$0.011 call
▸24 of 32 catalogued endpoints list a price this agent paid
- /admin-api/machine/request/searchPrice matchWeb search$0.01 listed
- /admin-api/machine/request/listPrice match$0.01 listed
- /admin-api/machine/request/movePrice match$0.01 listed
- /admin-api/machine/request/sendPrice match$0.01 listed
- /admin-api/machine/request/replyPrice match$0.01 listed
- /admin-api/machine/mailboxes/:email/searchPrice matchWeb search$0.01 listed
- /admin-api/machine/request/attachmentsPrice match$0.01 listed
- /admin-api/ui/domain-admin/pay/loginPrice match$0.01 listed
24 further catalogued endpoints not 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 | |
|---|---|---|---|---|---|
| 0xf990…dca5 | $0.01 | $0.00 | 1 | 130d 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 1 observed settlement.
Organic volume $0.01 of $0.01 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xd67e…1c710xf990…dca5 | Base | $0.01 | 100% | coinbase | 130d ago | 0x1b8f4f…5b89e4 |
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 0xd67e…1c71 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xd67ef2c9c94a8490f303ecfc83834e2dcd3b1c71
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: 0xd67e…1c71 curl -s 'https://api.roundhouseai.io/v0/agents/0xd67ef2c9c94a8490f303ecfc83834e2dcd3b1c71' curl -s 'https://api.roundhouseai.io/v0/entities/0xd67ef2c9c94a8490f303ecfc83834e2dcd3b1c71/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.