0x07c3…4015
Paid $6,145.32 of the $3154.54M Roundhouse has indexed across 1,426,781 wallets — 0.0002% of it.
Chains (from the recent scan): Robinhood Chain (2) · Ethereum (1)
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% | $6,145.32 | 3 | 2 |
$6,145.32 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.
- 0x5c7b…35c5 · last paid 1h ago$3,072.791 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x94ba…ff9d · last paid 45m ago$3,072.532 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x5c7b…35c5 | $3,072.79 | $0.00 | 1 | 1h ago | Graph |
| 0x94ba…ff9d | $3,072.53 | $0.00 | 2 | 45m ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
50% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x07c3…40150x94ba…ff9d | Robinhood Chain | $3,000.00 | 70% | 0xb381…ae08 | 45m ago | 0xbffb74…929386 |
| 0x07c3…40150x94ba…ff9d | Robinhood Chain | $72.53 | 70% | 0xb381…ae08 | 59m ago | 0x04646c…d60076 |
| 0x07c3…40150x5c7b…35c5 | Ethereum | $3,072.79 | 70% | 0x07ae…0e67 | 1h ago | 0x01e81f…b6c75c |
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 0x07c3…4015 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x07c3defa9fad9c8ee0a1526102abcd25d9254015
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: 0x07c3…4015 curl -s 'https://api.roundhouseai.io/v0/agents/0x07c3defa9fad9c8ee0a1526102abcd25d9254015' curl -s 'https://api.roundhouseai.io/v0/entities/0x07c3defa9fad9c8ee0a1526102abcd25d9254015/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.