AgentReport

0x3957…c982

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

Paid $0.03 of the $3070.29M Roundhouse has indexed across 1,403,290 wallets — less than 0.0001% of it.

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

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

$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 277d ago
    $0.03
    261 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.00261277d 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 261 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams346d ago0xbc6080…e638fe
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams346d ago0x0321d7…d27439
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams346d ago0x77147d…2224a6
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams346d ago0x77aa73…78b65b
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams346d ago0xbecaa8…bc3703
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams347d ago0x307612…229dc3
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams347d ago0xcb7148…67b7bf
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams347d ago0xbb5f71…63f0cf
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams347d ago0xfb5240…01938a
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams347d ago0x16f983…14bb45
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams347d ago0x009b1f…27ffb5
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams347d ago0xbf8476…b82983
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams348d ago0xae43ef…ea0b94
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams348d ago0x7d639d…07e3fa
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams348d ago0xb784b2…b2eb39
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams348d ago0x999fc6…b19236
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams348d ago0x95099c…64e060
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams348d ago0xd5f8af…aa7901
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams348d ago0x9871ac…ca71ec
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams348d ago0xc125dd…a3365c
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams348d ago0x9e6963…3eaa2d
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams349d ago0x4411b7…4da772
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams349d ago0xac5696…adbd0a
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams349d ago0xd20106…dd30d8
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams349d ago0xd8fe1c…5ab9ff

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

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

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: 0x3957…c982

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