0x2b80…296b
Paid $1.89 of the $3105.41M Roundhouse has indexed across 1,407,333 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (120)
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.89 | 120 | 2 |
$0.70 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.
- 0x3070…fa85 · last paid 137d ago$1.19119 calls
▸43 of 130 catalogued endpoints list a price this agent paid
- /api/v1/treasury-yieldsPrice match$0.01 listed
- /api/v1/gdpPrice match$0.01 listed
- /api/v1/exchangesPrice match$0.01 listed
- /api/v1/national-debtPrice match$0.01 listed
- /api/v1/unified-snapshot$0.02 listed
- /api/v1/filing-search$0.02 listed
- /api/v1/compare$0.05 listed
- /api/v1/grouped-daily$0.02 listed
122 further catalogued endpoints not listed.
- 0xccc8…15be · last paid 138d ago$0.701 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.
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 | |
|---|---|---|---|---|---|
| 0x3070…fa85 | $1.19 | $0.00 | 119 | 137d ago | Graph |
| 0xccc8…15be | $0.70 | $0.00 | 1 | 138d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
63% of observed volume is with a single counterparty, in all 120 observed settlements.
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 0x2b80…296b has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x2b80431e0b9be3afa2da93f4307abd7f6ca2296b
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: 0x2b80…296b curl -s 'https://api.roundhouseai.io/v0/agents/0x2b80431e0b9be3afa2da93f4307abd7f6ca2296b' curl -s 'https://api.roundhouseai.io/v0/entities/0x2b80431e0b9be3afa2da93f4307abd7f6ca2296b/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.