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,510 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%daydreams352d ago0xf956b0…70f6a1
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams352d ago0xf6a88b…a533f8
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams352d ago0x9a3691…aacf85
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams352d ago0xa2a4db…a8f39f
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams352d ago0x5cf7f4…27e481
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams353d ago0x61efb1…64c675
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams353d ago0x4c63a0…6564d5
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams353d ago0x846912…ae4773
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams354d ago0x494beb…00ca7a
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams354d ago0x02ea15…97fde9
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams354d ago0x23494d…79049d
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams355d ago0xdaeb03…609ad8
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams355d ago0x912267…a42005
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams355d ago0x9a7f56…0f4862
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams356d ago0xfc2bdb…5b6b39
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams356d ago0xc4c29e…b50460
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams356d ago0xa0b922…f238b6
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams357d ago0xb62371…976a2e
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams357d ago0x5cb62c…43dfd1
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams357d ago0x780f21…806f23
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams357d ago0x903856…b1f01d
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams358d ago0x024ac1…73e2bc
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams358d ago0x4e24b8…d16e40
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams358d ago0x185328…5091d7
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams358d ago0x8ad078…014b8f

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.