0xf829…87fa
Paid $606.80 of the $3067.00M Roundhouse has indexed across 1,400,982 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1001)
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% | $426.03 | 1,000 | 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.
- 0x8755…c62e · last paid 98d ago$426.031,000 calls
▸17 of 17 catalogued endpoints list a price this agent paid
- /0xmesuthere/a2aPrice match$0.11 listed
- /mememancer_/a2aPrice match$0.11 listed
- /a2aPrice match$1.00 listed
- /0xwach_dev/a2aPrice match$0.11 listed
- /web3idan/a2aPrice match$0.11 listed
- /stonescris6/a2aPrice match$0.02 listed
- /thurty33z/a2aPrice match$0.11 listed
- /moltycash/a2aPrice match$0.11 listed
9 further catalogued endpoints not listed.
Folded from this wallet's 1,001 most recent settlements of 1,509 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.
ERC-8004 registration
- Declares 6 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 | |
|---|---|---|---|---|---|
| 0x8755…c62e | $426.03 | $0.00 | 1,000 | 98d ago | Graph |
| 0xb179…0a21 | $0.00 | $222.52 | 1 | 141d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
66% of observed volume is with a single counterparty, in the 1001 most recent settlements scanned (its history is longer than the 2000-row scan cap).
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 0xf829…87fa has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xf82971117baf73c42c04c6a0d619ba9d6aea87fa
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: 0xf829…87fa curl -s 'https://api.roundhouseai.io/v0/agents/0xf82971117baf73c42c04c6a0d619ba9d6aea87fa' curl -s 'https://api.roundhouseai.io/v0/entities/0xf82971117baf73c42c04c6a0d619ba9d6aea87fa/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.