0x69ee…e515
Paid $0.004 of the $261.24M Roundhouse has indexed across 717,221 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (4)
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% | $0.004 | 4 | 2 |
$0.003 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 2 the amount paid narrows the list to the ones listed at that price.
- 0xd0cb…1f5c · last paid 336d ago$0.0033 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x71dc…aaf4 · last paid 328d ago$0.0011 call
▸1 of 16 catalogued endpoints list a price this agent paid
- /tools/web3/evm/eth-get-code$0.0001 listed
- /tools/web3/evm/eth-get-storage-at$0.0001 listed
- /tools/web3/evm/eth-get-uncle-count-by-block-hash$0.0001 listed
- /tools/web3/evm/web3-sha3$0.0001 listed
- /tools/web3/evm/eth-get-transaction-count$0.0001 listed
- /tools/web3/evm/eth-coinbase$0.0001 listed
- /tools/web3/evm/eth-protocol-version$0.0001 listed
- /tools/web3/evm/net-listening$0.0001 listed
8 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 | |
|---|---|---|---|---|---|
| 0xd0cb…1f5c | $0.003 | $0.00 | 3 | 336d ago | Graph |
| 0x71dc…aaf4 | $0.001 | $0.00 | 1 | 328d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
75% of observed volume is with a single counterparty, in all 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x69ee…e5150x71dc…aaf4 | Base | $0.001 | 100% | daydreams | 328d ago | 0xd7e122…2e7005 |
| 0x69ee…e5150xd0cb…1f5c | Base | $0.001 | 100% | coinbase | 336d ago | 0x3062ca…4e3195 |
| 0x69ee…e5150xd0cb…1f5c | Base | $0.001 | 100% | coinbase | 336d ago | 0x54eada…32f5a0 |
| 0x69ee…e5150xd0cb…1f5c | Base | $0.001 | 100% | coinbase | 336d ago | 0xa1a95f…7525bc |
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 0x69ee…e515 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x69ee7399a34af73c1e887b7b768ca37798c3e515
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: 0x69ee…e515 curl -s 'https://api.roundhouseai.io/v0/agents/0x69ee7399a34af73c1e887b7b768ca37798c3e515' curl -s 'https://api.roundhouseai.io/v0/entities/0x69ee7399a34af73c1e887b7b768ca37798c3e515/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.