AgentReport

0xd66d…6169

0xd66d82f2fa9b04c36baacb61a3c7f6269d146169Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
255
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3070.29M Roundhouse has indexed across 1,403,290 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (255)

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

$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 277d ago
    $0.03
    255 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.00255277d 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 255 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams346d ago0x70c38f…5adde8
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams346d ago0xe43bc8…a9fe77
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams346d ago0xe1b1ff…66ab5d
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams346d ago0x56245b…3fe2a4
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams346d ago0xe9489e…af8d54
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams346d ago0xd09b59…ba1bff
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams347d ago0xcac26b…847260
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams347d ago0x790d42…0ddd54
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams347d ago0xf63950…9a9a6d
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams347d ago0x96fdce…bb2495
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams347d ago0x159cf6…d6477b
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams347d ago0x7b01b5…1fa1e9
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams347d ago0xfd056b…37cabc
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams347d ago0xa4890b…50821a
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams348d ago0x5ce5ad…aa31dd
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams348d ago0xf65609…b93815
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams348d ago0xc70526…67a23d
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams348d ago0x7a08d7…674bf1
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams348d ago0x2c953b…685d5b
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams348d ago0xb4af37…4e3f87
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams348d ago0xf795b6…5dcec8
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams348d ago0xcbfdd5…5ba8dc
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams348d ago0x7d4f67…ddd303
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams348d ago0xddd52b…7cca38
0xd66d…61690x6482…b779BaseBase$0.0001100%daydreams349d ago0x2379fc…68d504

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

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

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: 0xd66d…6169

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