AgentReport

0xcbc5…2658

0xcbc55100714666997f7fc8ff54e366f977b82658Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
260
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,575 wallets — less than 0.0001% of it.

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

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

$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
    260 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.00260276d 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 260 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams323d ago0xec4fbc…d83dc8
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams323d ago0xc53fb6…adda3e
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams323d ago0xba2154…846445
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams323d ago0xaeda22…e36b37
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams324d ago0x8033c9…47f9b7
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams324d ago0x04fc6c…1bcb9d
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams324d ago0x32961d…f64a2b
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams324d ago0x8e8fa5…9940b0
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams324d ago0x5fe769…d5388c
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams324d ago0x8ab765…9da2a1
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams324d ago0xcebe50…726bd6
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams324d ago0x0e7a16…a42540
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams324d ago0x3f1482…1f298e
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams324d ago0xc6fc33…3f229f
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams324d ago0x04b0aa…9b443c
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams325d ago0xb3a0c6…278fbf
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams325d ago0xd1caef…ad160b
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams325d ago0x8d8dcd…49cd85
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams325d ago0x521788…cd0c4e
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams325d ago0x16bf24…d351dc
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams325d ago0x03b5ba…d2b23c
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams325d ago0xdfd0ff…45c02d
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams325d ago0xe91d94…5dbcaa
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams325d ago0x118666…6746d1
0xcbc5…26580x6482…b779BaseBase$0.0001100%daydreams325d ago0x5b3fa5…e6bee8

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

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

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: 0xcbc5…2658

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