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,722 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%daydreams353d ago0xcb0f2d…5c65c3
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams353d ago0xea50c9…659bc2
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams353d ago0xc72fe9…ac2dd7
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams353d ago0x9057bf…4d7056
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams353d ago0x3913dc…5003a4
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams353d ago0x9971e9…727c3a
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams353d ago0xc6e42d…c1472a
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams353d ago0x82e060…75c397
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams354d ago0x00571d…8381a2
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams355d ago0x1030cc…47b46e
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams355d ago0x3e6aba…482bce
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams355d ago0x89b976…e56aea
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams355d ago0x21976b…90fc88
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams356d ago0x576d59…2912ae
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams356d ago0xe4a2ed…eefe49
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams356d ago0xd3ec04…880a65
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams357d ago0x5d3e93…74dc89
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams357d ago0xb191ad…568f80
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams357d ago0xb667fe…6d866a
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams357d ago0x7c72c0…b8bdcb
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams357d ago0xa5d153…ad23fd
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams357d ago0xca7a49…339182
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams358d ago0x342a95…f390c0
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams358d ago0x26d63e…d1a93b
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams359d ago0x50568b…5f02ac

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.