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%daydreams343d ago0xc609be…2044c0
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams343d ago0xc33e31…ce9a66
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams344d ago0x7d8cae…2e4e5d
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams344d ago0x510b33…852784
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams344d ago0x44ecad…83d383
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams344d ago0x0360f3…8e3b41
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams344d ago0x40f5bc…dceb1d
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams344d ago0xa6bd47…89a447
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams344d ago0xae0355…18a4b0
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams344d ago0xe2891a…5fc0da
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams344d ago0x668553…b32f0b
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams344d ago0x388643…7418c6
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams344d ago0x974cc2…7d9ae5
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0x4f0f3d…4a478f
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0xbae9b3…03fa9f
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0xad12a6…e5b15e
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0xf5444b…21e500
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0x3b835e…2e08c2
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0x4e2e31…228fff
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0x874ef5…0579f9
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0x1d1695…19c3b4
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0x30e582…1adb64
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0x8dbb55…9e9d93
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0x50b00f…a87ff0
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams345d ago0x240a97…3071c3

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.