0xf29a…7e81
Paid $156.33 of the $3228.97M Roundhouse has indexed across 1,452,067 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): Ethereum (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 | 64% | $100.33 | 1 | 1 |
| Onchain Data | 36% | $56.01 | 1 | 1 |
$100.33 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.
- 0xbc0d…893e · last paid 51d ago$100.331 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x0000…0000 · last paid 6d ago$56.011 call
▸1 catalogued endpoints, none priced at an amount this agent paid
- /x402/gasGas price$0.80 listed
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 | |
|---|---|---|---|---|---|
| 0xbc0d…893e | $100.33 | $0.00 | 1 | 51d ago | Graph |
| 0x0000…0000 | $56.01 | $0.00 | 1 | 6d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
64% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xf29a…7e810x0000…0000 | Ethereum | $56.01 | 70% | 0xbc0d…893e | 6d ago | 0xe644c8…6ecaa1 |
| 0xf29a…7e810xbc0d…893e | Ethereum | $100.33 | 70% | 0xbc0d…893e | 51d ago | 0xfd9e46…1fd2a1 |
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 0xf29a…7e81 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf29acd30fd86ed75f98300275e960f7c65357e81
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: 0xf29a…7e81 curl -s 'https://api.roundhouseai.io/v0/agents/0xf29acd30fd86ed75f98300275e960f7c65357e81' curl -s 'https://api.roundhouseai.io/v0/entities/0xf29acd30fd86ed75f98300275e960f7c65357e81/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.