0xabf4…a9d0
Paid $31.00 of the $259.19M Roundhouse has indexed across 714,332 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1003)
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% | $31.00 | 3 | 2 |
$21.00 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 18d ago$21.002 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 6d 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,003 most recent settlements of 31,785 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.
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 | $21.00 | $0.00 | 2 | 18d ago | Graph |
| 0x2a83…9453 | $10.00 | $0.00 | 1 | 6d ago | Graph |
| 0x902d…8256 | $0.00 | $9.69 | 671 | 5h ago | Graph |
| 0x72c5…159b | $0.00 | $1.28 | 13 | 33m ago | Graph |
| 0xc9c7…1670 | $0.00 | $0.82 | 41 | 3h ago | Graph |
| 0x7be3…11b7 | $0.00 | $0.40 | 199 | 2h ago | Graph |
| 0x91f1…f880 | $0.00 | $0.20 | 10 | 1d ago | Graph |
| 0x8749…bc9c | $0.00 | $0.18 | 6 | 1d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
Not enough of this address's history was examined to assess it: self_dealing and counterparty_concentration and single_counterparty were computed over the 1003 most recent settlements scanned (its history is longer than the 2000-row scan cap), so nothing found there rules anything out. This is an incomplete check, not a clean record.
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. 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.