0x663f…1671
Paid $6.71 of the $3058.83M Roundhouse has indexed across 1,396,904 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (6)
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% | $6.71 | 4 | 2 |
$6.68 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.
- 0xccc8…15be · last paid 165d ago$6.682 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x7dd5…2629 · last paid 165d ago$0.032 calls
▸2 of 127 catalogued endpoints list a price this agent paid
- /api/tts/elevenlabs$0.02 listed
- /api/crypto/priceCrypto spot price$0.001 listed
- /api/travel/flights$0.02 listed
- /api/llm/kat-coder-pro-v2.5$0.01 listed
- /api/ipfs/pin$0.01 listed
- /api/crypto/trending$0.001 listed
- /api/travel/hotels$0.02 listed
- /api/ens/resolve$0.001 listed
119 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
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 | |
|---|---|---|---|---|---|
| 0x2ead…69d7 | $0.00 | $60.00 | 2 | 164d ago | Graph |
| 0xccc8…15be | $6.68 | $0.00 | 2 | 165d ago | Graph |
| 0x7dd5…2629 | $0.03 | $0.00 | 2 | 165d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
90% of observed volume is with a single counterparty, in all 6 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x2ead…69d70x663f…1671 | Base | $50.00 | 70% | 0xa923…c9ac | 164d ago | 0x1ec88d…9265ff |
| 0x663f…16710x7dd5…2629 | Base | $0.02 | 100% | coinbase | 165d ago | 0xb23edd…eae1c8 |
| 0x663f…16710xccc8…15be | Base | $4.43 | 70% | 0xf70d…dbef | 165d ago | 0xab7564…9d0d62 |
| 0x663f…16710xccc8…15be | Base | $2.25 | 70% | 0xf70d…dbef | 165d ago | 0x64ab37…b52e8e |
| 0x663f…16710x7dd5…2629 | Base | $0.02 | 100% | coinbase | 165d ago | 0x3489f6…05d393 |
| 0x2ead…69d70x663f…1671 | Base | $10.00 | 70% | 0xa923…c9ac | 165d ago | 0x03df9c…659a45 |
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 0x663f…1671 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x663ff50324784fdbbcdd34196697696563561671
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: 0x663f…1671 curl -s 'https://api.roundhouseai.io/v0/agents/0x663ff50324784fdbbcdd34196697696563561671' curl -s 'https://api.roundhouseai.io/v0/entities/0x663ff50324784fdbbcdd34196697696563561671/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.