0x7cd4…a264
Paid $24.64 of the $3059.45M Roundhouse has indexed across 1,397,037 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (561)
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 |
|---|---|---|---|---|
| Company & People | 100% | $24.64 | 561 | 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.
- 0x9700…d3ab · last paid 22d ago$24.64561 calls
▸90 of 90 catalogued endpoints list a price this agent paid
- /api/v1/paid/timePrice match$0.01 listed
- /api/v1/paid/solana-priority-feePrice match$0.002 listed
- /api/v1/paid/base-block-numberPrice match$0.002 listed
- /api/v1/paid/bazaar-pulsePrice match$0.002 listed
- /api/v1/paid/base-gas-pricePrice matchGas price$0.002 listed
- /api/v1/paid/crypto-pricePrice match$0.004 listed
- /api/v1/paid/x402-facilitator-healthPrice match$0.003 listed
- /api/v1/paid/agent-return-contextPrice match$0.005 listed
82 further catalogued endpoints not listed.
ERC-8004 registration
- Declares 5 endpoints, and 8 are in a public catalogue
Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1
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 | |
|---|---|---|---|---|---|
| 0x9700…d3ab | $24.64 | $0.00 | 561 | 22d 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 561 observed settlements.
Organic volume $24.64 of $24.64 total.
Recent activity
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 0x7cd4…a264 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7cd443d93a981ae154a78f4a9b4fadb6e8a7a264
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: 0x7cd4…a264 curl -s 'https://api.roundhouseai.io/v0/agents/0x7cd443d93a981ae154a78f4a9b4fadb6e8a7a264' curl -s 'https://api.roundhouseai.io/v0/entities/0x7cd443d93a981ae154a78f4a9b4fadb6e8a7a264/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.