AgentReport

0xc930…1a11

0xc930e962817d18e4d517900bc3d3c3a7441c1a11Explorer
Paid out
$0.02
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
249
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.02 of the $3067.84M Roundhouse has indexed across 1,401,919 wallets — less than 0.0001% of it.

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

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

$0.02 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.02
    249 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.02$0.00249276d 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 249 observed settlements.

Organic volume $0.02 of $0.02 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams326d ago0x99c814…b530f5
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams326d ago0xe986f9…4b969d
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams326d ago0x208a3b…100d34
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams326d ago0x1a6e56…168991
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams326d ago0xecdee9…3b8c19
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams327d ago0x6a09a4…d77b02
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams327d ago0x6811eb…69d6fd
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams327d ago0xf1a1b4…58d332
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams327d ago0x174ceb…4fc463
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams327d ago0xe02bbd…682c07
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams328d ago0xdd6189…86bf5e
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams328d ago0x4757e2…a8b591
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams328d ago0x45770e…7df237
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams328d ago0x443d63…782b81
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams335d ago0x0956a8…ca7259
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams337d ago0x1fa00e…d635af
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams337d ago0x9f1d12…9231cc
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams337d ago0x4ca84e…9aa9ca
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams337d ago0x4c9951…e3c62e
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams338d ago0x04af4a…b30f4e
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams338d ago0x8716b7…1cfe4d
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams338d ago0xd6b1d5…8f4bd2
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams338d ago0x14915c…8b10d6
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams338d ago0x6b0769…9cb532
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams338d ago0x87b229…4ce55b

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

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

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: 0xc930…1a11

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