0x9a6d…eb72
Paid $6.00 of the $846.70M Roundhouse has indexed across 1,330,126 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (6)
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% | $6.00 | 6 | 2 |
$4.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.
- 0xb7e2…1c4c · last paid 364d ago$4.004 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x6042…eebf · last paid 364d ago$2.002 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /mintPrice match$1.00 listed
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xb7e2…1c4c | $4.00 | $0.00 | 4 | 364d ago | Graph |
| 0x6042…eebf | $2.00 | $0.00 | 2 | 364d 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 6 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x9a6d…eb720xb7e2…1c4c | Base | $1.00 | 100% | coinbase | 364d ago | 0x40e4d6…aec9c5 |
| 0x9a6d…eb720xb7e2…1c4c | Base | $1.00 | 100% | coinbase | 364d ago | 0xbc680d…667bd8 |
| 0x9a6d…eb720xb7e2…1c4c | Base | $1.00 | 100% | coinbase | 364d ago | 0x255ae8…6fbcfe |
| 0x9a6d…eb720xb7e2…1c4c | Base | $1.00 | 100% | coinbase | 364d ago | 0xaa8cad…7494ac |
| 0x9a6d…eb720x6042…eebf | Base | $1.00 | 100% | payAI | 364d ago | 0x9104a8…da0576 |
| 0x9a6d…eb720x6042…eebf | Base | $1.00 | 100% | payAI | 364d ago | 0x821269…73465c |
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 0x9a6d…eb72 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9a6d7903d582d9937890a93b8d09e91850d2eb72
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: 0x9a6d…eb72 curl -s 'https://api.roundhouseai.io/v0/agents/0x9a6d7903d582d9937890a93b8d09e91850d2eb72' curl -s 'https://api.roundhouseai.io/v0/entities/0x9a6d7903d582d9937890a93b8d09e91850d2eb72/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.