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%daydreams341d ago0x56756d…487ee2
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams341d ago0xbe4826…9602b7
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams341d ago0x34ff59…7597d1
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams341d ago0x3ba634…d0e21a
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams341d ago0x95ed7e…aed936
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams342d ago0x7f461e…cf8a76
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams342d ago0x29918e…1a5011
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams342d ago0xc51802…f8b6d7
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams342d ago0x60e29b…f7c2b0
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams342d ago0x2eef1a…701c94
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams342d ago0xba3d55…b3b56b
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams342d ago0xe056c7…1f073c
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams342d ago0x65417f…bb51d7
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams342d ago0x8f02db…39e706
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams342d ago0x3df454…4e9b42
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams343d ago0x4a940b…481f71
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams343d ago0xce6787…7eeb01
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams343d ago0xa0a30a…9cf417
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams343d ago0x34e36b…896c63
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams343d ago0x102d77…722c58
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams343d ago0x25b430…34d34e
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams343d ago0x69a94f…3fc463
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams343d ago0x606950…ea263f
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams343d ago0x1058ad…1482a5
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams343d ago0xad07cf…5b16dc

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.