0x3132…3b5c
Paid $474.00 of the $3067.00M Roundhouse has indexed across 1,400,982 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (474)
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% | $474.00 | 474 | 5 |
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 4 of 5 the amount paid narrows the list to the ones listed at that price.
- 0x9b4d…6083 · last paid 379d ago$296.00296 calls
▸2 of 2 catalogued endpoints list a price this agent paid
- /mint?address=0x020161B0D3f33446cBc3194726B5E3898E6Ce80e&tier=10Price match$1.00 listed
- /mintPrice match$1.00 listed
- 0x2a50…f089 · last paid 381d ago$120.00120 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /mintPrice match$1.00 listed
- 0xe25b…f8cf · last paid 379d ago$55.0055 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/mintPrice match$1.00 listed
- 0x1917…c685 · last paid 377d ago$2.002 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/mintPrice match$1.00 listed
- 0xd85c…9d46 · last paid 383d ago$1.001 call
▸1 catalogued endpoints, none priced at an amount this agent paid
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 | |
|---|---|---|---|---|---|
| 0x9b4d…6083 | $296.00 | $0.00 | 296 | 379d ago | Graph |
| 0x2a50…f089 | $120.00 | $0.00 | 120 | 381d ago | Graph |
| 0xe25b…f8cf | $55.00 | $0.00 | 55 | 379d ago | Graph |
| 0x1917…c685 | $2.00 | $0.00 | 2 | 377d ago | Graph |
| 0xd85c…9d46 | $1.00 | $0.00 | 1 | 383d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
62% of observed volume is with a single counterparty, in all 474 observed settlements.
Recent activity
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 0x3132…3b5c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x3132c06bd1ec8978f27cb6370ff03b526dbd3b5c
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: 0x3132…3b5c curl -s 'https://api.roundhouseai.io/v0/agents/0x3132c06bd1ec8978f27cb6370ff03b526dbd3b5c' curl -s 'https://api.roundhouseai.io/v0/entities/0x3132c06bd1ec8978f27cb6370ff03b526dbd3b5c/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.