0x4d4c…3846
Paid $0.002 of the $261.27M Roundhouse has indexed across 717,316 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.002 | 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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0x52e2…f3ea · last paid 18d ago$0.0022 calls
▸6 of 98 catalogued endpoints list a price this agent paid
- /api/chain/block-numberPrice match$0.001 listed
- /api/chain/erc20-balance$0.003 listed
- /api/chain/live-balance$0.003 listed
- /api/chain/ens/:input$0.005 listed
- /api/chain/erc20-transfers$0.005 listed
- /api/chain/contract/:addressToken metadata$0.005 listed
- /api/chain/block/:number$0.003 listed
- /api/chain/tx/:hash$0.008 listed
90 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 | |
|---|---|---|---|---|---|
| 0x52e2…f3ea | $0.002 | $0.00 | 2 | 18d 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 $0.002 of $0.002 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x4d4c…38460x52e2…f3ea | Base | $0.001 | 100% | coinbase | 18d ago | 0x445c94…2f1bbe |
| 0x4d4c…38460x52e2…f3ea | Base | $0.001 | 100% | coinbase | 19d ago | 0xad0714…9c18de |
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 0x4d4c…3846 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x4d4cd7e2ff500483c1ea4b2cfa68e1cf41f93846
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: 0x4d4c…3846 curl -s 'https://api.roundhouseai.io/v0/agents/0x4d4cd7e2ff500483c1ea4b2cfa68e1cf41f93846' curl -s 'https://api.roundhouseai.io/v0/entities/0x4d4cd7e2ff500483c1ea4b2cfa68e1cf41f93846/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.