0xf29f…2d4b
Paid $67.24 of the $846.93M Roundhouse has indexed across 1,330,416 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (3)
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% | $67.24 | 2 | 2 |
$67.24 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xbf7d…43d0 · last paid 505d ago$33.621 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xb611…2dbc · last paid 505d ago$33.621 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xbf7d…43d0 | $33.62 | $0.00 | 1 | 505d ago | Graph |
| 0xb611…2dbc | $33.62 | $0.00 | 1 | 505d ago | Graph |
| 0x0b91…b9df | $0.00 | $33.62 | 1 | 505d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
No concentration or self-dealing patterns detected in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xf29f…2d4b0xbf7d…43d0 | Base | $33.62 | 70% | 0xe890…f632 | 505d ago | 0xa72630…76e2a9 |
| 0xf29f…2d4b0xb611…2dbc | Base | $33.62 | 70% | 0xe890…f632 | 505d ago | 0x6edc3f…3c86eb |
| 0x0b91…b9df0xf29f…2d4b | Base | $33.62 | 70% | 0xe890…f632 | 505d ago | 0xbec998…c3f598 |
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 0xf29f…2d4b has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf29f9a2ae7ba7a5d5e1f6bf61030911353432d4b
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: 0xf29f…2d4b curl -s 'https://api.roundhouseai.io/v0/agents/0xf29f9a2ae7ba7a5d5e1f6bf61030911353432d4b' curl -s 'https://api.roundhouseai.io/v0/entities/0xf29f9a2ae7ba7a5d5e1f6bf61030911353432d4b/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.