0xd2de…2cf5
Paid $5.57 of the $3059.45M Roundhouse has indexed across 1,397,037 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (993)
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 |
|---|---|---|---|---|
| Crypto Markets | 56% | $3.10 | 298 | 1 |
| Not in any catalogue | 44% | $2.45 | 693 | 1 |
| Web & Content | <1% | $0.01 | 2 | 1 |
$2.45 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 2 of 3 the amount paid narrows the list to the ones listed at that price.
- 0x9305…f13f · last paid 7d ago$3.10298 calls
▸59 of 64 catalogued endpoints list a price this agent paid
- /api/v1/profiler/address/current-balancePrice match$0.01 listed
- /api/v1/smart-money/dex-tradesPrice match$0.05 listed
- /api/v1/tgm/who-bought-soldPrice match$0.01 listed
- /api/v1/smart-money/netflowPrice match$0.05 listed
- /api/v1/tgm/flow-intelligencePrice match$0.01 listed
- /api/v1/profiler/address/related-walletsPrice match$0.01 listed
- /api/v1/smart-money/perp-tradesPrice match$0.05 listed
- /api/v1/tgm/flowsPrice match$0.01 listed
56 further catalogued endpoints not listed.
- 0x2633…2223 · last paid 7d ago$2.45693 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x9dba…0df8 · last paid 153d ago$0.012 calls
▸24 of 32 catalogued endpoints list a price this agent paid
- /tweets/userPrice match$0.01 listed
- /tweets/by/idPrice match$0.0025 listed
- /lists/tweetsPrice match$0.01 listed
- /tweets/searchWeb search$0.006 listed
- /tweets/mentions$0.006 listed
- /users/by/username$0.005 listed
- /tweets/mediaUpload$0.006 listed
- /users/by/id$0.005 listed
24 further catalogued endpoints not listed.
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 | |
|---|---|---|---|---|---|
| 0x9305…f13f | $3.10 | $0.00 | 298 | 7d ago | Graph |
| 0x2633…2223 | $2.45 | $0.00 | 693 | 7d ago | Graph |
| 0x9dba…0df8 | $0.01 | $0.00 | 2 | 153d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
56% of observed volume is with a single counterparty, in all 993 observed settlements.
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 0xd2de…2cf5 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xd2dea3cd70b66c13ba44c1d23860ed50ffd32cf5
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: 0xd2de…2cf5 curl -s 'https://api.roundhouseai.io/v0/agents/0xd2dea3cd70b66c13ba44c1d23860ed50ffd32cf5' curl -s 'https://api.roundhouseai.io/v0/entities/0xd2dea3cd70b66c13ba44c1d23860ed50ffd32cf5/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.