0x6113…2d0b
Paid $29.00 of the $3060.46M Roundhouse has indexed across 1,397,861 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 | 64% | $1.79 | 897 | 1 |
| Crypto Markets | 36% | $1.03 | 103 | 1 |
$1.79 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; for 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xa9dd…2315 · last paid 131d ago$1.79897 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x9305…f13f · last paid 14m ago$1.03103 calls
▸36 of 64 catalogued endpoints list a price this agent paid
- /api/v1/profiler/address/current-balancePrice match$0.01 listed
- /api/v1/tgm/who-bought-soldPrice match$0.01 listed
- /api/v1/tgm/flow-intelligencePrice match$0.01 listed
- /api/v1/profiler/address/related-walletsPrice match$0.01 listed
- /api/v1/token-screenerPrice match$0.01 listed
- /api/v1/smart-money/dex-trades$0.05 listed
- /api/v1/smart-money/netflow$0.05 listed
- /api/v1/smart-money/perp-trades$0.05 listed
56 further catalogued endpoints not listed.
Folded from this wallet's 1,000 most recent settlements of 14,089 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 | |
|---|---|---|---|---|---|
| 0xa9dd…2315 | $1.79 | $0.00 | 897 | 131d ago | Graph |
| 0x9305…f13f | $1.03 | $0.00 | 103 | 14m ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
64% of observed volume is with a single counterparty, in the 1000 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 0x6113…2d0b has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x61139de852a77ea7e1afe9c45785dd04ef9a2d0b
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: 0x6113…2d0b curl -s 'https://api.roundhouseai.io/v0/agents/0x61139de852a77ea7e1afe9c45785dd04ef9a2d0b' curl -s 'https://api.roundhouseai.io/v0/entities/0x61139de852a77ea7e1afe9c45785dd04ef9a2d0b/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.