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,396 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%daydreams338d ago0x4594c7…cb1297
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams338d ago0x392bc0…d947e8
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams338d ago0x269c70…c2ce95
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams338d ago0xf970a0…2e54d8
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams338d ago0x5e89d3…92c74f
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams338d ago0x4da913…6057ba
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams338d ago0x01ea91…bcba30
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams339d ago0x99c902…da3577
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams340d ago0x881911…22e101
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams340d ago0x92c778…109ad4
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams340d ago0x39419e…bf2fae
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams340d ago0x6e68fd…627c91
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams340d ago0xfa2d51…670f52
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams340d ago0xbc9ba9…5f727d
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams340d ago0x4ac1b7…d9158d
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams340d ago0x63b036…b66e3a
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams340d ago0xca0f6a…457804
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams340d ago0x5b3ed8…e08529
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams340d ago0xacfd6e…251aa0
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams341d ago0x17201d…4ef37c
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams341d ago0x3c5b6f…be6b3d
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams341d ago0x263460…dcec30
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams341d ago0x6bb4cd…1de152
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams341d ago0x729fcf…4e7310
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams341d ago0x6457fb…68ce3f

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.