0x29f8…8ede
Paid $0.05 of the $3222.19M Roundhouse has indexed across 1,449,281 wallets — less than 0.0001% of it.
Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.
Chains (from the recent scan): Robinhood Chain (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 |
|---|---|---|---|---|
| Not in any catalogue | 80% | $0.04 | 1 | 1 |
| Web & Content | 20% | $0.01 | 1 | 1 |
$0.04 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.
- 0xfb0d…f2d7 · last paid 16m ago$0.041 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xabf4…a9d0 · last paid 17m ago$0.011 call
▸5 of 200 catalogued endpoints list a price this agent paid
- /api/searchPrice matchWeb search$0.01 listed
- /api/onchain-sql$0.03 listed
- /api/perp-basis$0.002 listed
- /api/perp-fundingPerp funding and open interest$0.002 listed
- /v1/metered/chat/completionsText completion$0.001 listed
- /api/hash$0.001 listed
- /v1/nano/chat/completionsText completion$0.003 listed
- /api/image-genImage generation$0.03 listed
192 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xfb0d…f2d7 | $0.04 | $0.00 | 1 | 16m ago | Graph |
| 0xabf4…a9d0 | $0.01 | $0.00 | 1 | 17m ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
80% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x29f8…8ede0xfb0d…f2d7 | Robinhood Chain | $0.04 | 70% | 0xfb0d…f2d7 | 16m ago | 0xa1eb7a…e1f881 |
| 0x29f8…8ede0xabf4…a9d0 | Robinhood Chain | $0.01 | 100% | roundhouse | 17m ago | 0xaadfc7…9e8396 |
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 0x29f8…8ede has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x29f811275c2cee3582abd62c7d59a8ea81b88ede
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: 0x29f8…8ede curl -s 'https://api.roundhouseai.io/v0/agents/0x29f811275c2cee3582abd62c7d59a8ea81b88ede' curl -s 'https://api.roundhouseai.io/v0/entities/0x29f811275c2cee3582abd62c7d59a8ea81b88ede/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.