0x0d87…395c
Paid $65.19 of the $846.74M Roundhouse has indexed across 1,330,277 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (3)
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% | $65.19 | 2 | 2 |
$65.19 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xd016…db1d · last paid 463d ago$32.601 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xedfe…6675 · last paid 463d ago$32.601 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xd016…db1d | $32.60 | $32.60 | 2 | 463d ago | Graph |
| v3.linkdrop.eth | $32.60 | $0.00 | 1 | 463d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
67% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x0d87…395c0xd016…db1d | Base | $32.60 | 70% | 0xe890…f632 | 463d ago | 0x7a2e78…a44a9d |
| 0x0d87…395cv3.linkdrop.eth | Base | $32.60 | 70% | 0x5f34…bdc0 | 463d ago | 0xbd1343…1c7fd5 |
| 0xd016…db1d0x0d87…395c | Base | $32.60 | 70% | 0xe890…f632 | 464d ago | 0xc6df87…d6bd67 |
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 0x0d87…395c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x0d876023a77e2edc92517e34243d5d09c2d9395c
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: 0x0d87…395c curl -s 'https://api.roundhouseai.io/v0/agents/0x0d876023a77e2edc92517e34243d5d09c2d9395c' curl -s 'https://api.roundhouseai.io/v0/entities/0x0d876023a77e2edc92517e34243d5d09c2d9395c/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.