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 $3068.58M Roundhouse has indexed across 1,402,563 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 277d 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.00258277d 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%daydreams346d ago0x4c5c3e…f4fb14
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams346d ago0xf5e49a…f87112
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams346d ago0xe7480f…ad96d7
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams346d ago0xfe3c17…4bee0e
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams346d ago0x4c14e5…142909
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams346d ago0x5e9277…0964f8
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams346d ago0x1282ee…6df68a
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams346d ago0xcdb9b6…167a92
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams346d ago0x0149ab…658d3b
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams346d ago0x5ef242…c93384
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams347d ago0x1bf6aa…0a4a3f
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams347d ago0x7d0935…8e9d95
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams347d ago0xa326fc…d2a008
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams347d ago0xe94dea…56be4a
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams347d ago0xf9c7af…18633f
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams347d ago0xb13784…3118c8
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams347d ago0xc29f3a…2b89a6
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams348d ago0xde8731…dcd042
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams348d ago0x2aa291…a4c148
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams348d ago0x221e02…31306d
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams348d ago0x20d24c…8330c4
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams348d ago0xe00482…fca594
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams348d ago0x3358a5…494a24
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams348d ago0x9e3d8d…14056d
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams348d ago0xc155ac…cc0140

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.