0x7689…dfe3
Paid $0.001 of the $3052.78M Roundhouse has indexed across 1,394,692 wallets — less than 0.0001% of it.
Whole-history totals from the index rollup, which can be up to 30 minutes behind.
Chains (from the recent scan): Base (1)
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% | $0.001 | 1 | 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.
- 0xb467…384a · last paid 5d ago$0.0011 call
▸1 of 15 catalogued endpoints list a price this agent paid
- /x402/v1/detectPrice match$0.001 listed
- /x402/v1/rewrite$0.004 listed
- /x402/v1/dub$0.003 listed
- /x402/v1/summarize$0.002 listed
- /x402/v1/tokenverdict$0.00 listed
- /x402/v1/ai/batch$0.00 listed
- /x402/v1/outline$0.00 listed
- /x402/v1/classify$0.00 listed
7 further catalogued endpoints not listed.
ERC-8004 registration
- Declares 2 endpoints, and 8 are in a public catalogue
Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xb467…384a | $0.001 | $0.00 | 1 | 5d 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 1 observed settlement.
Organic volume $0.001 of $0.001 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x7689…dfe30xb467…384a | Base | $0.001 | 100% | payAI | 5d ago | 0x483645…cf2420 |
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 0x7689…dfe3 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x768969f491d49ccdfce14bfbe8005d5bf1a6dfe3
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: 0x7689…dfe3 curl -s 'https://api.roundhouseai.io/v0/agents/0x768969f491d49ccdfce14bfbe8005d5bf1a6dfe3' curl -s 'https://api.roundhouseai.io/v0/entities/0x768969f491d49ccdfce14bfbe8005d5bf1a6dfe3/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.