0xd596…5d1e
Paid $2.00 of the $3058.83M Roundhouse has indexed across 1,396,716 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 | 95% | $1.90 | 1 | 1 |
| AI & Media | 5% | $0.10 | 1 | 1 |
$1.90 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.
- 0x5206…e5ab · last paid 17d ago$1.901 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x47d3…9dda · last paid 94d ago$0.101 call
▸2 catalogued endpoints, none priced at an amount this agent paid
- /v1/sessionTranscription$0.03 listed
- /v1/credits/purchase$5.00 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 | |
|---|---|---|---|---|---|
| 0x5206…e5ab | $1.90 | $0.00 | 1 | 17d ago | Graph |
| 0x47d3…9dda | $0.10 | $0.00 | 1 | 94d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
95% of observed volume is with a single counterparty, in all 2 observed settlements.
Organic volume $2.00 of $2.00 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xd596…5d1e0x5206…e5ab | Base | $1.90 | 70% | 0x4c72…eca6 | 17d ago | 0x55b82a…effe5f |
| 0xd596…5d1e0x47d3…9dda | Base | $0.10 | 100% | coinbase | 94d ago | 0x887db9…cae8f4 |
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 0xd596…5d1e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xd596537fef39bb4ea390248c88bd5074b9d85d1e
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: 0xd596…5d1e curl -s 'https://api.roundhouseai.io/v0/agents/0xd596537fef39bb4ea390248c88bd5074b9d85d1e' curl -s 'https://api.roundhouseai.io/v0/entities/0xd596537fef39bb4ea390248c88bd5074b9d85d1e/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.