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.43M Roundhouse has indexed across 1,401,742 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%daydreams326d ago0x549a7a…53a7b5
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams326d ago0xd3c99c…4d5c8e
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams326d ago0x535804…255947
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams326d ago0xb084e3…7f5550
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams326d ago0xac0e5d…e80d74
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams326d ago0x771d94…7b2280
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams326d ago0x88e919…cd48fb
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams326d ago0x6dda54…909b2c
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams327d ago0x0911a3…672a00
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams327d ago0x85c108…fa2115
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams327d ago0xae9ecd…d4cd24
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams327d ago0x1a041a…beeafd
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams327d ago0x317cfc…8055e9
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams327d ago0xc2e582…b08003
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams327d ago0x614aa4…636ca6
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams327d ago0x7175f1…66746a
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams328d ago0x800049…ec1579
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams328d ago0x26ba2d…0fa114
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams328d ago0x63cb72…6ba287
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams328d ago0xb02d95…ac8c58
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams335d ago0xc4924f…6ecdb0
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams337d ago0x674556…9389a8
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams337d ago0x841b41…aad10b
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams337d ago0xa9898a…166b9c
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams337d ago0xca940e…90626b

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.