AgentReport

0xcd65…0227

0xcd6596c5129e7851b0aae49f5353754991da0227Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
265
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.84M Roundhouse has indexed across 1,401,919 wallets — less than 0.0001% of it.

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

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 catalogue100%$0.032651

$0.03 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.

  • 0x6482…b779 · last paid 276d ago
    $0.03
    265 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

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
0x6482…b779$0.03$0.00265276d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 265 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams341d ago0x573c86…c740b2
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams341d ago0xacd2eb…61a2be
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams341d ago0x49b036…101e31
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams341d ago0xb0b904…43c437
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams342d ago0xce4117…e3f6c3
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams342d ago0x2a6e5b…a8b82d
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams342d ago0x160b72…75e8a0
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams342d ago0xa97c7f…2d9484
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams342d ago0x58077e…2af583
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams342d ago0x7b665a…f1326f
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams342d ago0x0334fa…6036df
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams342d ago0x5222cf…1a423a
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams342d ago0x26ef9c…1a715d
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams342d ago0x07aae6…2864f2
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams343d ago0x523367…cb5875
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams343d ago0xc7133e…85f07f
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams343d ago0xe119a7…dd5aa2
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams343d ago0x1da1c1…ff7b9b
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams343d ago0x05c253…c558aa
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams343d ago0x84eec8…45160f
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams343d ago0x49a92a…4e455d
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams343d ago0xf81831…1dc6b7
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams343d ago0x38480c…fd00d7
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams343d ago0x7eec12…ac11e0
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams343d ago0x564bf2…300e7d

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

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

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: 0xcd65…0227

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