AgentReport

0x619f…95fa

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

Paid $0.03 of the $3070.29M Roundhouse has indexed across 1,403,290 wallets — less than 0.0001% of it.

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

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

$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 277d ago
    $0.03
    260 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.00260277d 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 260 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams349d ago0x7f5b81…358ed4
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams349d ago0xc13a4c…1ddbf2
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams349d ago0x17d980…b0c04f
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams349d ago0xe8a62b…334036
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams349d ago0xf59cc9…6fbd31
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams349d ago0xfa8825…3ae1ca
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams350d ago0xad8af1…18d69a
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams350d ago0x3748eb…036f38
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams350d ago0x7b70ea…08c455
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams350d ago0xfce741…f864fe
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams350d ago0xed8dc3…65691a
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams350d ago0x0657aa…3ddf14
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams350d ago0x29298b…dc744b
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams351d ago0xa5c25d…1316d2
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams351d ago0x43b95f…c0a279
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams351d ago0x1b66ef…796eb7
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams351d ago0x6925a7…91c100
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams351d ago0x4d308e…b80346
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams352d ago0xe1ade2…05a3f4
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams352d ago0xd42d6e…061e32
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams352d ago0x147bbc…5aaee0
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams352d ago0x6df54b…573b57
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams352d ago0xfa6698…ec378f
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams352d ago0xf8d997…299ad6
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams352d ago0x06fc16…4dcfd4

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

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

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: 0x619f…95fa

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