AgentReport

0x4653…d5d7

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

Paid $0.03 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.

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

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

$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
    262 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.00262276d 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 262 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams325d ago0x2b7d54…c7311b
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams325d ago0x42d63c…a5e02a
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams326d ago0xea5a80…f86fd4
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x0e7622…6c05e1
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams326d ago0xfdd130…759acf
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x0bc1c3…fbcb27
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams326d ago0xf20f78…11299c
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams326d ago0xd574a3…bed645
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x356b35…f7b081
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x8ff20f…ff036f
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x8622be…b41563
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x0fdb9a…07968a
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams327d ago0xac9894…bd94ea
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams327d ago0x0d32f3…d33d35
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams327d ago0x511830…17d52a
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams327d ago0x6bf6bc…4eff92
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams327d ago0x657f35…e4a0b3
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams327d ago0xd727c4…11fcc7
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams327d ago0xdffe53…8f33d0
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams335d ago0xc5d4c7…2514e2
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams337d ago0x3c01a9…21354a
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams337d ago0xc0abdf…76b1b9
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams337d ago0xaea754…44fdf8
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams337d ago0x8a2fe9…ed07f1
0x4653…d5d70x6482…b779BaseBase$0.0001100%daydreams337d ago0xb81887…89c761

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

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

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: 0x4653…d5d7

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