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.17M Roundhouse has indexed across 1,400,092 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%daydreams325d ago0x57e0af…3acff5
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams325d ago0xc2c382…74dd6d
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams325d ago0x0a8942…cec7fd
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams326d ago0xcc760d…32ab69
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams326d ago0xadc18f…168f24
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams326d ago0xf56ace…16ea45
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams326d ago0xa82d32…033f1f
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams326d ago0xe04515…6d880b
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams326d ago0xaaf482…9c4b83
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams326d ago0x0c3fa3…ab1c69
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams326d ago0xccd488…5296b1
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams326d ago0xe382a8…7a1181
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams327d ago0x9c6ff5…14e031
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams327d ago0x73f945…6d665a
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams327d ago0x1a09bc…148437
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams327d ago0xa4d9a8…3adb87
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams327d ago0xe973f1…ffc78a
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams327d ago0xe355f9…d7870a
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams327d ago0x56ccef…37822e
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams327d ago0x502b53…df89a9
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams327d ago0xa2d189…cdf369
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams335d ago0x8e7ef9…e4d472
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams337d ago0x55c8c7…241c8d
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams337d ago0xa95313…2bca5d
0xc327…43ca0x6482…b779BaseBase$0.0001100%daydreams337d ago0xeeedb6…231d8b

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.