AgentReport

0xcecd…e74a

0xcecde6bbbca9e3c229e91f367f303da5e5d2e74aExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
261
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,843 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (261)

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.032611

$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
    261 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.00261276d 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 261 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams348d ago0xb3e556…de1dea
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams348d ago0xcaada0…d7b957
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams349d ago0xe1c53d…bf18d7
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams349d ago0x8c4ca5…fee5e1
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams349d ago0x842e80…186a7a
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams349d ago0xa3c2dd…55830f
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams349d ago0xa67eeb…1d983d
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams349d ago0x51b3e8…04c971
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams350d ago0xdd8159…ed68b7
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams350d ago0xa8a529…f44c21
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams350d ago0xd34dd5…b6a52d
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams350d ago0xd93bef…1f6dff
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams351d ago0x46001d…8be346
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams351d ago0x281cfe…cc9267
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams351d ago0x595edb…a62d9d
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams351d ago0x60b46e…3c3714
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams351d ago0xdb76a3…78f66c
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams351d ago0x23feb0…2ce362
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams351d ago0xd0e17e…f175f4
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams351d ago0x880742…0353c6
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams352d ago0x37074d…b77b3b
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams352d ago0xe173fb…2aa5bb
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams352d ago0x3625dc…c9f614
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams352d ago0x3e7fc5…25a89b
0xcecd…e74a0x6482…b779BaseBase$0.0001100%daydreams352d ago0xe97ee1…56ace4

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 0xcecd…e74a has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0xcecde6bbbca9e3c229e91f367f303da5e5d2e74a

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: 0xcecd…e74a

curl -s 'https://api.roundhouseai.io/v0/agents/0xcecde6bbbca9e3c229e91f367f303da5e5d2e74a'
curl -s 'https://api.roundhouseai.io/v0/entities/0xcecde6bbbca9e3c229e91f367f303da5e5d2e74a/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.