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 $3067.43M Roundhouse has indexed across 1,401,742 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 276d 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.00269276d 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%daydreams338d ago0x1f3165…c2c5f2
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams338d ago0x1ea09d…a6748b
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams338d ago0xb73b44…4439e8
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams338d ago0xf8f069…b62720
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams338d ago0x541df4…72ce65
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams338d ago0xced7b5…c70563
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams339d ago0xdf6197…1ba59f
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams339d ago0x5c23da…b73943
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0xf747b6…f58e5d
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0x42c188…80d90e
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0x0ac3e4…845bc6
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0x58e873…7362d5
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0xc2ecdf…e9ec7f
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0x295d45…fda314
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0xb57a06…131410
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0xca5d84…8ade16
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0xa3438e…cde3d2
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0x9758ce…e4a4e0
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0xceba21…c00120
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams340d ago0x86ccc7…d0ca87
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams341d ago0xe70ec5…064f6c
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams341d ago0x9c6b30…a74642
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams341d ago0xb6e8a5…bb6da5
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams341d ago0xd99a21…f28884
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams341d ago0x5a2347…22ff08

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.