0xe270…5c8f
Paid $4.44 of the $259.89M Roundhouse has indexed across 715,350 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (44)
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 | 53% | $2.34 | 2 | 1 |
| AI & Media | 47% | $2.10 | 42 | 1 |
$2.34 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 64d ago$2.342 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xabf4…a9d0 · last paid 64d ago$2.1042 calls
▸5 of 200 catalogued endpoints list a price this agent paid
- /api/ttsPrice matchText to speech$0.05 listed
- /api/perp-fundingPerp funding and open interest$0.002 listed
- /api/perp-basis$0.002 listed
- /api/hash$0.001 listed
- /api/sol-token-safety$0.005 listed
- /v1/nano/chat/completionsText completion$0.003 listed
- /api/bestsellers$0.005 listed
- /api/demand-radar$0.005 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 | |
|---|---|---|---|---|---|
| 0xccc8…15be | $2.34 | $0.00 | 2 | 64d ago | Graph |
| 0xabf4…a9d0 | $2.10 | $0.00 | 42 | 64d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
53% of observed volume is with a single counterparty, in all 44 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 0xe270…5c8f has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xe270116023eb1951093f2f11d97149c7552e5c8f
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: 0xe270…5c8f curl -s 'https://api.roundhouseai.io/v0/agents/0xe270116023eb1951093f2f11d97149c7552e5c8f' curl -s 'https://api.roundhouseai.io/v0/entities/0xe270116023eb1951093f2f11d97149c7552e5c8f/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.