0x29e7…56c5
Paid $1.05 of the $258.35M Roundhouse has indexed across 712,918 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (3)
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% | $1.05 | 2 | 2 |
$1.00 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.
- 0x5da4…6c70 · last paid 8h ago$1.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x71bc…f42b · last paid 6h ago$0.051 call
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/agent/v1/services/website-quick-checkPrice match$0.05 listed
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x71bc…f42b | $0.05 | $2.00 | 2 | 6h ago | Graph |
| 0x5da4…6c70 | $1.00 | $0.00 | 1 | 8h ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
67% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x29e7…56c50x71bc…f42b | Base | $0.05 | 100% | coinbase | 6h ago | 0x3c52c1…0e2b0f |
| 0x29e7…56c50x5da4…6c70 | Base | $1.00 | 70% | 0x35ad…204d | 8h ago | 0x1e5940…e581a1 |
| 0x71bc…f42b0x29e7…56c5 | Base | $2.00 | 70% | 0xa923…c9ac | 8h ago | 0x26fe1f…cd86eb |
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 0x29e7…56c5 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x29e7e7e24ab53c34b215269f190bbedc6e7556c5
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: 0x29e7…56c5 curl -s 'https://api.roundhouseai.io/v0/agents/0x29e7e7e24ab53c34b215269f190bbedc6e7556c5' curl -s 'https://api.roundhouseai.io/v0/entities/0x29e7e7e24ab53c34b215269f190bbedc6e7556c5/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.