0x7ad0…b6b3
Paid $1,134.00 of the $3063.55M Roundhouse has indexed across 1,399,142 wallets — less than 0.0001% of it.
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 |
|---|---|---|---|---|
| Not in any catalogue | 100% | $1,000.00 | 1,000 | 2 |
$834.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 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x0b28…eb6f · last paid 377d ago$834.00834 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x9b4d…6083 · last paid 379d ago$166.00166 calls
▸2 of 2 catalogued endpoints list a price this agent paid
- /mint?address=0x020161B0D3f33446cBc3194726B5E3898E6Ce80e&tier=10Price match$1.00 listed
- /mintPrice match$1.00 listed
Folded from this wallet's 1,000 most recent settlements of 1,134 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.
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 | |
|---|---|---|---|---|---|
| 0x0b28…eb6f | $834.00 | $0.00 | 834 | 377d ago | Graph |
| 0x9b4d…6083 | $166.00 | $0.00 | 166 | 379d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
83% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).
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 0x7ad0…b6b3 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7ad0f6295e0a13c89d8e7bbf65042fab0d8eb6b3
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: 0x7ad0…b6b3 curl -s 'https://api.roundhouseai.io/v0/agents/0x7ad0f6295e0a13c89d8e7bbf65042fab0d8eb6b3' curl -s 'https://api.roundhouseai.io/v0/entities/0x7ad0f6295e0a13c89d8e7bbf65042fab0d8eb6b3/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.