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%daydreams353d ago0xc59dbc…a64472
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams353d ago0x7ddd23…417867
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams355d ago0x726366…da401e
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams355d ago0x3cf198…e3966b
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams355d ago0x884e22…0d9ad5
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams355d ago0xbe8269…6b9a01
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams355d ago0x98d02b…003d7c
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams356d ago0x77f2cf…2be17c
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams356d ago0x33b2fb…d21771
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams356d ago0x9e2a88…1ac0ab
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams356d ago0x4c7525…30136e
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams356d ago0x9f9cfe…70dedd
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams356d ago0xd2664a…6135ac
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams357d ago0xdc2f36…4ba6b6
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams357d ago0xe29f0e…2f6010
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams357d ago0x579b0d…b1ce40
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams357d ago0xefb157…47b88a
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams357d ago0x3d0248…f63b72
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams358d ago0xb8cdab…1acf21
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams358d ago0x85dbf1…10aa65
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams358d ago0x024fd2…256f80
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams358d ago0xc53b8f…21d716
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams359d ago0xbb561d…ff6e5b
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams359d ago0x62ec7f…1eac0f
0x95a5…6ba20x6482…b779BaseBase$0.0001100%daydreams359d ago0xa521bf…b3a8d9

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.