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%daydreams349d ago0x4295fe…0c2779
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams349d ago0x147722…98154d
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams349d ago0xc9ad29…a15d8e
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams349d ago0xe1b6a5…6b95ed
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams350d ago0x3bcab6…bd59eb
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams350d ago0x7ec058…5b4d6a
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams350d ago0x3db155…55785c
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams350d ago0xbaf0ce…9fbe1c
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams350d ago0x301ef5…425029
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams351d ago0xf9fc3a…d5b6ad
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams351d ago0x19439d…3639fa
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams351d ago0x9faa52…03a6b4
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams351d ago0x2a6116…88208d
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams351d ago0xe84081…f9c56b
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams351d ago0x50ae3b…5c8438
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams351d ago0xed293d…b82421
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams352d ago0xb5ad51…ec221d
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams352d ago0x3dabd6…a6dc58
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams352d ago0xb8fef2…7d2151
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams352d ago0x3cf9da…c57e6a
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams352d ago0x143321…36b4ac
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams352d ago0x1811fb…84cb04
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams352d ago0x337d4e…d9a52c
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams352d ago0x12631c…0168d4
0x3957…c9820x6482…b779BaseBase$0.0001100%daydreams353d ago0x3cf85e…f06443

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.