AgentReport

0xf60b…190a

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

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,563 wallets — less than 0.0001% of it.

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

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

$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
    254 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.00254277d 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 254 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams343d ago0xb42525…a29a9e
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams343d ago0xa2ac48…7774ec
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams344d ago0xd26e60…49a7fe
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x8662a2…fb64b7
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x4adba3…014a71
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x14f632…29cd7c
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x987e5b…79649f
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x726173…9c0df1
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x8b0624…fb29b8
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x65a954…6fcc9c
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x54d2de…4e6fef
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams344d ago0xe53ed1…15ddfe
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x670e31…75fecd
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x8c7b38…aeed5a
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe56807…22f568
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x7da410…0b0e00
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xea59b8…a96f66
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x799de3…9bb475
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xc8ddca…6b22ec
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x3d8743…5498f7
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xc436a0…8ab673
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xacbf34…feaf7b
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xb4db3b…5069c5
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x970dac…cfa286
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x4b0e6a…d93bd4

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

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

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: 0xf60b…190a

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