0xa06c…1961
Paid $0.21 of the $259.40M Roundhouse has indexed across 714,764 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (19)
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 | 57% | $0.12 | 9 | 2 |
| AI & Media | 43% | $0.09 | 9 | 1 |
$0.06 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.
- 0x6302…ad57 · last paid 112d ago$0.099 calls
▸33 of 55 catalogued endpoints list a price this agent paid
- /api/v1/location/nearby_searchPrice match$0.01 listed
- /api/v1/location/:locationId/detailsPrice match$0.01 listed
- /api/v1/location/searchPrice match$0.01 listed
- /properties/randomPrice match$0.01 listed
- /api/v1/location/:locationId/photosPrice match$0.01 listed
- /createTaskPrice match$0.01 listed
- /listings/salePrice match$0.01 listed
- /take$0.02 listed
47 further catalogued endpoints not listed.
- 0x2dd9…daf7 · last paid 112d ago$0.066 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xdd25…2ec0 · last paid 114d ago$0.063 calls
▸20 of 141 catalogued endpoints list a price this agent paid
- /api/seats-aero/searchPrice match$0.02 listed
- /api/google-flights/searchPrice match$0.02 listed
- /api/seats-aero/availability$0.04 listed
- /api/hotels/search$0.03 listed
- /api/flights/search$0.05 listed
- /api/reference/locations$0.0054 listed
- /api/hotels/list$0.03 listed
- /api/flights/availability$0.03 listed
133 further catalogued endpoints not 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 | |
|---|---|---|---|---|---|
| 0xfbe7…ca17 | $0.00 | $2.00 | 1 | 114d ago | Graph |
| 0x6302…ad57 | $0.09 | $0.00 | 9 | 112d ago | Graph |
| 0x2dd9…daf7 | $0.06 | $0.00 | 6 | 112d ago | Graph |
| 0xdd25…2ec0 | $0.06 | $0.00 | 3 | 114d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
91% of observed volume is with a single counterparty, in all 19 observed settlements.
Organic volume $2.21 of $2.21 total.
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 0xa06c…1961 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xa06c8de156bb1f2ffa73a92fe72f6793697b1961
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: 0xa06c…1961 curl -s 'https://api.roundhouseai.io/v0/agents/0xa06c8de156bb1f2ffa73a92fe72f6793697b1961' curl -s 'https://api.roundhouseai.io/v0/entities/0xa06c8de156bb1f2ffa73a92fe72f6793697b1961/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.