0x0c2a…abfd
Paid $0.003 of the $3058.83M Roundhouse has indexed across 1,396,904 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (2)
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 |
|---|---|---|---|---|
| Location & Weather | 67% | $0.002 | 1 | 1 |
| Not in any catalogue | 33% | $0.001 | 1 | 1 |
$0.001 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.
- 0x0e84…b808 · last paid 3d ago$0.0021 call
▸6 of 87 catalogued endpoints list a price this agent paid
- /base-seasonPrice match$0.002 listed
- /tweet-search$0.005 listed
- /crypto-news$0.001 listed
- /meta-intelligence$0.001 listed
- /pay/agent_ottoai_crypto_news$0.001 listed
- /filtered-news$0.001 listed
- /token-details$0.001 listed
- /kol-sentiment$0.003 listed
79 further catalogued endpoints not listed.
- 0xb334…cb08 · last paid 3d ago$0.0011 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x0e84…b808 | $0.002 | $0.00 | 1 | 3d ago | Graph |
| 0xb334…cb08 | $0.001 | $0.00 | 1 | 3d 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 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x0c2a…abfd0xb334…cb08 | Base | $0.001 | 100% | payAI | 3d ago | 0xf9c98c…be59ea |
| 0x0c2a…abfd0x0e84…b808 | Base | $0.002 | 100% | coinbase | 3d ago | 0x9e577b…bc1010 |
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 0x0c2a…abfd has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x0c2a7cc6f2bd3a4c13f8e2ea7f19eb0f33f0abfd
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: 0x0c2a…abfd curl -s 'https://api.roundhouseai.io/v0/agents/0x0c2a7cc6f2bd3a4c13f8e2ea7f19eb0f33f0abfd' curl -s 'https://api.roundhouseai.io/v0/entities/0x0c2a7cc6f2bd3a4c13f8e2ea7f19eb0f33f0abfd/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.