0x9837…1a4b
Paid $0.04 of the $3063.39M Roundhouse has indexed across 1,398,970 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (15)
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 | 89% | $0.03 | 11 | 2 |
| Onchain Data | 11% | $0.004 | 4 | 1 |
$0.03 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 3 the amount paid narrows the list to the ones listed at that price.
- 0x4430…baee · last paid 26d ago$0.036 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x40d1…9bff · last paid 54d ago$0.0055 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x581a…aa1c · last paid 53d ago$0.0044 calls
▸3 of 5 catalogued endpoints list a price this agent paid
- /api/tokensPrice match$0.001 listed
- /api/token/:mintPrice matchToken metadata$0.001 listed
- /api/quotePrice matchCrypto spot price$0.001 listed
- /api/router/volume$0.01 listed
- /api/tx/build$0.005 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 | |
|---|---|---|---|---|---|
| 0x4430…baee | $0.03 | $0.00 | 6 | 26d ago | Graph |
| 0x40d1…9bff | $0.005 | $0.00 | 5 | 54d ago | Graph |
| 0x581a…aa1c | $0.004 | $0.00 | 4 | 53d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
76% of observed volume is with a single counterparty, in all 15 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 0x9837…1a4b has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x98376598e4f8b5e3e3df0505d4a6218714a61a4b
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: 0x9837…1a4b curl -s 'https://api.roundhouseai.io/v0/agents/0x98376598e4f8b5e3e3df0505d4a6218714a61a4b' curl -s 'https://api.roundhouseai.io/v0/entities/0x98376598e4f8b5e3e3df0505d4a6218714a61a4b/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.