0x0f45…48da
Paid $2,237.24 of the $3061.41M Roundhouse has indexed across 1,398,509 wallets — less than 0.0001% of it.
Chains (from the recent scan): Ethereum (5)
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 |
|---|---|---|---|---|
| Onchain Data | 100% | $2,237.24 | 5 | 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.
- 0x0000…0000 · last paid 32d ago$2,237.245 calls
▸1 catalogued endpoints, none priced at an amount this agent paid
- /x402/gasGas price$5.00 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 | |
|---|---|---|---|---|---|
| 0x0000…0000 | $2,237.24 | $0.00 | 5 | 32d 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 5 observed settlements.
Organic volume $2,237.24 of $2,237.24 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x0f45…48da0x0000…0000 | Ethereum | $531.51 | 70% | 0x39d6…3765 | 32d ago | 0x4246f4…e0e4ee |
| 0x0f45…48da0x0000…0000 | Ethereum | $439.13 | 70% | 0xc4d1…14a0 | 42d ago | 0x910fbd…8b5ec5 |
| 0x0f45…48da0x0000…0000 | Ethereum | $170.94 | 70% | 0xc4d1…14a0 | 69d ago | 0x6d09b2…255344 |
| 0x0f45…48da0x0000…0000 | Ethereum | $1,088.05 | 70% | 0xc4d1…14a0 | 84d ago | 0x9efa60…c645d3 |
| 0x0f45…48da0x0000…0000 | Ethereum | $7.60 | 50% | 0x39d6…3765 | 115d ago | 0x96b919…026c02 |
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 0x0f45…48da has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x0f45614533e67d96a1fa8e24e267032d1b9c48da
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: 0x0f45…48da curl -s 'https://api.roundhouseai.io/v0/agents/0x0f45614533e67d96a1fa8e24e267032d1b9c48da' curl -s 'https://api.roundhouseai.io/v0/entities/0x0f45614533e67d96a1fa8e24e267032d1b9c48da/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.