0x7672…eebd
Paid $1.00 of the $3053.48M Roundhouse has indexed across 1,395,044 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (2)
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.00 | 2 | 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.
- 0x6b7b…a4e5 · last paid 2h ago$1.001 call
▸1 catalogued endpoints, none priced at an amount this agent paid
- /x402/decode$0.005 listed
- 0xcc42…305f · last paid 2h ago$0.0011 call
▸1 of 200 catalogued endpoints list a price this agent paid
- /v1/pingPrice match$0.001 listed
- /v1/econ/:series$0.02 listed
- /v1/alerts/fire-weather$0.01 listed
- /v1/calendar/delta$0.005 listed
- /v1/oracle/v3/sea-edgeWeather forecast$0.05 listed
- /v1/recalls/delta$0.005 listed
- /v1/board/science-tech$0.04 listed
- /v1/movers/entertainment$0.04 listed
192 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x6b7b…a4e5 | $1.00 | $0.00 | 1 | 2h ago | Graph |
| 0xcc42…305f | $0.001 | $0.00 | 1 | 2h 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, in all 2 observed settlements.
Organic volume $1.00 of $1.00 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x7672…eebd0x6b7b…a4e5 | Base | $1.00 | 100% | coinbase | 2h ago | 0xe9b7d2…2deca1 |
| 0x7672…eebd0xcc42…305f | Base | $0.001 | 100% | coinbase | 2h ago | 0x158704…9c5a4e |
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 0x7672…eebd has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x76724b84cd979dc980168d4ac38538377b59eebd
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: 0x7672…eebd curl -s 'https://api.roundhouseai.io/v0/agents/0x76724b84cd979dc980168d4ac38538377b59eebd' curl -s 'https://api.roundhouseai.io/v0/entities/0x76724b84cd979dc980168d4ac38538377b59eebd/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.