0x1372…ad9e
Paid $5.70 of the $834.10M Roundhouse has indexed across 1,300,498 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (55)
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 | 88% | $5.00 | 1 | 1 |
| Reference Data | 12% | $0.70 | 54 | 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 2 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xa946…2101 · last paid 5d ago$5.001 call
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/v1/keys/vendPrice match$5.00 listed
- 0x5f71…5af8 · last paid 5d ago$0.7054 calls
▸27 of 27 catalogued endpoints list a price this agent paid
- /fetch/basicPrice match$0.004 listed
- /contentsPrice match$0.004 listed
- /domainPrice matchDomain and DNS lookup$0.005 listed
- /discussionsPrice match$0.004 listed
- /pdfPrice match$0.004 listed
- /fetch/proPrice match$0.006 listed
- /mapPrice match$0.004 listed
- /techPrice match$0.005 listed
19 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 | |
|---|---|---|---|---|---|
| 0xa946…2101 | $5.00 | $0.00 | 1 | 5d ago | Graph |
| 0x5f71…5af8 | $0.70 | $0.00 | 54 | 5d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
88% of observed volume is with a single counterparty, in all 55 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x1372…ad9e0x5f71…5af8 | Base | $0.0006 | 100% | payAI | 5d ago | 0xa9e15f…926da5 |
| 0x1372…ad9e0x5f71…5af8 | Base | $0.0006 | 100% | payAI | 5d ago | 0xa7d095…1694b2 |
| 0x1372…ad9e0x5f71…5af8 | Base | $0.0006 | 100% | payAI | 5d ago | 0x66e9a7…b32400 |
| 0x1372…ad9e0x5f71…5af8 | Base | $0.0006 | 100% | payAI | 5d ago | 0xe05109…949183 |
| 0x1372…ad9e0x5f71…5af8 | Base | $0.0006 | 100% | payAI | 5d ago | 0x91001c…a4f96a |
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 0x1372…ad9e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x1372ea22c003dd143a3845f56ca070c4b952ad9e
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: 0x1372…ad9e curl -s 'https://api.roundhouseai.io/v0/agents/0x1372ea22c003dd143a3845f56ca070c4b952ad9e' curl -s 'https://api.roundhouseai.io/v0/entities/0x1372ea22c003dd143a3845f56ca070c4b952ad9e/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.