0x44c7…0caf
Paid $0.02 of the $261.16M Roundhouse has indexed across 717,066 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (2)
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.02 | 2 | 2 |
$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 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x4e9b…5edb · last paid 333d ago$0.011 call
▸4 of 7 catalogued endpoints list a price this agent paid
- /token/gems-listPrice match$0.01 listed
- /token/leaderboardPrice match$0.01 listed
- /token/gems-listPrice match$0.01 listed
- /token/leaderboardPrice match$0.01 listed
- /twitter/@canza_io$0.10 listed
- /twitter/@canza_io$1.00 listed
- /token/address$0.10 listed
- 0xc717…b2bc · last paid 333d 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.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x4e9b…5edb | $0.01 | $0.00 | 1 | 333d ago | Graph |
| 0xc717…b2bc | $0.01 | $0.00 | 1 | 333d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
50% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x44c7…0caf0x4e9b…5edb | Base | $0.01 | 100% | x402rs | 333d ago | 0x237ecc…0d0240 |
| 0x44c7…0caf0xc717…b2bc | Base | $0.01 | 100% | openx402 | 333d ago | 0x4aadea…9ee0ae |
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 0x44c7…0caf has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x44c77e17f41e2661d0b2c8db971bd74982230caf
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: 0x44c7…0caf curl -s 'https://api.roundhouseai.io/v0/agents/0x44c77e17f41e2661d0b2c8db971bd74982230caf' curl -s 'https://api.roundhouseai.io/v0/entities/0x44c77e17f41e2661d0b2c8db971bd74982230caf/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.