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%daydreams342d ago0x558a98…ada4a6
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams342d ago0x8f71bc…6ca377
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams342d ago0x745edb…074b58
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams342d ago0x59723c…c11e2e
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams342d ago0x8773d4…cdf4ee
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams342d ago0x314737…5bb44a
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams342d ago0xba939a…34880e
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams342d ago0x6014be…92c8e2
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams342d ago0x5e86f8…f42123
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams343d ago0xe050e3…de2d82
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams343d ago0x18fb2b…60fc4f
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams343d ago0xf76acd…de1113
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams343d ago0x94e97e…19b4e9
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams343d ago0x5c3d7d…8fa47d
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams343d ago0xb5bbc0…034f4d
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams343d ago0x1770c8…507e4d
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams343d ago0xbe2112…71b46c
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams343d ago0x63e3e2…508872
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams343d ago0xc74903…b8fe56
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams344d ago0x477bfc…08a5e6
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams344d ago0xb3eec6…cc9d75
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams344d ago0x505f43…6c593f
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams344d ago0x7e6d5c…14a18b
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams344d ago0xff5aa3…555cbb
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams344d ago0x952abf…c17e72

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.