0x6461…f7a5
Paid $0.02 of the $834.00M Roundhouse has indexed across 1,300,369 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 | 56% | $0.01 | 1 | 1 |
| Location & Weather | 44% | $0.008 | 2 | 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 2 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x6f04…7a48 · last paid 11d ago$0.011 call
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/web-intelligencePrice match$0.01 listed
- 0xdd25…2ec0 · last paid 23d ago$0.0082 calls
▸23 of 149 catalogued endpoints list a price this agent paid
- /api/seats-aero/search$0.02 listed
- /api/seats-aero/availability$0.04 listed
- /api/google-flights/search$0.02 listed
- /api/hotels/search$0.03 listed
- /api/flights/search$0.05 listed
- /api/reference/locations$0.0054 listed
- /api/hotels/list$0.03 listed
- /api/flights/availability$0.03 listed
141 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
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 | |
|---|---|---|---|---|---|
| 0x6f04…7a48 | $0.01 | $0.00 | 1 | 11d ago | Graph |
| 0xdd25…2ec0 | $0.008 | $0.00 | 2 | 23d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
56% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x6461…f7a50x6f04…7a48 | Base | $0.01 | 100% | coinbase | 11d ago | 0x11de09…817075 |
| 0x6461…f7a50xdd25…2ec0 | Base | $0.004 | 100% | coinbase | 23d ago | 0xd11ede…e1a463 |
| 0x6461…f7a50xdd25…2ec0 | Base | $0.004 | 100% | coinbase | 23d ago | 0xab9754…115705 |
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 0x6461…f7a5 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x64613acd2a1fecfe1b0c0c428884ec3ea699f7a5
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: 0x6461…f7a5 curl -s 'https://api.roundhouseai.io/v0/agents/0x64613acd2a1fecfe1b0c0c428884ec3ea699f7a5' curl -s 'https://api.roundhouseai.io/v0/entities/0x64613acd2a1fecfe1b0c0c428884ec3ea699f7a5/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.