AgentReport

0xc327…43ca

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

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

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

$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
    266 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.00266276d 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 266 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams348d ago0x8e1669…768b4f
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams348d ago0x963f0a…38c96e
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams348d ago0x563c47…6a4eab
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams348d ago0x70657a…0c4b6f
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams348d ago0xfccbe1…fc1ece
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams348d ago0xad03f3…539aa6
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams348d ago0x10df48…319fae
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams348d ago0x8bec13…b0e945
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams349d ago0x16c659…5295d1
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams349d ago0x735c23…32445c
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams349d ago0xf7b470…1fc939
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams349d ago0xda7ddb…75a2af
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams350d ago0xccec53…fba138
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams350d ago0xb86d5d…a9e85d
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams350d ago0x9a934e…57d485
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams350d ago0x647782…296c78
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams350d ago0xfd9e3e…295756
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams350d ago0xf3a190…f3cce1
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams351d ago0x4b5823…12e725
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams351d ago0x005da1…ac4888
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams351d ago0x5a12d0…9956ff
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams351d ago0xf1db24…035166
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams351d ago0xd66d63…26bf1a
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams351d ago0xdfe29d…25785a
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams351d ago0x1ec613…ad27cb

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

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

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: 0xc327…43ca

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