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%daydreams352d ago0xf11abc…65bfd3
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams352d ago0xd609b3…e51990
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams352d ago0x0b8874…16fe2b
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams352d ago0xc74d08…6b7630
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams352d ago0x34d97d…719b29
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams352d ago0x4f22ed…3d89e4
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams353d ago0x284ce3…e87690
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams353d ago0x47a52d…75ea43
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams353d ago0x530c02…d61140
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams353d ago0x74c558…9b7530
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams353d ago0xd0cb82…9d1768
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams353d ago0x88bfa4…78ba7d
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams353d ago0x81fd38…75771b
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams353d ago0x4f0f14…b3f045
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams354d ago0x5fc589…eef98d
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams355d ago0xa4aa9e…4f7f78
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams355d ago0xaa1d70…77b552
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams355d ago0x75dcc8…cf71e8
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams355d ago0xed76f3…737513
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams355d ago0xf9b047…4ad87e
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams356d ago0x1313c9…5f8661
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams356d ago0x14d292…cf57d3
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams356d ago0xbe083d…601bf2
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams356d ago0x3eada7…bd8a0c
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams356d ago0xebab04…72b2f9

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.