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%daydreams349d ago0xdaea8a…15dbc0
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams349d ago0x685cc4…65a1d7
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams349d ago0xf3e96f…daa60b
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams349d ago0xc52ee0…856174
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams350d ago0x27c47c…15c438
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams350d ago0x207c49…af1c29
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams350d ago0xb9147a…3cc80d
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams350d ago0xd32292…3e8350
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams350d ago0x56ba33…a68386
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams351d ago0xe0dbd5…b5cfb8
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams351d ago0xe078a7…dee435
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams351d ago0x1fe791…b1977e
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams351d ago0x564cb8…696948
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams351d ago0xe65f53…42285f
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams351d ago0x12f8e9…48e8bb
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams352d ago0x3b3170…eea5c9
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams352d ago0x9c1d21…939f9f
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams352d ago0xd1dbb9…0b8442
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams352d ago0x4e43e2…63486e
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams352d ago0x92120b…379019
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams352d ago0x8d7d6d…4fd499
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams352d ago0x65f7d4…d19627
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams352d ago0x729e35…b9cd9c
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams352d ago0x5c419e…cb5240
0x83df…fa060x6482…b779BaseBase$0.0001100%daydreams353d ago0x6a3542…7ac461

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.