0x1611…d499
Paid $7.72 of the $3059.84M Roundhouse has indexed across 1,397,496 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (75)
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% | $7.72 | 55 | 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x161d…7fb9 · last paid 129d ago$7.7255 calls
▸22 catalogued endpoints, none priced at an amount this agent paid
- /regime$0.02 listed
- /validate$0.25 listed
- /reason$0.08 listed
- /decision-receipt$0.08 listed
- /signals/full$0.03 listed
- /review$0.83 listed
- /memory/get$0.02 listed
- /residence/act$0.21 listed
14 further catalogued endpoints not 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 | |
|---|---|---|---|---|---|
| 0x161d…7fb9 | $7.72 | $8.00 | 75 | 129d 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 all 75 observed settlements.
Organic volume $15.72 of $15.72 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 0x1611…d499 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x1611cf65193a4830fca47643e7825e5eacddd499
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: 0x1611…d499 curl -s 'https://api.roundhouseai.io/v0/agents/0x1611cf65193a4830fca47643e7825e5eacddd499' curl -s 'https://api.roundhouseai.io/v0/entities/0x1611cf65193a4830fca47643e7825e5eacddd499/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.