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%daydreams338d ago0x649da4…c69d93
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams338d ago0x55f4e6…5d3962
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams339d ago0xf1267f…f4919d
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams339d ago0x5882f8…6ffbfb
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams339d ago0x0e4d8c…fe607c
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams339d ago0xc39e23…539bb1
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams339d ago0x77d234…31e12b
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams339d ago0xa0fa60…3bf9ed
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams339d ago0xf6d8f3…751c99
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams340d ago0x9fbaec…e6ca08
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams340d ago0xc69b45…53931c
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams340d ago0x0a1297…c4dd3a
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams340d ago0x8ed49b…7445c5
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams340d ago0xdc1d73…b111d2
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams340d ago0xb7076c…55e102
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams340d ago0xbb4869…34620d
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams340d ago0x24eada…75696c
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams340d ago0x325230…ad8f1a
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams340d ago0x5c6df5…87c465
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams340d ago0x521d7d…25544c
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams341d ago0xba3782…239515
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams341d ago0xea904d…158d77
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams341d ago0xed30ad…b40ff3
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams341d ago0xf7d3b1…c85e81
0x80fd…24740x6482…b779BaseBase$0.0001100%daydreams341d ago0x2e846f…7e5650

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.