0x7cd2…f84d
Paid $8.15 of the $847.23M Roundhouse has indexed across 1,330,946 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (26)
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% | $8.15 | 10 | 2 |
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 2 the amount paid narrows the list to the ones listed at that price.
- 0xa733…a1d6 · last paid 24d ago$5.001 call
▸6 catalogued endpoints, none priced at an amount this agent paid
- /v1/listings/:id/verdict$0.005 listed
- /v1/demand/clusters$0.25 listed
- /v1/listings/:id/verify-now$3.00 listed
- /v1/verdicts$0.10 listed
- /v1/listings/:id/purchases$0.01 listed
- /v1/listings/9a8bf56d-2fc/verdict$0.005 listed
- 0xac6a…e3b4 · last paid 3d ago$3.159 calls
▸3 of 3 catalogued endpoints list a price this agent paid
- /x402/provisionPrice match$0.50 listed
- /x402/receiptPrice match$0.05 listed
- /x402/topupPrice match$0.50 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 | |
|---|---|---|---|---|---|
| 0xa733…a1d6 | $5.00 | $0.00 | 1 | 24d ago | Graph |
| 0xac6a…e3b4 | $3.15 | $0.00 | 9 | 3d ago | Graph |
| 0x9383…7afc | $0.00 | $1.15 | 16 | 6d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
54% of observed volume is with a single counterparty, in all 26 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x7cd2…f84d0xac6a…e3b4 | Base | $0.05 | 100% | coinbase | 57d ago | 0xb580e0…f13f11 |
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 0x7cd2…f84d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7cd2e0ed2721319b20faac4109774d030833f84d
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: 0x7cd2…f84d curl -s 'https://api.roundhouseai.io/v0/agents/0x7cd2e0ed2721319b20faac4109774d030833f84d' curl -s 'https://api.roundhouseai.io/v0/entities/0x7cd2e0ed2721319b20faac4109774d030833f84d/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.