0x2888…fe70
Paid $0.08 of the $260.63M Roundhouse has indexed across 716,280 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (4)
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.08 | 4 | 2 |
$0.05 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xa8ce…b0c5 · last paid 331d ago$0.051 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xde3e…0e08 · last paid 326d ago$0.033 calls
▸1 catalogued endpoints, none priced at an amount this agent paid
- /inference-api/agent/v1/parse-pdf$0.00 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 | |
|---|---|---|---|---|---|
| 0xa8ce…b0c5 | $0.05 | $0.00 | 1 | 331d ago | Graph |
| 0xde3e…0e08 | $0.03 | $0.00 | 3 | 326d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
63% of observed volume is with a single counterparty, in all 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x2888…fe700xde3e…0e08 | Base | $0.00997 | 100% | thirdweb | 326d ago | 0x921ad3…420d4f |
| 0x2888…fe700xde3e…0e08 | Base | $0.00997 | 100% | thirdweb | 326d ago | 0x76b887…0c61c2 |
| 0x2888…fe700xa8ce…b0c5 | Base | $0.05 | 100% | thirdweb | 331d ago | 0x12d87f…7e1c8e |
| 0x2888…fe700xde3e…0e08 | Base | $0.00997 | 100% | thirdweb | 331d ago | 0x379c22…4077cb |
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 0x2888…fe70 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x2888a8646c28a49ef8ddaa5d1a033d0b2071fe70
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: 0x2888…fe70 curl -s 'https://api.roundhouseai.io/v0/agents/0x2888a8646c28a49ef8ddaa5d1a033d0b2071fe70' curl -s 'https://api.roundhouseai.io/v0/entities/0x2888a8646c28a49ef8ddaa5d1a033d0b2071fe70/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.