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 $3067.84M Roundhouse has indexed across 1,402,228 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 276d 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.00260276d 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%daydreams326d ago0xd6bee1…4db0d8
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams326d ago0x13c196…14d50f
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams326d ago0xefab0e…6e83fd
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams326d ago0x97f538…5eebc0
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams326d ago0x4914e0…526f69
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams326d ago0x1dfd77…4de1a3
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams326d ago0x4120e0…e9b151
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams326d ago0x4a6222…fd9ed4
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams326d ago0x8fba97…3d4080
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams327d ago0x1257d0…3fde79
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams327d ago0xd67e2b…6bd8e1
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams327d ago0x41f2a6…131f5a
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams327d ago0xc812a1…58d41f
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams327d ago0x9199cf…bc646e
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams327d ago0x8e7db6…ba460e
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams327d ago0x8493f7…cfb936
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams327d ago0xb77658…13b519
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams328d ago0xc25a9c…f805c2
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams328d ago0xfc9b0c…35f9f6
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams336d ago0x86fa42…a20e22
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams337d ago0x73560a…4c1cd7
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams337d ago0xf8a60f…86e713
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams337d ago0xea4426…4e11df
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams338d ago0xa676b8…aa5758
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams338d ago0x7dd89b…ddd7a9

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.