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,396 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 276d 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.00254276d 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%daydreams337d ago0xead4f1…7a9433
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams337d ago0x82f6ed…a3178f
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams338d ago0xbf2ef5…689c96
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams338d ago0xfc4fcd…4569bc
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams338d ago0x86f647…737bec
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams338d ago0x5c17db…a25843
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams338d ago0x132915…cda8cc
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams338d ago0x180612…9466fa
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams338d ago0x6327fc…47939e
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams339d ago0x9c2f98…68de20
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams339d ago0x9e7efd…0bb049
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x339570…2e6db5
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x0cb380…1332b2
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xf14e1d…0de3bb
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x0045e3…073f5f
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe65fa5…2d1573
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x0a5269…1e1981
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x1fb71f…64dc9b
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xddf5d4…363a38
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xbbe7eb…5dcd6e
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xb7c1cd…25066f
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xd76b85…cd2f4f
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams341d ago0x4e0941…3d8e8c
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams341d ago0x0dbb8a…45d82c
0xf60b…190a0x6482…b779BaseBase$0.0001100%daydreams341d ago0x7fe50a…bb0539

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.