0x1ba7…5834
Paid $1.25 of the $3053.48M Roundhouse has indexed across 1,395,044 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (104)
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 |
|---|---|---|---|---|
| Reference Data | 89% | $1.11 | 72 | 1 |
| Not in any catalogue | 11% | $0.14 | 32 | 1 |
$0.14 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.
- 0xc291…dc46 · last paid 62d ago$1.1172 calls
▸182 of 185 catalogued endpoints list a price this agent paid
- /gate/squeezeos/api/canon/batchPrice match$0.01 listed
- /gate/calibration-court/api/v1/recalibratePrice match$0.01 listed
- /gate/squeezeos/v1/livewire/market/sessionPrice match$0.005 listed
- /gate/squeezeos/v1/scrapePrice matchPage to markdown$0.01 listed
- /api/web/extract-oncePrice match$0.005 listed
- /gate/squeezeos/api/quick/searchPrice matchWeb search$0.001 listed
- /gate/squeezeos/api/compliance/anomalies/TESTBANKPrice match$0.01 listed
- /gate/mnemos/v1/gas/recommendPrice match$0.001 listed
177 further catalogued endpoints not listed.
- 0x4e14…7700 · last paid 70d ago$0.1432 calls
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 | |
|---|---|---|---|---|---|
| 0xc291…dc46 | $1.11 | $0.00 | 72 | 62d ago | Graph |
| 0x4e14…7700 | $0.14 | $0.00 | 32 | 70d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
89% of observed volume is with a single counterparty, in all 104 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 0x1ba7…5834 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x1ba7242f936d12b8cd5ba12d09cfdd86df615834
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: 0x1ba7…5834 curl -s 'https://api.roundhouseai.io/v0/agents/0x1ba7242f936d12b8cd5ba12d09cfdd86df615834' curl -s 'https://api.roundhouseai.io/v0/entities/0x1ba7242f936d12b8cd5ba12d09cfdd86df615834/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.