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 $3068.58M Roundhouse has indexed across 1,402,396 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%daydreams336d ago0x4ad461…718648
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams337d ago0x6494fd…7a2728
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams337d ago0x4e1c11…e689b3
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams337d ago0x3942e0…1081f9
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams338d ago0x6648a5…74bdd8
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams338d ago0x5af8f8…017909
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams338d ago0x29f844…4d098a
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams338d ago0xdb5855…695bc4
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams338d ago0xd3a658…9f6f06
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams338d ago0xfc4e5c…f84a2f
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams338d ago0xf48d41…6a6a4b
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams339d ago0x2757e0…2397bd
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams340d ago0xbec76b…ab7012
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams340d ago0x1acda2…7c41dd
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams340d ago0x9a2dbc…d0161a
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams340d ago0xc8596e…be530e
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams340d ago0xd15bb4…6eb5f1
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams340d ago0xb55c89…cc6c18
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams340d ago0x898d1a…f12b18
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams340d ago0x3f76f0…fb6517
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams340d ago0xa9abcc…886d54
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams340d ago0xb94046…8b5387
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams340d ago0xfd156c…ee55d0
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams341d ago0x4ff26d…195eee
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams341d ago0xa67617…e56081

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.