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 $3068.58M Roundhouse has indexed across 1,402,563 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%daydreams353d ago0x93cfb7…af3fdc
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams353d ago0xa92f6a…adad5b
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams353d ago0x854ef4…8d945c
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams353d ago0x331917…15b5af
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams353d ago0x3c16c4…96198b
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams353d ago0x5cabd1…305413
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams354d ago0x54bc79…2f6c57
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams354d ago0x6c2d95…a87ab7
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams355d ago0xa22cd5…b64278
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams355d ago0x5a358b…2b28c8
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams355d ago0xf5234a…772062
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams355d ago0x7430e0…a57a47
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams356d ago0x05bbfa…a5f49b
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams356d ago0x984429…3d64c4
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams356d ago0x9d2a3c…e9ad29
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams356d ago0xfed084…57045a
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams357d ago0xe2762d…ac636c
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams357d ago0xbdb809…0a1527
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams357d ago0x5451e4…be738e
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams357d ago0x5d3b29…97b206
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams357d ago0xc347d9…a9bc8e
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams358d ago0x93a77f…08cf96
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams358d ago0xbacdad…fe3934
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams358d ago0x9956f5…0a372c
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams359d ago0xa3e0e5…7d879c

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.