AgentReport

0x11b9…8008

0x11b924d313c0237a626eb796874b0385c8878008Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
262
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

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

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

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

$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
    262 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.00262276d 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 262 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams323d ago0x5060d9…05a65e
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams323d ago0x40f2d0…cd8edb
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams323d ago0x867af5…a899c6
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams323d ago0xfb5128…ed7472
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams323d ago0xc8552b…e30a3b
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams324d ago0xb0c333…8cb02f
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams324d ago0xd3592a…bf4f32
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams324d ago0x18a523…7c5225
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams324d ago0xbd4ad9…9be14d
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams324d ago0xedacb0…59f863
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams324d ago0xc20ef9…9b2416
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams324d ago0xa9b1d8…de43c1
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams324d ago0xace470…db111b
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams324d ago0x429332…60acb9
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams324d ago0x1601ab…c16832
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams324d ago0x99b84e…748c1a
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams325d ago0xf746ce…caee46
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams325d ago0xa322f3…5e1c0c
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams325d ago0xffc98f…dd7f4a
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams325d ago0xc150a6…b3b2b5
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams325d ago0xb70f68…525643
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams325d ago0x080229…e5bff1
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams325d ago0x01737b…bf052f
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams325d ago0xedd466…cb1537
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams325d ago0x21213e…650ecc

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

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

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: 0x11b9…8008

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