0x2d3a…c423
Paid $22.30 of the $3053.48M Roundhouse has indexed across 1,395,044 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1243)
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 |
|---|---|---|---|---|
| Web & Content | 100% | $19.11 | 999 | 1 |
| Not in any catalogue | <1% | $0.009999 | 1 | 1 |
$0.009999 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.
- 0xf22e…f493 · last paid 24d ago$19.11999 calls
▸200 of 200 catalogued endpoints list a price this agent paid
- /searchPrice matchWeb search$0.003 listed
- /search/newsPrice matchNews search$0.003 listed
- /crypto/hashPrice match$0.001 listed
- /crypto/convertPrice match$0.001 listed
- /quant/kellyPrice match$0.001 listed
- /convertPrice matchCurrency conversion$0.001 listed
- /legal/litigationPrice match$0.03 listed
- /extractPrice matchPage to markdown$0.002 listed
192 further catalogued endpoints not listed.
- 0x60f5…dd7c · last paid 44d ago$0.0099991 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Folded from this wallet's 1,243 most recent settlements of 1,507 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. One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
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 | |
|---|---|---|---|---|---|
| 0xf22e…f493 | $19.11 | $21.61 | 1,146 | 24d ago | Graph |
| 0x5e91…e1b3 | $0.00 | $0.03 | 1 | 125d ago | Graph |
| 0x2b0f…d4fb | $0.00 | $0.03 | 1 | 127d ago | Graph |
| 0x0d7b…d509 | $0.00 | $0.02 | 1 | 124d ago | Graph |
| 0x151c…e65e | $0.00 | $0.02 | 2 | 126d ago | Graph |
| 0xd127…13b5 | $0.00 | $0.02 | 2 | 127d ago | Graph |
| 0x0260…7d16 | $0.00 | $0.02 | 1 | 124d ago | Graph |
| 0x3c43…30cb | $0.00 | $0.02 | 1 | 128d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
99% of observed volume is with a single counterparty, in the 1243 most recent settlements scanned (its history is longer than the 2000-row scan cap).
Organic volume $41.21 of $41.21 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 0x2d3a…c423 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x2d3af92df6129878509f152e531e1bec2b34c423
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: 0x2d3a…c423 curl -s 'https://api.roundhouseai.io/v0/agents/0x2d3af92df6129878509f152e531e1bec2b34c423' curl -s 'https://api.roundhouseai.io/v0/entities/0x2d3af92df6129878509f152e531e1bec2b34c423/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.