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%daydreams346d ago0xc389de…35ebe1
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams346d ago0x5cd04c…9f6838
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams346d ago0x499944…0075d6
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams347d ago0x66f51d…9db8ff
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams347d ago0x59464c…e7f7c4
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams347d ago0xd07fdc…f6ada5
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams347d ago0x765899…bc1470
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams347d ago0x3bd115…4b2df2
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams347d ago0x7624d7…eed12d
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams347d ago0x2ed28d…494fe9
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0x574895…768935
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0x82113d…8b5579
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0x5d4738…cf7756
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0x93b439…3d4456
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0x52ba16…b4e8a4
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0xec10e2…0dc15d
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0xb97a4e…63a7f1
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0xa68410…223f51
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0x254ecc…8844cc
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0xff5f01…c5921e
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0xc41719…9cf3fd
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams348d ago0x0d9532…01c831
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams349d ago0x99b044…ecb989
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams349d ago0xcd2086…39813b
0xc930…1a110x6482…b779BaseBase$0.0001100%daydreams349d ago0x248fdc…e5ca62

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.