AgentReport

0xebad…fb23

0xebadc01cbf52187e3d4bdf15519c99a2b553fb23Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
258
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,402,228 wallets — less than 0.0001% of it.

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

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

$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
    258 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.00258276d 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 258 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams326d ago0xd19f5c…2486aa
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams326d ago0x1a3453…2f5d2c
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams326d ago0xa81021…d349fd
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams326d ago0xf0f747…3bfa01
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams326d ago0x1d5f27…8a2d5a
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams326d ago0x82811c…dc82a1
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams326d ago0xa845e1…925476
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams327d ago0xe0848d…bf2ae3
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams327d ago0xdf3b75…c6acb9
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams327d ago0x680eed…27088b
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams327d ago0xfc4f19…9adf95
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams327d ago0xae3c7d…00fcc7
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams327d ago0x5b4d4a…446d7c
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams327d ago0xe92b80…48215f
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams327d ago0xcfac4c…a4a4a9
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams328d ago0xfbccbe…c69df3
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams328d ago0x1c9448…183c7f
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams328d ago0xb199da…dfdc9a
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams328d ago0xdc4a62…1387f6
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams336d ago0x97b384…66d43b
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams337d ago0x64dcc7…a4f9f6
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams337d ago0x04648f…41fb97
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams337d ago0x2f6f77…dc3f70
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams337d ago0x644f66…a97d36
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams338d ago0x93dab7…b1c6b5

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

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

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: 0xebad…fb23

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