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%daydreams337d ago0xdd01bf…067179
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams338d ago0x3dc6df…f94fd3
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams338d ago0x60e09d…924494
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams338d ago0xc0eb26…f47a4c
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams338d ago0xffb9f3…2383a7
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams338d ago0x480ec7…fa7f6c
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams338d ago0x2ca34c…27e14a
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams339d ago0x49e23f…4ac62a
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams339d ago0xdff50e…15b804
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams340d ago0xc47fe6…5f74b0
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams340d ago0x24186c…567344
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams340d ago0xb3e451…7b1ed3
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams340d ago0x1cc73c…c4e455
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams340d ago0xb5f8dc…9dd90d
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams340d ago0x49bcc4…d59be3
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams340d ago0x841d99…d76361
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams340d ago0xc17a5f…f067d0
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams340d ago0x086e7e…ebddea
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams340d ago0x0607e8…08adcd
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams340d ago0x9a316c…31db35
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams341d ago0x7923fc…330265
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams341d ago0xf3df8c…1687ef
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams341d ago0xb8fbfe…2df865
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams341d ago0x5c9b96…cfcc8e
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams341d ago0xb7c4ef…4c90fb

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.