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,255 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%daydreams341d ago0x767679…faa7b8
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams342d ago0xa217f8…143fa1
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams342d ago0xa9b281…77ca55
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams342d ago0x98979e…d30004
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams342d ago0x08c951…74ca62
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams342d ago0x05270e…2dc0e0
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams342d ago0xada452…d486f4
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams342d ago0x64703d…aaa83d
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams342d ago0xc3dacc…e6f1cf
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams342d ago0xbe0494…695707
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams343d ago0x86c1ef…18db60
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams343d ago0x8f0d95…bfe6e9
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams343d ago0x23403f…3f8e64
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams343d ago0x03f951…711a96
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams343d ago0xd4ef15…d2f29a
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams343d ago0x454223…bfe234
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams343d ago0x6ea7f4…771d89
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams343d ago0x157094…4597bd
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams343d ago0x42c1f4…6a0f26
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams343d ago0xa80e8b…4be386
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams343d ago0xa5eb30…7e9a30
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams344d ago0xf567d3…68173b
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams344d ago0x428298…658bc2
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams344d ago0x1f5341…a2c8f5
0x8167…f8cb0x6482…b779BaseBase$0.0001100%daydreams344d ago0x67d875…206237

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.