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%daydreams323d ago0xfe5b70…7155ac
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams323d ago0x4054e1…3e293f
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams324d ago0xb8bbc1…3442b3
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams324d ago0x578f05…ba7185
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams324d ago0xe22314…774a42
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams324d ago0x58f5a0…13bcd6
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams324d ago0x453a7b…69484b
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams324d ago0x863bbc…74a042
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams324d ago0xc9c058…95a9cb
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams324d ago0x1d5d72…56c03c
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams324d ago0x412ab2…f67c2f
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams324d ago0xd0f3a6…39178a
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams325d ago0xf1bf78…f684d3
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams325d ago0x56f755…be36dd
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams325d ago0x09e65d…1738f5
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams325d ago0x4d732b…82b0b0
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams325d ago0xa45da3…bab7db
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams325d ago0x7a4895…4c930a
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams325d ago0x2f12b3…be7bf7
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams325d ago0xea157c…4c6452
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams325d ago0x4db5b0…1ad832
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams325d ago0x68438f…69bd2a
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams326d ago0xdde38f…68d25b
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams326d ago0x661201…1110f8
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams326d ago0xa475d5…feed24

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.