0x91d5…0abd
Paid $2.75 of the $3056.54M Roundhouse has indexed across 1,396,119 wallets — less than 0.0001% of it.
Whole-history totals from the index rollup, which can be up to 30 minutes behind.
Chains (from the recent scan): Base (276)
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 | 100% | $2.75 | 1 | 1 |
Every merchant paid publishes at least one catalogued endpoint.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xfc24…ebb3 · last paid 56d ago$2.751 call
▸200 catalogued endpoints, none priced at an amount this agent paid
- /satellite/imageImage generation$0.02 listed
- /papers/doi$0.01 listed
- /papers/most-cited$0.02 listed
- /bulk/email/hosted-by/gmx$0.10 listed
- /bulk/email/disposable/mohmal-com$0.10 listed
- /bulk/email/hosted-by/web-de$0.10 listed
- /library/language/zh$0.01 listed
- /dev/convert/short-tons-to-kg$0.01 listed
192 further catalogued endpoints not listed.
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 | |
|---|---|---|---|---|---|
| 0xfc24…ebb3 | $2.75 | $0.00 | 1 | 56d ago | Graph |
| 0xe3ba…3fb3 | $0.00 | $2.69 | 269 | 56d ago | Graph |
| 0x8749…bc9c | $0.00 | $0.03 | 3 | 57d ago | Graph |
| 0x69e1…8a19 | $0.00 | $0.03 | 3 | 58d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
50% of observed volume is with a single counterparty, in all 276 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 0x91d5…0abd has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x91d568599fb802cb3f03f067d2063785dbaf0abd
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: 0x91d5…0abd curl -s 'https://api.roundhouseai.io/v0/agents/0x91d568599fb802cb3f03f067d2063785dbaf0abd' curl -s 'https://api.roundhouseai.io/v0/entities/0x91d568599fb802cb3f03f067d2063785dbaf0abd/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.