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%daydreams353d ago0x149c7a…4d0494
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams353d ago0x15221f…994e72
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams354d ago0xf0388c…54d49d
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams354d ago0xa74c61…f861ed
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams354d ago0x8fee6f…76ca00
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams354d ago0x987895…143a58
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams355d ago0xd5f56c…c62312
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams355d ago0x6417fa…4d3244
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams355d ago0x26871c…2cd1ae
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams355d ago0x055552…ec5f2f
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams355d ago0xef1a7a…ea4eae
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams356d ago0x62a590…cfef5a
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams356d ago0xc6c7fa…1a3cfe
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams356d ago0xa2f041…72c317
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams356d ago0xd57880…cbcd0d
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams356d ago0x6b6eaa…b457c2
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams356d ago0xb9ed31…02beef
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams357d ago0xfbf549…1222eb
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams357d ago0x7983d6…58ca1e
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams357d ago0xab7317…547720
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams357d ago0xca0558…2f1cef
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams357d ago0xc7f254…aaf72f
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams358d ago0xa3f9a7…28b10a
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams358d ago0x98817a…ed92f5
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams358d ago0x308f9b…e02da7

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.