AgentReport

0x80fd…2474

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

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,255 wallets — less than 0.0001% of it.

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

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

$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
    263 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.00263276d 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 263 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams348d ago0x0e7502…d42891
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams348d ago0x371544…fb80d2
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams349d ago0xc31259…2873a7
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams349d ago0xf7d199…c8dfac
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams349d ago0xbf5938…e3ca0a
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams349d ago0xbbef43…8565ef
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams350d ago0x26b6a1…306c4b
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams350d ago0xeb29a7…3a7d56
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams350d ago0xb4d877…5943f5
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams350d ago0x2b749e…91959b
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams350d ago0x435926…6a32dc
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams350d ago0x37aff4…982885
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams351d ago0xfcba2e…66e7a6
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams351d ago0x700604…ac8749
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams351d ago0xba76e8…575a06
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams351d ago0xb2a1cc…2f5332
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams351d ago0x83eac5…6408ee
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams351d ago0x7990d6…f538b6
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams351d ago0x3eca77…efc879
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams351d ago0xeabebd…3d355f
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams352d ago0x7ddbeb…339fb0
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams352d ago0x6f8056…0b70a4
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams352d ago0x1b0e26…95247d
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams352d ago0x1f96ff…0cee34
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams352d ago0x289c29…14b306

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

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

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: 0x80fd…2474

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