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.17M Roundhouse has indexed across 1,400,092 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%daydreams326d ago0x499577…415d90
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams326d ago0x3ce9b8…ae24d6
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams326d ago0xe6094d…240e2c
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams326d ago0xdce4f7…4922d6
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams326d ago0xf01abc…29aca8
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams326d ago0xb51620…19b66c
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams326d ago0x538fad…997389
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams326d ago0x1257f7…ba9866
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams327d ago0xaef0d6…902bb0
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams327d ago0x437e08…d85e5b
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams327d ago0x8ca56d…ecfe93
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams327d ago0x5d563b…894160
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams327d ago0x5862f1…1a97a4
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams327d ago0xb929aa…8472a9
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams327d ago0xb6ff43…a2fb0d
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams328d ago0x4b2bf2…e413a1
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams328d ago0x322e3d…90338f
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams335d ago0x973561…99d0ce
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams335d ago0x5b2048…27c76e
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams337d ago0x9db559…acfdc2
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams337d ago0x2321dc…0bee58
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams337d ago0x37f64c…b5ae4e
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams337d ago0x0570b7…1bd61d
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams337d ago0x6a79ab…28f961
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams337d ago0x8e3161…3f9250

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.