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.43M Roundhouse has indexed across 1,401,742 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%daydreams326d ago0x62a97a…59c069
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams326d ago0x0bd507…a30994
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams326d ago0xdb2f4f…92911d
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams326d ago0x474076…cd8118
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams326d ago0xd50797…e45552
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams326d ago0x937c02…f26ef2
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams326d ago0x502ba2…4340df
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams326d ago0x952141…5d12da
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams326d ago0x95f833…060328
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams327d ago0xeb4263…66aa13
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams327d ago0xc07705…78de0c
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams327d ago0x7a72d7…98c58f
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams327d ago0xf73b9c…620fd5
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams327d ago0xac6438…8f76cd
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams327d ago0xc824d3…3aadf5
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams327d ago0xbb986e…ba2670
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams327d ago0xbef1a0…229af6
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams327d ago0xb43be8…8740c1
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams328d ago0x7bc90e…2036cb
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams328d ago0xf2b6a8…f480f5
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams328d ago0xaf6be4…a7dfab
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams335d ago0xe12c0e…2678d6
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams337d ago0xfd84ba…5bd65b
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams337d ago0x99ad05…2a0ef5
0x665e…97620x6482…b779BaseBase$0.0001100%daydreams337d ago0x28a080…a6ffad

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.