AgentReport

0x166f…fc93

0x166f23a945ad6788777b3bcf39801e74b5b2fc93Explorer
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 $3104.66M Roundhouse has indexed across 1,404,591 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
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams349d ago0xc5bf89…7667d1
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams349d ago0x7d47a6…66d184
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams350d ago0x7effce…d80558
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams350d ago0x6caeaf…cd98e9
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams350d ago0x0779e9…6552e9
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams351d ago0x8a51a5…5c6963
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams351d ago0x407df1…8f1bd6
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams351d ago0x6fa91c…7a1405
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams351d ago0x0559d7…f18c88
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams351d ago0x2dbeb6…226b03
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams351d ago0x81a7a4…f6a577
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams352d ago0xc00097…f4ea64
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams352d ago0xc32629…93c37a
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams352d ago0x58109e…8acaae
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams352d ago0x40d96f…13f5b0
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams352d ago0x82f767…3f458a
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams352d ago0xbcb6aa…6efc66
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams353d ago0xc416ce…44e17d
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams353d ago0x44ff02…cdc199
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams353d ago0x6ae343…cdc338
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams353d ago0xb05221…ad16ed
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams353d ago0x6b7832…610fff
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams353d ago0xcbb163…c64b59
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams353d ago0x21185e…e0df46
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams353d ago0x546ba0…4ff2d8

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

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

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: 0x166f…fc93

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