0x9af9…ce09
Paid $269.00 of the $3067.00M Roundhouse has indexed across 1,401,091 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1000)
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% | $250.00 | 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.
- 0x75dd…d2a5 · last paid 2m ago$250.001,000 calls
▸5 of 20 catalogued endpoints list a price this agent paid
- /token-unlocks/v1/allocationsPrice match$0.25 listed
- /metrics/v2/assets/roi$0.75 listed
- /signal/v1/assets/mindshare-gainers-24h$0.35 listed
- /funding/v1/rounds$0.15 listed
- /funding/v1/funds$0.35 listed
- /news/v1/news/feed$0.55 listed
- /funding/v1/projects$0.15 listed
- /signal/v1/assets/mindshare-losers-7d$0.35 listed
12 further catalogued endpoints not listed.
Folded from this wallet's 1,000 most recent settlements of 1,076 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 | |
|---|---|---|---|---|---|
| 0x75dd…d2a5 | $250.00 | $0.00 | 1,000 | 2m 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 the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).
Organic volume $250.00 of $250.00 total.
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 0x9af9…ce09 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9af9e3011ecf57936114903b8fd98d398d5bce09
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: 0x9af9…ce09 curl -s 'https://api.roundhouseai.io/v0/agents/0x9af9e3011ecf57936114903b8fd98d398d5bce09' curl -s 'https://api.roundhouseai.io/v0/entities/0x9af9e3011ecf57936114903b8fd98d398d5bce09/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.