0x1fc1…7e05
Paid $1.20 of the $3200.11M Roundhouse has indexed across 1,437,441 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% | $1.20 | 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 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0x942b…20c1 · last paid 23d ago$1.202 calls
▸12 of 74 catalogued endpoints list a price this agent paid
- /x402/intelligence/address$0.20 listed
- /x402/intelligence/entity$0.20 listed
- /x402/intelligence/entity-summary$0.20 listed
- /x402/intelligence/address-batch$50.00 listed
- /x402/token/balanceWallet balances$0.20 listed
- /x402/counterparties/address$10.00 listed
- /x402/intelligence/tokenToken metadata$0.20 listed
- /x402/balances/entity$1.00 listed
66 further catalogued endpoints not 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 | |
|---|---|---|---|---|---|
| 0xa9a1…daa6 | $0.00 | $2.02 | 1 | 57d ago | Graph |
| 0x942b…20c1 | $1.20 | $0.00 | 2 | 23d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
63% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x1fc1…7e050x942b…20c1 | Base | $0.60 | 100% | coinbase | 23d ago | 0x430006…00c3e7 |
| 0x1fc1…7e050x942b…20c1 | Base | $0.60 | 100% | coinbase | 57d ago | 0xc3b8d2…80e5b5 |
| 0xa9a1…daa60x1fc1…7e05 | Base | $2.02 | 70% | 0xa923…c9ac | 57d ago | 0x22c571…68cdc3 |
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 0x1fc1…7e05 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x1fc1486b6c81976ebb49d2de19b7f8cfd70b7e05
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: 0x1fc1…7e05 curl -s 'https://api.roundhouseai.io/v0/agents/0x1fc1486b6c81976ebb49d2de19b7f8cfd70b7e05' curl -s 'https://api.roundhouseai.io/v0/entities/0x1fc1486b6c81976ebb49d2de19b7f8cfd70b7e05/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.