AgentReport

0x95a5…6ba2

0x95a5e363edba61f5fec817bec0897bd366d66ba2Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
258
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,402,228 wallets — less than 0.0001% of it.

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

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

$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
    258 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.00258276d 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 258 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams349d ago0x15903f…4fc7af
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams349d ago0x8b040c…0393ed
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams350d ago0x174a87…66b306
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams350d ago0x6dca8b…d4a4a0
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams350d ago0x57fd00…d57e2a
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams351d ago0x5d50d9…67a98f
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams351d ago0x8f0eb0…457d16
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams351d ago0x482f95…c4f898
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams351d ago0x7f943f…7814e8
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams351d ago0x02d8c5…888757
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams351d ago0x4aab41…3611d2
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams351d ago0x54c558…0b2389
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams352d ago0x269d78…3b6f75
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams352d ago0xc8cb27…d768d5
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams352d ago0xd660c2…92f291
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams352d ago0xdc4c1b…292b65
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams352d ago0xf246d7…d1eaff
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams352d ago0xe59b86…8a51c0
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams352d ago0x34765d…d4cfe1
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams352d ago0xed5c30…d95e4f
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams353d ago0x40cfce…d6f04d
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams353d ago0xd60eda…fd227a
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams353d ago0x623acb…b54ee0
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams353d ago0x9b5888…91fc7b
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams353d ago0x4504b2…7ddce9

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

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

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: 0x95a5…6ba2

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