0xd3f2…edda
Paid $8.63 of the $847.77M Roundhouse has indexed across 1,332,130 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 |
|---|---|---|---|---|
| Web & Content | 100% | $8.47 | 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.
- 0x9dba…0df8 · last paid 3m ago$8.471,000 calls
▸24 of 32 catalogued endpoints list a price this agent paid
- /tweets/userPrice match$0.01 listed
- /users/followersPrice match$0.01 listed
- /users/by/usernamePrice match$0.005 listed
- /users/by/idPrice match$0.005 listed
- /tweets/searchWeb search$0.006 listed
- /tweets/mentions$0.006 listed
- /tweets/by/id$0.0025 listed
- /tweets/mediaUpload$0.006 listed
24 further catalogued endpoints not listed.
Folded from this wallet's 1,000 most recent settlements of 1,018 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 | |
|---|---|---|---|---|---|
| 0x9dba…0df8 | $8.47 | $0.00 | 1,000 | 3m 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 $8.47 of $8.47 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 0xd3f2…edda has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xd3f2e4d2850d8487e41089a18f0df02b6c55edda
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: 0xd3f2…edda curl -s 'https://api.roundhouseai.io/v0/agents/0xd3f2e4d2850d8487e41089a18f0df02b6c55edda' curl -s 'https://api.roundhouseai.io/v0/entities/0xd3f2e4d2850d8487e41089a18f0df02b6c55edda/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.