AgentReport

0x3d60…e638

0x3d60f5496b82083ffbf58a05fb76d32ae2aee638Explorer
Paid out
$42.44
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
72
Last 7d vs prior 7d
4
Distinct counterparties
Over the whole indexed history

Paid $42.44 of the $3066.54M Roundhouse has indexed across 1,400,843 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (72)

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.

GroupShareSpentCallsSellers
Not in any catalogue94%$40.0051
Crypto Markets6%$2.41602
Reference Data<1%$0.0371

$40.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 3 of 4 the amount paid narrows the list to the ones listed at that price.

One merchant publishes more endpoints than a single catalogue read returns; its list is partial.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x2670…293f$40.00$0.00538d agoGraph
0x1f81…39f1$2.07$0.004339d agoGraph
Kronos Crypto Data & Forecasts$0.34$0.001739d agoGraph
0x0e84…b808$0.03$0.00739d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

94% of observed volume is with a single counterparty, in all 72 observed settlements.

Organic volume $42.44 of $42.44 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x3d60…e638Kronos Crypto Data & ForecastsBaseBase$0.02100%coinbase47d ago0x396c7f…b10139
0x3d60…e6380x1f81…39f1BaseBase$0.05100%coinbase47d ago0x04f0d9…c28f78
0x3d60…e6380x1f81…39f1BaseBase$0.05100%coinbase47d ago0xd7423c…89d591
0x3d60…e6380x0e84…b808BaseBase$0.005100%coinbase47d ago0xc00b34…01d705
0x3d60…e6380x0e84…b808BaseBase$0.005100%coinbase47d ago0x04b5b7…a74548
0x3d60…e6380x0e84…b808BaseBase$0.005100%coinbase47d ago0x9acf92…99366f
0x3d60…e6380x1f81…39f1BaseBase$0.05100%coinbase47d ago0x3a01d6…88c509
0x3d60…e6380x1f81…39f1BaseBase$0.01100%coinbase47d ago0x7c4416…ad9714
0x3d60…e6380x1f81…39f1BaseBase$0.01100%coinbase47d ago0x883189…d87b0a
0x3d60…e638Kronos Crypto Data & ForecastsBaseBase$0.02100%coinbase47d ago0x3587d3…0bd7f3
0x3d60…e6380x1f81…39f1BaseBase$0.05100%coinbase47d ago0x5b56c5…f53eec
0x3d60…e638Kronos Crypto Data & ForecastsBaseBase$0.02100%coinbase47d ago0x256f3b…bb1e96
0x3d60…e6380x1f81…39f1BaseBase$0.05100%coinbase47d ago0x1e3ed5…116409
0x3d60…e638Kronos Crypto Data & ForecastsBaseBase$0.02100%coinbase47d ago0xfbdd9c…bef919
0x3d60…e638Kronos Crypto Data & ForecastsBaseBase$0.02100%coinbase47d ago0x4d1ebe…e583b7
0x3d60…e638Kronos Crypto Data & ForecastsBaseBase$0.02100%coinbase47d ago0xafccbf…af7375
0x3d60…e6380x1f81…39f1BaseBase$0.05100%coinbase47d ago0x680581…9d6eb4
0x3d60…e6380x0e84…b808BaseBase$0.003100%coinbase47d ago0xe9d1b5…f3ccca
0x3d60…e6380x1f81…39f1BaseBase$0.05100%coinbase47d ago0x4690f2…f765b0
0x3d60…e6380x1f81…39f1BaseBase$0.05100%coinbase47d ago0xfcc488…71fd20
0x3d60…e6380x2670…293fBaseBase$5.00100%coinbase47d ago0x0630f0…62f6b0
0x3d60…e6380x2670…293fBaseBase$5.00100%coinbase47d ago0x755850…79bb43

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 0x3d60…e638 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x3d60f5496b82083ffbf58a05fb76d32ae2aee638

Open skill.md
Show 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: 0x3d60…e638

curl -s 'https://api.roundhouseai.io/v0/agents/0x3d60f5496b82083ffbf58a05fb76d32ae2aee638'
curl -s 'https://api.roundhouseai.io/v0/entities/0x3d60f5496b82083ffbf58a05fb76d32ae2aee638/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.