0x9dba…0df8
Paid $2.00 of the $3053.48M Roundhouse has indexed across 1,395,044 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1002)
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% | $2.00 | 2 | 2 |
$1.00 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x2a83…9453 · last paid 96d ago$1.001 call
▸1 catalogued endpoints, none priced at an amount this agent paid
- /api/base/paid-content$0.01 listed
- 0x2d3c…33c2 · last paid 242d ago$1.001 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,002 most recent settlements of 408,829 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 | |
|---|---|---|---|---|---|
| 0xe577…93aa | $0.00 | $2.05 | 308 | 3h ago | Graph |
| 0x6b6a…1ff1 | $0.00 | $1.10 | 183 | 6m ago | Graph |
| 0xd3f2…edda | $0.00 | $1.09 | 131 | 3h ago | Graph |
| 0x2a83…9453 | $1.00 | $0.00 | 1 | 96d ago | Graph |
| 0x2d3c…33c2 | $1.00 | $0.00 | 1 | 242d ago | Graph |
| 0xd97c…0093 | $0.00 | $0.62 | 89 | 5h ago | Graph |
| 0x680b…4ff8 | $0.00 | $0.58 | 77 | 21h ago | Graph |
| 0x9efa…0352 | $0.00 | $0.36 | 60 | 4h ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
Not enough of this address's history was examined to assess it: self_dealing and counterparty_concentration and single_counterparty were computed over the 1002 most recent settlements scanned (its history is longer than the 2000-row scan cap), so nothing found there rules anything out. This is an incomplete check, not a clean record.
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 0x9dba…0df8 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9dba414637c611a16bea6f0796bfcbcbdc410df8
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: 0x9dba…0df8 curl -s 'https://api.roundhouseai.io/v0/agents/0x9dba414637c611a16bea6f0796bfcbcbdc410df8' curl -s 'https://api.roundhouseai.io/v0/entities/0x9dba414637c611a16bea6f0796bfcbcbdc410df8/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.