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%daydreams345d ago0xd65089…ed48fb
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams345d ago0x880957…27b2f6
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams346d ago0x2552ae…a53910
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams346d ago0xdc9d94…c2c903
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams346d ago0xe8c4db…c8d04b
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams346d ago0x5dbbc8…5ea0e0
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams346d ago0x090f65…78381a
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams346d ago0x903fe5…4a296f
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams346d ago0x6d8d98…78f198
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams346d ago0x030dd7…8122c5
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams346d ago0x363498…ea74eb
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams346d ago0xf4e4c5…a812cb
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams346d ago0x92fcb3…619dc7
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams347d ago0xedd346…8f592a
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams347d ago0xf089c4…c8c264
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams347d ago0xe7da0d…0eecb9
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams347d ago0x25df25…8b90d4
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams347d ago0xb235df…7935ef
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams348d ago0x02ede7…50f4af
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams348d ago0x93a389…86d04e
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams348d ago0x69cf6f…72b66b
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams348d ago0xe032f0…fd0760
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams348d ago0x6741d5…ed0632
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams348d ago0xeeca32…56f7f1
0x80e5…f3760x6482…b779BaseBase$0.0001100%daydreams348d ago0x6b7a23…0f9e28

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.