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%daydreams345d ago0xdb3947…67e4e3
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams346d ago0x8ba55f…2bc414
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams346d ago0x115bf2…11974f
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams346d ago0xe4bd45…4b903d
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams346d ago0xa853db…1e8cc2
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams346d ago0x5e535b…a94c34
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams346d ago0x3dbfda…9ab6bb
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams346d ago0x2ca01f…7ada2d
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams346d ago0x7f0809…ec3c9c
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams346d ago0xf2a405…d9e7cb
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams346d ago0x22aa10…5e73e8
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams347d ago0xf5222e…b644e7
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams347d ago0x42a58e…8fd4d9
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams347d ago0x056c31…0b8f2d
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams347d ago0xbd1ca8…272ec5
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams347d ago0xa6c455…d34d88
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams347d ago0xde37a2…2de16b
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams347d ago0x48fbe0…9581b3
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams348d ago0xca49eb…97d78e
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams348d ago0x55e1cb…270d41
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams348d ago0x5732c1…d4f36c
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams348d ago0x6886aa…2d0d3c
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams348d ago0x3dd127…9e40b9
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams348d ago0x2a4f3d…b951d4
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams348d ago0x919a40…9628ff

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.