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.84M Roundhouse has indexed across 1,401,919 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%daydreams343d ago0xa5c06e…e79b95
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams343d ago0x23a069…fb56f3
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams344d ago0x5797db…409666
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams344d ago0x043f2b…4931fa
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams344d ago0x270b30…9be3eb
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams344d ago0x5cfd1a…5a3082
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams344d ago0x33e756…eef782
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams344d ago0xb50741…01f746
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams344d ago0xb4f1d8…6fbaf0
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams344d ago0xe93103…3c7ffb
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams344d ago0xa5ea1f…2cbb03
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams344d ago0xeb10fd…4d5230
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams344d ago0x4e1577…177756
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams345d ago0x4e3791…5035d5
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams345d ago0xcb68b3…73c539
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams345d ago0x0e9997…25ec06
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams345d ago0x01c2aa…3fd3c2
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams345d ago0xa3471f…51158d
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams345d ago0x90b850…5b5df2
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams345d ago0x378b73…9d3947
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams345d ago0x10cb2c…d8183a
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams345d ago0x97c915…cc4633
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams345d ago0x7ee8d9…0018ce
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams345d ago0x05c1ef…ab5513
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams346d ago0xc10145…571cf3

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.