0xf726…05a8
Paid $0.01 of the $3103.01M Roundhouse has indexed across 1,403,642 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 (1)
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% | $0.01 | 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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0x788b…8454 · last paid 16d ago$0.011 call
▸3 of 8 catalogued endpoints list a price this agent paid
- /api/bazaar/omikujiPrice match$0.01 listed
- /api/bazaar/surface_comparison_factsPrice match$0.01 listed
- /bazaar/omikujiPrice match$0.01 listed
- /api/bazaar/verified-domain-tracks$19.00 listed
- /api/bazaar/hybrid_confession$0.02 listed
- /api/bazaar/domain-observation-slots$1.00 listed
- /api/bazaar/task-offers$1.00 listed
- /api/bazaar/confession$0.02 listed
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x788b…8454 | $0.01 | $0.00 | 1 | 16d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 1 observed settlement.
Organic volume $0.01 of $0.01 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xf726…05a80x788b…8454 | Base | $0.01 | 100% | coinbase | 16d ago | 0xca0439…fb9cb6 |
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 0xf726…05a8 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf726361299cc9ec43aed843f3591aeb28a6a05a8
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: 0xf726…05a8 curl -s 'https://api.roundhouseai.io/v0/agents/0xf726361299cc9ec43aed843f3591aeb28a6a05a8' curl -s 'https://api.roundhouseai.io/v0/entities/0xf726361299cc9ec43aed843f3591aeb28a6a05a8/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.