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%daydreams343d ago0x459979…3df748
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams343d ago0x278e35…8a8f19
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams344d ago0xb5d1c1…bca0f1
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams344d ago0xd00880…4535f3
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams344d ago0xcdbdaf…120bb1
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams344d ago0xbda377…aafc36
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams344d ago0xdb12ce…6ffa1f
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams344d ago0xc37045…7db898
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams344d ago0x5be7c6…57788d
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams344d ago0xf26f00…37fe52
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams344d ago0xac0100…59ec75
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams344d ago0x14e5ae…d2e312
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams344d ago0xddab86…68c47e
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0x475078…9519fb
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0x06f858…a9f896
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0x00c5ca…9a4047
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0x0138e0…df4de7
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0xcd2a9c…1cb872
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0x3d9770…8c69af
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0xec31e3…e2d80c
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0xd9b5e4…cfccdd
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0x651d51…061f30
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0xde74d6…445fbd
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0x7193da…0f7b12
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams345d ago0xfe69f2…d4a5e8

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.