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 $3068.58M Roundhouse has indexed across 1,402,563 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%daydreams349d ago0xb47016…8e89cc
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams349d ago0xd4ecf0…18d1c6
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams349d ago0x2bf3fd…e898d6
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams350d ago0x9451f1…5a76b8
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams350d ago0x6c9142…e96592
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams350d ago0xeffb58…b1b7eb
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams351d ago0x432f64…b2bce7
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams351d ago0x90db9d…fb935e
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams351d ago0xedded9…037732
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams351d ago0xf95991…149a71
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams351d ago0xfa7d85…f1e616
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams352d ago0xc83152…97f909
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams352d ago0x644b84…af8dd4
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams352d ago0x184b49…87513e
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams352d ago0x4667ca…dd62b3
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams352d ago0x8b0ac4…9db5e2
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams352d ago0x5e4613…021a81
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams352d ago0x7166f2…9a6232
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams352d ago0xbe4e9f…d0ff8b
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams353d ago0xc471bb…3d129f
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams353d ago0x889897…fa8577
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams353d ago0x7902a1…c1d28a
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams353d ago0x22fbba…503654
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams353d ago0xa8d409…5a5afb
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams353d ago0xb1f6c6…ab5dca

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.