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,563 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%daydreams341d ago0x99f0f9…d0c699
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams342d ago0x55adbd…1246e1
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams342d ago0xfe1c56…7ca967
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams342d ago0x7e79d7…aaafe3
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams342d ago0x8f66ea…980644
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams342d ago0x0e8889…2c83d9
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams342d ago0xeab091…7b5ae7
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams342d ago0xf0d980…28a270
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams342d ago0x083f3e…c46ea0
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams342d ago0x4b0adb…4964bc
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams342d ago0x45bd51…ad8bff
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams342d ago0xfd2061…1acc44
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams343d ago0xae837e…1cb12e
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams343d ago0x98a709…6c84e3
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams343d ago0xd0c8bd…451ceb
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams343d ago0xc857f7…ae5b36
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams343d ago0x293a2c…b4a556
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams343d ago0xe06900…cc253f
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams343d ago0xe9d90f…fbd041
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams343d ago0xd3b0c4…3a5ce1
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams343d ago0x98a6e1…04149f
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams343d ago0x2b42f3…e089c3
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams343d ago0x4ea86d…dcdc47
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams344d ago0x958c37…7235a9
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams344d ago0x2344bb…7cb073

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.