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 $3068.58M Roundhouse has indexed across 1,402,563 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 276d 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.00273276d 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%daydreams341d ago0x084cc2…d16e88
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams341d ago0x83fa9a…29eb8f
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams341d ago0x0645a7…3edfc4
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams341d ago0x2dec2d…641d1c
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams341d ago0x511243…c9c3f4
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams341d ago0xc8840e…06aba2
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams341d ago0x17270f…468bc1
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams342d ago0x49a4d5…449591
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams342d ago0x88e6f9…bf0e12
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams342d ago0xd536f3…222a01
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams342d ago0xf4d2bd…bbd909
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams342d ago0x783c92…16fc6a
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams342d ago0xbcdd4c…af714d
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams342d ago0x4a98a5…85303a
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams342d ago0xac6843…5db3cc
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams342d ago0x156265…26ca95
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams342d ago0x7aecb1…cd9841
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams342d ago0x91d5c7…785458
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams343d ago0x34fb85…65b9c9
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams343d ago0x45f9be…a1127d
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams343d ago0xedd2fb…ac9ae8
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams343d ago0xb9f00d…bb3ea2
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams343d ago0xf59aa9…ced947
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams343d ago0xa288ba…44133f
0x0c3f…4a140x6482…b779BaseBase$0.0001100%daydreams343d ago0x3f7cf8…ce4457

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.