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,396 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%daydreams353d ago0x0000b2…e7f50c
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams353d ago0x8e3c6b…910ac9
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams353d ago0xec5385…cf93cc
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams353d ago0x6fc57f…59de24
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams353d ago0xc39838…358fdb
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams353d ago0xbe0081…5abeac
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams353d ago0x062a65…41640d
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams355d ago0x710ff1…465250
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams355d ago0xec2fdb…dd0904
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams355d ago0x598a26…2b0b77
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams355d ago0xc57a4d…181c27
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams355d ago0xed7b52…15f047
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams355d ago0x0e9ea0…1052a5
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams356d ago0xd84f7b…33367f
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams356d ago0x2e0c08…d3d0b7
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams356d ago0x88244b…d3bb54
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams356d ago0x49c6df…4cfe7d
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams356d ago0x0cc0da…58f3cd
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams357d ago0xbb8afd…d53ac1
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams357d ago0x150452…aa3021
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams357d ago0x5679d3…38c782
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams357d ago0xc7c4ce…d9d5fd
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams357d ago0x87d568…8ccd1b
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams358d ago0x6cea3d…1bd028
0x62b7…ac740x6482…b779BaseBase$0.0001100%daydreams358d ago0x857328…7e5d87

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.