AgentReport

0x665e…9762

0x665e47477adb60cf2fbd28c67da0cc7291d19762Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
265
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 (265)

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

$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
    265 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.00265276d 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 265 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams343d ago0x9a8ce0…b2597b
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams343d ago0x6a6247…91d88d
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams343d ago0xc77244…9dd428
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams344d ago0x7e5515…05df5a
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams344d ago0x981c3e…89cbfa
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams344d ago0xfd873b…26b97d
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams344d ago0x1a35cb…3979d7
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams344d ago0x422b1c…66006a
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams344d ago0x7041a8…d28401
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams344d ago0xf2d304…35c358
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams344d ago0x2a1ae7…470568
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams344d ago0x77e024…6b4803
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams344d ago0x0a6bfb…04dc98
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams344d ago0xc31ac4…d60c27
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams345d ago0xc9bfc8…92ec9f
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams345d ago0x85cc77…bc9636
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams345d ago0x1cc6e8…9aa9ef
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams345d ago0x57528d…72fd83
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams345d ago0x7bfd08…33d592
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams345d ago0xce2b9a…c69e88
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams345d ago0x0ebcf2…c7f390
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams345d ago0xf7bf0a…05ea83
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams345d ago0xf8594e…3bf863
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams345d ago0x5847ed…0c1316
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams345d ago0x664d03…9ae3aa

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

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

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: 0x665e…9762

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