0x5af7…f67e
Paid $13.00 of the $3067.43M Roundhouse has indexed across 1,401,742 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (5)
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% | $13.00 | 5 | 2 |
$9.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.
- 0xb34b…17db · last paid 378d ago$9.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x1917…c685 · last paid 377d ago$4.004 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/mintPrice match$1.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 | |
|---|---|---|---|---|---|
| 0xb34b…17db | $9.00 | $0.00 | 1 | 378d ago | Graph |
| 0x1917…c685 | $4.00 | $0.00 | 4 | 377d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
69% of observed volume is with a single counterparty, in all 5 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x5af7…f67e0x1917…c685 | Base | $1.00 | 100% | payAI | 377d ago | 0x8b6603…c968e7 |
| 0x5af7…f67e0x1917…c685 | Base | $1.00 | 100% | payAI | 377d ago | 0x1d4a0c…1cf6d4 |
| 0x5af7…f67e0x1917…c685 | Base | $1.00 | 100% | payAI | 377d ago | 0x210f34…ecb2e2 |
| 0x5af7…f67e0x1917…c685 | Base | $1.00 | 100% | payAI | 377d ago | 0x19cb9f…d291a5 |
| 0x5af7…f67e0xb34b…17db | Base | $9.00 | 100% | x402rs | 378d ago | 0xcf90dc…f5a81f |
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 0x5af7…f67e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x5af7fdbbf0430f93cb0c88a703d38318c1d6f67e
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: 0x5af7…f67e curl -s 'https://api.roundhouseai.io/v0/agents/0x5af7fdbbf0430f93cb0c88a703d38318c1d6f67e' curl -s 'https://api.roundhouseai.io/v0/entities/0x5af7fdbbf0430f93cb0c88a703d38318c1d6f67e/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.