0x1e6d…05ff
Paid $0.17 of the $3066.54M Roundhouse has indexed across 1,400,689 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (18)
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 | 65% | $0.11 | 12 | 3 |
| Web & Content | 35% | $0.06 | 6 | 1 |
$0.01 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 4 the amount paid narrows the list to the ones listed at that price.
- 0x8324…fd0e · last paid 308d ago$0.1010 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /x402/tools/analyze_tokenPrice match$0.01 listed
- 0xca12…cd0c · last paid 308d ago$0.066 calls
▸5 catalogued endpoints, none priced at an amount this agent paid
- /newsNews search$0.03 listed
- /news-by-keyword$0.05 listed
- /news-ticker-summary$0.03 listed
- /recaps$0.10 listed
- /pm-scorings$0.10 listed
- 0x9d11…3546 · last paid 309d ago$0.011 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x0773…4d39 · last paid 308d ago$0.0011 call
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/x402/pingPrice match$0.001 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 | |
|---|---|---|---|---|---|
| 0x8324…fd0e | $0.10 | $0.00 | 10 | 308d ago | Graph |
| 0xca12…cd0c | $0.06 | $0.00 | 6 | 308d ago | Graph |
| 0x9d11…3546 | $0.01 | $0.00 | 1 | 309d ago | Graph |
| 0x0773…4d39 | $0.001 | $0.00 | 1 | 308d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
58% of observed volume is with a single counterparty, in all 18 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 0x1e6d…05ff has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x1e6d80ba69e86c5b891ecc8d8e184d02b40305ff
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: 0x1e6d…05ff curl -s 'https://api.roundhouseai.io/v0/agents/0x1e6d80ba69e86c5b891ecc8d8e184d02b40305ff' curl -s 'https://api.roundhouseai.io/v0/entities/0x1e6d80ba69e86c5b891ecc8d8e184d02b40305ff/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.