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 $3068.58M Roundhouse has indexed across 1,402,396 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%daydreams338d ago0xb95704…94da42
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams338d ago0x62df76…740162
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams338d ago0x8e0a2c…61d07a
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams338d ago0x5afada…b196a6
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams338d ago0x368e04…f1f06b
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams338d ago0x5d606f…b79e67
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams339d ago0xa2ce6c…f5c29c
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams340d ago0x260c86…edb9b2
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams340d ago0xad107b…6a27c2
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams340d ago0xc85383…a2caa3
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams340d ago0x499eb0…14f8de
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams340d ago0x2843f8…326322
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams340d ago0x42f1c2…0d0fac
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams340d ago0xf7b9cc…622c92
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams340d ago0x7b2ecc…74502b
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams340d ago0xcbe803…2b62c8
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams340d ago0x782277…29b6e3
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams340d ago0x075761…8f7dc3
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams341d ago0x7a1263…da085e
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams341d ago0x486a5b…89032c
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams341d ago0x25e758…a812aa
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams341d ago0x21ca1e…06a2a4
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams341d ago0x7f4470…4bfe9e
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams341d ago0x6c0bcf…f87cae
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams341d ago0xe8d755…c33363

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.