AgentReport

0x40fa…7186

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

Paid $0.03 of the $3067.25M Roundhouse has indexed across 1,401,192 wallets — less than 0.0001% of it.

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

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

$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
    256 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.00256276d 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 256 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams344d ago0x6b9ba9…7f388b
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams344d ago0x3001dd…24addd
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams344d ago0xb197bb…596841
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams344d ago0xf7d9b4…4626bc
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams344d ago0x661cc8…ed021b
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams344d ago0x78548e…7094a9
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams344d ago0x50287e…16c7ff
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams344d ago0x9a41d2…2cffc6
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0xbacdc3…f3a5e3
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0xa5b086…0fa398
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0x26feb5…827fc6
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0xfd78bd…9f150f
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0x86fcc6…280746
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0x14dceb…a68d3c
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0xe20945…e29d50
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0xe6908c…b224d5
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0xc19290…5e621a
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0xb92cfe…0e309d
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0x42cecc…766fb7
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams345d ago0xd19498…5b270a
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams346d ago0x5a23f6…1a77ae
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams346d ago0xdb254d…c50440
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams346d ago0x5044cf…c886dc
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams346d ago0x6e7f70…355eb3
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams346d ago0x16fe00…9ab2c3

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

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

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: 0x40fa…7186

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