0x0010…39d9
Paid $4.00 of the $260.90M Roundhouse has indexed across 716,705 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% | $4.00 | 3 | 3 |
$3.00 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; for 2 of 3 the amount paid narrows the list to the ones listed at that price.
- 0xb34b…17db · last paid 333d ago$3.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xd732…5308 · last paid 333d ago$1.001 call
▸2 of 3 catalogued endpoints list a price this agent paid
- /api/payPrice match$1.00 listed
- /api/payPrice match$1.00 listed
- /api/pay-10$10.00 listed
- 0x9490…36d6 · last paid 334d ago$0.0011 call
▸1 of 1 catalogued endpoints list a price this agent paid
- /rumoursPrice match$0.001 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 | |
|---|---|---|---|---|---|
| 0xb34b…17db | $3.00 | $0.00 | 1 | 333d ago | Graph |
| 0xd732…5308 | $1.00 | $0.00 | 1 | 333d ago | Graph |
| 0x9490…36d6 | $0.001 | $0.00 | 1 | 334d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
75% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x0010…39d90xb34b…17db | Base | $3.00 | 100% | x402rs | 333d ago | 0x90b570…0d76ab |
| 0x0010…39d90xd732…5308 | Base | $1.00 | 100% | mogami | 333d ago | 0x10a10d…801b41 |
| 0x0010…39d90x9490…36d6 | Base | $0.001 | 100% | x402rs | 334d ago | 0x28a5dc…c4981e |
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 0x0010…39d9 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x0010b310e8310bfa3e5135c9e73a6f13973339d9
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: 0x0010…39d9 curl -s 'https://api.roundhouseai.io/v0/agents/0x0010b310e8310bfa3e5135c9e73a6f13973339d9' curl -s 'https://api.roundhouseai.io/v0/entities/0x0010b310e8310bfa3e5135c9e73a6f13973339d9/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.