AgentReport

0xc3c3…2d5f

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

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

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

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

$0.02 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.02
    250 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.02$0.00250276d 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 250 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x7c8602…26f460
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x098315…ef3ee5
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x0c47a5…caff71
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x76915f…ad8f78
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x451b95…19d317
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x76a936…e6a0d2
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x9831d8…b0493d
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams326d ago0xa11ce0…016844
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x26a56f…959875
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams327d ago0xa7e7df…c0120a
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x0b9ea9…a0a580
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams327d ago0xf92c3e…e2d352
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x6bd8e4…e48339
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x119632…233e28
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams327d ago0xd29a3e…9fd86d
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams328d ago0x2888f2…a36eb6
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams335d ago0x8d53b7…4202dc
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xfe450f…2a9437
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xa71971…4d3073
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x0ec696…cd5e29
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x784a3c…d68739
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x370309…bb57c4
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xf6e35d…eac16c
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x188b78…ee00cf
0xc3c3…2d5f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x4819a7…58b213

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

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

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: 0xc3c3…2d5f

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