AgentReport

0x3d5c…1265

0x3d5c24f9861c9b3e51f49f4c5d17dad31d2d1265Explorer
Paid out
$5.89
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
57
Last 7d vs prior 7d
13
Distinct counterparties
Over the whole indexed history

Paid $5.89 of the $3060.46M Roundhouse has indexed across 1,397,861 wallets — less than 0.0001% of it.

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

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
Web & Content92%$5.41356
Not in any catalogue5%$0.3222
Company & People2%$0.11122
AI & Media<1%$0.0231
Reference Data<1%$0.0231

$0.29 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 10 of 12 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
0x19a0…a454$5.25$0.001565d agoGraph
0xeadb…e9b7$0.29$0.00117d agoGraph
0x9dba…0df8$0.13$0.001565d agoGraph
0x32a1…e5c3$0.11$0.001165d agoGraph
0x02c2…3043$0.03$0.00165d agoGraph
0xb1ef…88c0$0.02$0.00365d agoGraph
0x0e84…b808$0.02$0.00365d agoGraph
0xefcd…5669$0.01$0.00265d agoGraph

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

Data quality

89% of observed volume is with a single counterparty, in all 57 observed settlements.

Recent activity

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

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

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: 0x3d5c…1265

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