AgentReport

0xf10f…72f7

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

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

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

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

$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
    259 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.00259277d 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 259 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams348d ago0xdee01b…cf04f8
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams348d ago0x33ca61…03b6e3
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams348d ago0xc2b08e…7abcc8
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams349d ago0x7f264d…ef12a6
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams349d ago0xcb1b20…c238fd
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams349d ago0x9976be…e87ec8
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams349d ago0x67a23e…2ce5aa
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams349d ago0xa75ea4…273a30
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams349d ago0xd9cb34…ce10c6
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams349d ago0x1ccc62…c6003a
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams349d ago0x30291f…01ce29
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams350d ago0x44e1c7…2053d1
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams350d ago0x8125a9…ce9bdd
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams350d ago0x8b41e9…bb2d3b
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams350d ago0xda9f1a…845168
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams350d ago0x50841a…a4addb
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams351d ago0x99dc32…acee51
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams351d ago0xa7e9e1…f1fa92
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams351d ago0xb3b2b1…be3e84
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams351d ago0x5cebd4…b6df0f
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams351d ago0x6d080b…e87042
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams352d ago0x6b0a8f…e513d6
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams352d ago0x66a888…c25024
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams352d ago0xd3db7d…38c041
0xf10f…72f70x6482…b779BaseBase$0.0001100%daydreams352d ago0x7196bc…7b7a37

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

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

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: 0xf10f…72f7

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