AgentReport

0x80e5…f376

0x80e50ad5721ce6a4bebbdf081cba7dc49bd0f376Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
271
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.84M Roundhouse has indexed across 1,401,919 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (271)

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.032711

$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
    271 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.00271276d 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 271 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams352d ago0x03b9dd…ffd45d
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams352d ago0x3c5278…c8792a
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams352d ago0xebd3df…711b97
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams352d ago0x53e0c2…1cc86c
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams352d ago0x31fcec…bdca8b
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams353d ago0x3fcefe…1b2d5d
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams353d ago0x5101a5…6b4f48
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams353d ago0xd71d1a…9281fc
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams353d ago0xfe2643…c32179
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams353d ago0x8ad993…826c12
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams353d ago0xcf4e40…76f97d
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams353d ago0x9e0c76…46fe02
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams353d ago0x649ade…ccd85b
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams354d ago0x8feb8e…504b78
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams354d ago0x4caa94…0f606e
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams355d ago0x80247c…9bee8d
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams355d ago0x222be0…e01e80
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams355d ago0x0eba1c…56e95a
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams356d ago0x5e715e…42b1c9
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams356d ago0x3e7aaa…ef1422
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams356d ago0xf57720…f2ec1e
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams356d ago0x0ebe24…473558
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams357d ago0xaf779e…e94be8
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams357d ago0x64c5e4…4078dc
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams357d ago0x788cdc…f60edf

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 0x80e5…f376 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x80e50ad5721ce6a4bebbdf081cba7dc49bd0f376

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: 0x80e5…f376

curl -s 'https://api.roundhouseai.io/v0/agents/0x80e50ad5721ce6a4bebbdf081cba7dc49bd0f376'
curl -s 'https://api.roundhouseai.io/v0/entities/0x80e50ad5721ce6a4bebbdf081cba7dc49bd0f376/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.