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,722 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 277d 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.00265277d 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%daydreams346d ago0x482c00…6aaef2
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams346d ago0x5fb351…9fd65e
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams346d ago0xcb0398…a6ae18
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams346d ago0x0e4d9d…c1f6b9
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams346d ago0x5b9612…c9808c
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams346d ago0xa5fcff…5eca8b
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams347d ago0x999f1c…60f02c
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams347d ago0xb91932…f71260
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams347d ago0x2b1582…1f5fc3
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams347d ago0x30f591…95ce62
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams347d ago0x5b54d0…c6fab3
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams347d ago0x0d1534…5aa280
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams347d ago0x3f986f…048aa5
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams347d ago0xa536e5…cec61a
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams348d ago0x3ada21…a5c335
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams348d ago0x529724…609486
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams348d ago0x5361d8…e4fbfb
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams348d ago0xdb0087…51a76e
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams348d ago0x3172bf…169913
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams348d ago0xcc73ef…b82900
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams348d ago0x84209f…b26b78
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams348d ago0xfd54bb…c58dd7
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams348d ago0xe33883…db7ad5
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams349d ago0x6da154…9e3de8
0xcd65…02270x6482…b779BaseBase$0.0001100%daydreams349d ago0x483aaf…8bf495

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.