0x7815…3e3e
Paid $10.30 of the $841.46M Roundhouse has indexed across 1,316,090 wallets — less than 0.0001% of it.
Floors, not totals: this wallet has more history than one scan returns, and the index rollup has no row for it yet, so the figures above count only its 1,000 most recent settlements.
Chains (from the recent scan): Base (1000)
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% | $10.30 | 1,000 | 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.
- 0x9636…c397 · last paid 4d ago$10.301,000 calls
▸2 of 2 catalogued endpoints list a price this agent paid
- /recommendPrice matchWeb search$0.01 listed
- /recommendPrice match$0.01 listed
Folded from this wallet's 1,000 most recent settlements, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x9636…c397 | $10.30 | $0.00 | 1,000 | 4d 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 the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).
Organic volume $10.30 of $10.30 total.
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 0x7815…3e3e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7815a4e16f55776c55f9dcde9d6594af1bcd3e3e
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: 0x7815…3e3e curl -s 'https://api.roundhouseai.io/v0/agents/0x7815a4e16f55776c55f9dcde9d6594af1bcd3e3e' curl -s 'https://api.roundhouseai.io/v0/entities/0x7815a4e16f55776c55f9dcde9d6594af1bcd3e3e/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.