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.17M Roundhouse has indexed across 1,400,092 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%daydreams326d ago0xe2981f…d2979c
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams326d ago0x4e4cf3…cdf527
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams326d ago0x92cc09…1005c5
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams326d ago0x8115e6…dde4fc
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams326d ago0x258c27…1ee58a
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams326d ago0x0570ca…659797
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams326d ago0x3f3e5e…90898f
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams326d ago0x98c2b5…068bf7
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams327d ago0x4315d8…c5193c
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams327d ago0xdb4a6c…5dd596
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams327d ago0xff2b52…903bad
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams327d ago0x092284…323b18
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams327d ago0xed7616…b3a361
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams327d ago0x005b03…17ca89
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams327d ago0xf85c53…9a0556
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams327d ago0xedcda5…92d8cc
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams335d ago0x02d982…f095f4
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams337d ago0xd7c1d1…93e088
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams337d ago0xdc6694…98a1f4
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams337d ago0x8eb7d1…ee166e
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams337d ago0xe7543d…01b8ca
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams337d ago0xf64121…966c7d
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams337d ago0x3c1e14…e6b7ee
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams337d ago0xcdd2c2…85a18a
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams337d ago0xebbfc1…33e1ee

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.