AgentReport

0x8167…f8cb

0x81670fe432910ed9dc7b1ce49591dfbd9308f8cbExplorer
Paid out
$0.02
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
248
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.02 of the $3066.54M Roundhouse has indexed across 1,400,510 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (248)

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.022481

$0.02 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.02
    248 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.02$0.00248276d 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 248 observed settlements.

Organic volume $0.02 of $0.02 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams346d ago0x9c96da…a68050
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams346d ago0x03723a…e4a81f
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams346d ago0xcc9722…3be0b0
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams346d ago0x0457fd…a3c21e
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams347d ago0x68d2e0…59ddb6
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams347d ago0xeeb6fa…b5942d
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams347d ago0xb6f844…82b12d
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams347d ago0x08d859…07310b
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams347d ago0xce89aa…bf8439
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams348d ago0xd04563…f9286a
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams348d ago0xabf95c…e2da3c
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams348d ago0x757131…e87249
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams348d ago0x43b269…820a7d
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams348d ago0x9ced9a…50d39c
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams348d ago0xecec7d…e78da4
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams348d ago0x97982a…f6bf01
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams348d ago0x932a83…8dc649
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams348d ago0x9c136c…faf249
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams348d ago0xa0e20d…c6e520
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams348d ago0xc86db5…08c382
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams349d ago0x45b8e9…e87780
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams349d ago0xdc3ac0…2f8e89
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams349d ago0x44fdf8…8e86b2
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams349d ago0xe2b45d…f4d93e
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams349d ago0xba3690…ba97f4

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

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

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: 0x8167…f8cb

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