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%daydreams352d ago0x357a01…90b1fe
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams352d ago0x008227…8f9622
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams352d ago0x917017…75b545
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams352d ago0xcac93d…f9219f
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams352d ago0x1bd299…a437f2
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams352d ago0xf5038f…fed22c
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams353d ago0x355471…04e1ec
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams353d ago0xed1ee3…0c22bd
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams353d ago0x72ecc5…42be92
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams353d ago0xc0ff3d…ef6611
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams353d ago0xb2a412…f21d65
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams353d ago0xcccea9…4c56ab
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams354d ago0xa32d85…9e3c9f
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams355d ago0xfa5f5e…d7fa58
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams355d ago0xc8d3d7…f81bb5
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams355d ago0xa12d34…eba67c
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams355d ago0xcd851a…3a0036
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams355d ago0x26e7cf…f4b47b
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams355d ago0xcf6f3a…de7d3b
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams356d ago0xfc1c18…74f06a
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams356d ago0x1ba3eb…c07d67
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams356d ago0xb6deb3…784636
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams356d ago0x172baa…971095
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams357d ago0x692654…05dbab
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams357d ago0x7f68e0…e6439a

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.