0xabf4…a9d0
Paid $63.25 of the $3058.83M Roundhouse has indexed across 1,396,904 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1004)
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% | $63.25 | 4 | 2 |
$53.25 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x47c5…4fc3 · last paid 33d ago$53.253 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x2a83…9453 · last paid 51d ago$10.001 call
▸1 catalogued endpoints, none priced at an amount this agent paid
- /api/base/paid-content$0.01 listed
Folded from this wallet's 1,004 most recent settlements of 51,210 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 5 endpoints, and 1 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 | |
|---|---|---|---|---|---|
| 0x47c5…4fc3 | $53.25 | $0.00 | 3 | 33d ago | Graph |
| 0x902d…8256 | $0.00 | $25.42 | 571 | 4h ago | Graph |
| 0x2a83…9453 | $10.00 | $0.00 | 1 | 51d ago | Graph |
| 0x7a21…5c58 | $0.00 | $2.22 | 74 | 55m ago | Graph |
| 0x7be3…11b7 | $0.00 | $0.47 | 233 | 1h ago | Graph |
| 0xdd06…8948 | $0.00 | $0.21 | 2 | 3d ago | Graph |
| 0x72c5…159b | $0.00 | $0.20 | 44 | 1d ago | Graph |
| 0xc9c7…1670 | $0.00 | $0.17 | 7 | 1d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
58% of observed volume is with a single counterparty, in the 1004 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 0xabf4…a9d0 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0
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: 0xabf4…a9d0 curl -s 'https://api.roundhouseai.io/v0/agents/0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0' curl -s 'https://api.roundhouseai.io/v0/entities/0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0/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.