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,563 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 277d 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.00262277d 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%daydreams341d ago0xfd8fbd…5b15dd
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams341d ago0xb54875…c8109f
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams341d ago0x4ba42b…e59992
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams341d ago0xb6f25c…6a7c92
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams341d ago0x46dc81…be556a
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams341d ago0xc61b32…ba50c4
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams341d ago0x469a7c…c2af11
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams341d ago0x719a68…b630c9
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams341d ago0xbb4c86…148938
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams342d ago0xb8152a…a544d8
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams342d ago0x31810e…42b13f
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams342d ago0x8a4b19…463e01
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams342d ago0x59ea64…e75b26
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams342d ago0xebf8f2…639375
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams342d ago0x632448…46b088
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams342d ago0xa6422a…fa9273
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams342d ago0xee6aff…2c8082
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams342d ago0xb3f595…c4810d
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams342d ago0x19290f…4826af
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams342d ago0x083c82…6dbaac
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams343d ago0xa64be2…f9c0bc
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams343d ago0x6f5e5d…e19353
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams343d ago0x3430e1…af7515
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams343d ago0x9a96a0…b057a0
0x11b9…80080x6482…b779BaseBase$0.0001100%daydreams343d ago0x8e9fc9…1f1b8c

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.