AgentReport

0x83df…fa06

0x83df8e952e875bde15bf70088c552bb3047efa06Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
251
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

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

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

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

$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
    251 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.00251276d 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 251 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams346d ago0xfdb9d9…9a3d36
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams346d ago0x87b770…14797e
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams346d ago0xe9b37b…1713bd
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams346d ago0x3b694a…01d9fb
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams346d ago0xa4703a…d67035
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams346d ago0xd06a21…10c5a0
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams346d ago0x813b17…f8b087
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams346d ago0x881bd9…23c3cd
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams346d ago0xe9c2a0…0551b5
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams346d ago0x81dcfc…5396a7
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams347d ago0x7e0a26…d0d0f2
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams347d ago0x99a1f9…00473e
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams347d ago0xd4435f…33dab1
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams347d ago0xb855ab…bc0855
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams347d ago0xaade00…1f8e1c
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams347d ago0x52e6e9…0d37b2
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams348d ago0xbc9346…cd1b9e
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams348d ago0x1e20f5…fcf0ec
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams348d ago0xb2bf08…edb10d
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams348d ago0x1b683e…f89556
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams348d ago0x718a9c…cc6e29
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams348d ago0x8a723f…389b48
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams348d ago0x8e8335…b90ecb
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams348d ago0x4a7436…079dae
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams348d ago0x028b33…ab2458

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

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

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: 0x83df…fa06

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