0xff51…e4bf
Paid $0.000138 of the $258.65M Roundhouse has indexed across 713,540 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 |
|---|---|---|---|---|
| Risk & Compliance | 100% | $0.000138 | 2 | 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.
- 0x2bb7…ac6d · last paid 101d ago$0.0001382 calls
▸200 catalogued endpoints, none priced at an amount this agent paid
- /proxy/supply-chain-finance-score-api-3c9435$0.005 listed
- /proxy/transition-finance-score-api-ddb242$0.005 listed
- /proxy/project-finance-score-api-fb6470$0.05 listed
- /proxy/refinance-calculator-api-9ebfbf$0.005 listed
- /proxy/refinance-breakeven-calculator-api-bd92dc$0.005 listed
- /proxy/email-free-provider-a95057$0.005 listed
- /proxy/campaign-update-score-api-2a1281$0.005 listed
- /proxy/on-chain-volume-score-api-7e996b$0.01 listed
192 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x2bb7…ac6d | $0.000138 | $0.00 | 2 | 101d 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 2 observed settlements.
Organic volume $0.000138 of $0.000138 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xff51…e4bf0x2bb7…ac6d | Base | $0.000069 | 5% | 0x6f92…3187 | 101d ago | 0x9d851d…211793 |
| 0xff51…e4bf0x2bb7…ac6d | Base | $0.000069 | 5% | 0x6f92…3187 | 101d ago | 0x9d851d…211793 |
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 0xff51…e4bf has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xff51dd913bbd5b6ac2027fc87d456ac22873e4bf
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: 0xff51…e4bf curl -s 'https://api.roundhouseai.io/v0/agents/0xff51dd913bbd5b6ac2027fc87d456ac22873e4bf' curl -s 'https://api.roundhouseai.io/v0/entities/0xff51dd913bbd5b6ac2027fc87d456ac22873e4bf/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.