AgentReport

0x0c3f…4a14

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

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

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

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

$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 277d ago
    $0.03
    273 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.00273277d 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 273 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams348d ago0x7989bc…b3ae4c
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams348d ago0xd358a8…49e934
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams348d ago0x0236c5…4202ec
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams349d ago0x6bff61…939a0f
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams349d ago0x05b72e…3f5d5a
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams349d ago0x0fda9b…adaf36
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams349d ago0xbc3656…ba2c96
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams349d ago0xbc2bfb…668d3f
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams349d ago0x471789…81b62d
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams350d ago0x28a37b…422cab
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams350d ago0xb15e92…8c4d4d
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams350d ago0xe0b2b9…7648ba
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams350d ago0xa6a74d…5c9e40
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams350d ago0xddccc6…274191
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams351d ago0x5189e5…1d653c
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams351d ago0x3b6bb6…eebd39
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams351d ago0x6bc04d…9e489e
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams351d ago0x9e587b…cc9eca
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams351d ago0x17b1de…cbea2b
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams351d ago0x09027f…50c7b1
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams351d ago0x615097…e64d6f
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams351d ago0x7a5ff6…c27c45
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams351d ago0xb3b343…f7c961
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams352d ago0x3d3381…193350
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams352d ago0xc0672e…319955

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

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

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: 0x0c3f…4a14

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