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%daydreams341d ago0xa04ee1…51ba83
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams341d ago0xab6fad…348212
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams341d ago0x92f40c…4dea30
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams341d ago0x8f8f09…6103fc
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams341d ago0xb8a38f…4c642a
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams342d ago0x14effe…a46605
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams342d ago0xb13bfa…468eb2
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams342d ago0xbc6714…7dcf21
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams342d ago0x68a83b…0d4f1b
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams342d ago0x225ec7…46a8f1
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams342d ago0xfd06f6…b9e0d2
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams342d ago0xa33345…ad9605
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams342d ago0x82adfe…88d675
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams342d ago0x9b6300…d09e54
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams342d ago0x9a0a23…5413b7
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams342d ago0x0136bb…bdb05e
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams343d ago0x506650…ea546c
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams343d ago0x139c2b…7790db
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams343d ago0x3011ce…93a085
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams343d ago0xeb11e8…a42647
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams343d ago0x7cbee8…e5c6dc
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams343d ago0x09f593…f955fd
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams343d ago0x00d4da…cba7c7
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams343d ago0x22bc86…c83d0d
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams343d ago0xa5a0c6…c72f66

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.