0x63c3…c897
Paid $0.01 of the $3063.39M Roundhouse has indexed across 1,398,970 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (40)
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.01 | 1 | 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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0xecb6…ee4d · last paid 316d ago$0.011 call
▸2 of 8 catalogued endpoints list a price this agent paid
- /api/get_portfolioPrice match$0.01 listed
- /api/get_swap_quotePrice match$0.01 listed
- /api/get_transaction_status$0.001 listed
- /api/execute_swap$0.02 listed
- /api/search_token$0.001 listed
- /api/submit_transaction_hash$0.005 listed
- /api/get_balances$0.005 listed
- /api/get_token_price$0.002 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 | |
|---|---|---|---|---|---|
| 0x90b1…6787 | $0.00 | $0.11 | 11 | 6d ago | Graph |
| 0x7e57…2f09 | $0.00 | $0.10 | 10 | 106d ago | Graph |
| 0x3eef…a439 | $0.00 | $0.03 | 3 | 64d ago | Graph |
| 0xa1d1…1978 | $0.00 | $0.02 | 2 | 10d ago | Graph |
| 0x1d86…e2fa | $0.00 | $0.02 | 2 | 21d ago | Graph |
| 0x9110…35fa | $0.00 | $0.02 | 2 | 40d ago | Graph |
| 0xa918…c7a6 | $0.00 | $0.02 | 2 | 63d ago | Graph |
| 0x7e80…fe7a | $0.00 | $0.02 | 2 | 122d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
No concentration or self-dealing patterns detected in all 40 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 0x63c3…c897 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x63c347d7e42b940e79afec3d172bfc2921b6c897
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: 0x63c3…c897 curl -s 'https://api.roundhouseai.io/v0/agents/0x63c347d7e42b940e79afec3d172bfc2921b6c897' curl -s 'https://api.roundhouseai.io/v0/entities/0x63c347d7e42b940e79afec3d172bfc2921b6c897/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.