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%daydreams353d ago0xbdf245…f55ff1
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams353d ago0x0b81f9…25f523
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams354d ago0xb382a1…f1152d
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams355d ago0xd29ad6…b93527
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams355d ago0xe38f0b…deb57c
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams356d ago0xdf16a8…44c30c
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams356d ago0x7d65bf…788c2a
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams356d ago0xca4832…f84a8c
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams356d ago0xbb4cc6…326ace
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams357d ago0xce5068…e1d0e0
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams357d ago0xcabdac…675955
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams357d ago0x39fb67…047d4b
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams357d ago0xc0849e…ee964e
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams358d ago0x9f6ad7…17b73f
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams358d ago0xa7dfd9…2edd1c
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams358d ago0xd70c70…8de200
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams359d ago0x536500…0431cc
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams359d ago0xb4e273…c46293
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams359d ago0x712fe4…8d4fbf
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams359d ago0x7263f6…aa8488
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams360d ago0x03beec…320739
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams360d ago0x24e26c…e90cd1
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams360d ago0x3ac87a…025048
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams360d ago0x89d8df…a11cb6
0x166f…fc930x6482…b779BaseBase$0.0001100%daydreams361d ago0x951646…1a237e

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.