0x679ee8fbdaece0673750b80765bed7a06ce6f011
Paid $0.11 of the $259.22M Roundhouse has indexed across 714,420 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 |
|---|---|---|---|---|
| AI & Media | 100% | $0.11 | 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.
- 0xee72…977c · last paid 118d ago$0.112 calls
▸20 of 36 catalogued endpoints list a price this agent paid
- /fetchPrice matchPage to markdown$0.01 listed
- /care/feedPrice match$0.01 listed
- /care/restPrice match$0.01 listed
- /care/playPrice match$0.01 listed
- /care/bathePrice match$0.01 listed
- /schedulePrice match$0.10 listed
- /repliesPrice match$0.01 listed
- /care/pack$0.03 listed
28 further catalogued endpoints not listed.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xee72…977c | $0.11 | $0.00 | 2 | 118d 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 2 observed settlements.
Organic volume $0.11 of $0.11 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x679e…f0110xee72…977c | Base | $0.10 | 100% | coinbase | 118d ago | 0x93b607…a030b1 |
| 0x679e…f0110xee72…977c | Base | $0.01 | 100% | coinbase | 118d ago | 0xb94d4e…bc497e |
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 0x679ee8fbdaece0673750b80765bed7a06ce6f011 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x679ee8fbdaece0673750b80765bed7a06ce6f011
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: 0x679ee8fbdaece0673750b80765bed7a06ce6f011 curl -s 'https://api.roundhouseai.io/v0/agents/0x679ee8fbdaece0673750b80765bed7a06ce6f011' curl -s 'https://api.roundhouseai.io/v0/entities/0x679ee8fbdaece0673750b80765bed7a06ce6f011/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.