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%daydreams352d ago0x94bf5a…85cd7d
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams353d ago0xbe221e…4e1f62
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams353d ago0x79852a…b31e9e
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams353d ago0xa0257e…281098
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams353d ago0xede403…b03dc2
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams353d ago0x8e2dd8…ed2104
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams353d ago0xe46930…d379fe
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams353d ago0x8d76e0…2ba207
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams353d ago0xc50f4e…16b999
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams355d ago0x541237…877f93
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams355d ago0xfa321b…c01183
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams355d ago0xd95e50…3efbad
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams355d ago0x2489e1…14e943
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams356d ago0x95545a…6ba19d
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams356d ago0x7dffb7…4e314f
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams356d ago0xd650f5…a86a08
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams356d ago0xb18588…66de3a
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams357d ago0x9bcd9e…9269f1
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams357d ago0xa0aaf5…a04827
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams357d ago0x3c3684…0a7bbb
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams358d ago0x38e3ab…79c6c7
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams358d ago0x8de0fc…b36e60
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams358d ago0x87774b…0afa66
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams358d ago0x8b6690…c6af0a
0x619f…95fa0x6482…b779BaseBase$0.0001100%daydreams359d ago0x864d0b…b48670

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.