0x3a6d…a361
Paid $3,064.00 of the $846.98M Roundhouse has indexed across 1,330,524 wallets — 0.0004% 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% | $3,064.00 | 4 | 2 |
$3,064.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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xf269…b3fa · last paid 510d ago$2,000.002 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x06e9…01d5 · last paid 510d ago$1,064.002 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 | |
|---|---|---|---|---|---|
| 0xf269…b3fa | $2,000.00 | $0.00 | 2 | 510d ago | Graph |
| 0x06e9…01d5 | $1,064.00 | $0.00 | 2 | 510d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
65% of observed volume is with a single counterparty, in all 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x3a6d…a3610x06e9…01d5 | Base | $1,063.00 | 70% | 0xe890…f632 | 510d ago | 0xd067f4…6d2cbe |
| 0x3a6d…a3610x06e9…01d5 | Base | $1.00 | 70% | 0xe890…f632 | 510d ago | 0x9ea317…48d97c |
| 0x3a6d…a3610xf269…b3fa | Base | $1,998.00 | 70% | 0xe890…f632 | 510d ago | 0xaec1bb…5b18be |
| 0x3a6d…a3610xf269…b3fa | Base | $2.00 | 70% | 0xe890…f632 | 510d ago | 0x267b20…92175b |
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 0x3a6d…a361 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x3a6db2248b69b8da17e92758ce4a7947f339a361
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: 0x3a6d…a361 curl -s 'https://api.roundhouseai.io/v0/agents/0x3a6db2248b69b8da17e92758ce4a7947f339a361' curl -s 'https://api.roundhouseai.io/v0/entities/0x3a6db2248b69b8da17e92758ce4a7947f339a361/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.