0x7e27…e7a3
Paid $628.54 of the $3066.17M Roundhouse has indexed across 1,399,970 wallets — less than 0.0001% of it.
Whole-history totals from the index rollup, which can be up to 30 minutes behind.
Chains (from the recent scan): Ethereum (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 |
|---|---|---|---|---|
| Onchain Data | 100% | $628.54 | 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x0000…0000 · last paid 64d ago$628.544 calls
▸1 catalogued endpoints, none priced at an amount this agent paid
- /x402/gasGas price$5.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 | |
|---|---|---|---|---|---|
| 0x0000…0000 | $628.54 | $0.00 | 4 | 64d 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 $628.54 of $628.54 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x7e27…e7a30x0000…0000 | Ethereum | $160.46 | 70% | 0x39d6…3765 | 64d ago | 0xbc8e26…0c546f |
| 0x7e27…e7a30x0000…0000 | Ethereum | $60.71 | 70% | 0x39d6…3765 | 114d ago | 0x154cd2…e5cd36 |
| 0x7e27…e7a30x0000…0000 | Ethereum | $121.62 | 70% | 0x39d6…3765 | 114d ago | 0x6586d0…62daa0 |
| 0x7e27…e7a30x0000…0000 | Ethereum | $285.76 | 70% | 0x39d6…3765 | 114d ago | 0x77a503…883d7a |
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 0x7e27…e7a3 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7e2752118d9377dd85eff48e4ea0cbbe8949e7a3
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: 0x7e27…e7a3 curl -s 'https://api.roundhouseai.io/v0/agents/0x7e2752118d9377dd85eff48e4ea0cbbe8949e7a3' curl -s 'https://api.roundhouseai.io/v0/entities/0x7e2752118d9377dd85eff48e4ea0cbbe8949e7a3/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. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.