AgentReport

0x62b7…ac74

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

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,722 wallets — less than 0.0001% of it.

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

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

$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
    269 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.00269277d 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 269 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams349d ago0x55e51b…8262a9
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams349d ago0x67dd18…581f1f
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams349d ago0x0de9d3…2e082e
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams349d ago0xe309fc…c8c903
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams349d ago0x56500c…f1fc9b
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams349d ago0x0c41f7…3bedea
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams350d ago0xe2fb51…36b842
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams350d ago0x8ef8f6…65d867
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams350d ago0xda5414…26c796
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams350d ago0xe622a5…f7e590
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams351d ago0x71bc55…710127
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams351d ago0xd05393…fdb115
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams351d ago0xac420e…77b308
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams351d ago0x1ba0a6…3c29e5
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams352d ago0x301339…0d5551
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams352d ago0x1ff377…390e6f
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams352d ago0x90fdb3…2f9e80
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams352d ago0x28de24…3e08a3
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams352d ago0xbb9912…8c9ba2
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams352d ago0x219dbc…186ac8
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams352d ago0x6a34cb…f6d9c4
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams352d ago0xf47384…20fc51
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams352d ago0x7b7e54…d9df5a
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams352d ago0x8e090d…ff0b70
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams353d ago0x2193cf…6dc1e6

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

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

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: 0x62b7…ac74

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