0x7d26…c9c4
Paid $0.28 of the $259.14M Roundhouse has indexed across 714,236 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.28 | 4 | 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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0x64e4…89e4 · last paid 14d ago$0.284 calls
▸2 of 4 catalogued endpoints list a price this agent paid
- /v1/services/wallet_risk_snapshotPrice match$0.01 listed
- /v1/services/arc_wallet_intelPrice match$0.01 listed
- /v1/services/arc_token_diligence$0.20 listed
- /v1/services/robinhood_token_traction_audit$0.05 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 | |
|---|---|---|---|---|---|
| 0x64e4…89e4 | $0.28 | $0.00 | 4 | 14d 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 4 observed settlements.
Organic volume $0.28 of $0.28 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x7d26…c9c40x64e4…89e4 | Base | $0.01 | 100% | coinbase | 14d ago | 0x9f6c81…af06b0 |
| 0x7d26…c9c40x64e4…89e4 | Base | $0.01 | 100% | coinbase | 15d ago | 0x8f17fd…3189a3 |
| 0x7d26…c9c40x64e4…89e4 | Base | $0.01 | 100% | coinbase | 15d ago | 0xc77af6…cf7bd6 |
| 0x7d26…c9c40x64e4…89e4 | Base | $0.25 | 100% | coinbase | 38d ago | 0x0fe1ed…900733 |
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 0x7d26…c9c4 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7d266b7c2a733ed84e32ad68764e685f1c5dc9c4
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: 0x7d26…c9c4 curl -s 'https://api.roundhouseai.io/v0/agents/0x7d266b7c2a733ed84e32ad68764e685f1c5dc9c4' curl -s 'https://api.roundhouseai.io/v0/entities/0x7d266b7c2a733ed84e32ad68764e685f1c5dc9c4/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.