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%daydreams276d ago0xfeaeea…e92cd2
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams279d ago0x17ee5c…059224
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams280d ago0x56cf13…bd09c6
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams321d ago0x95293e…69db80
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams321d ago0xdf35b4…2dc6a4
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams321d ago0x65488a…ca6397
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams321d ago0xa61578…765d37
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams322d ago0x43ef20…4f73e6
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams322d ago0xf7a7bd…166060
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams322d ago0xf1c61b…50aacf
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams322d ago0x3d4f0e…440d3f
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams322d ago0xfee71b…284709
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams322d ago0xeeec0b…6bda9a
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams322d ago0x861dde…874a9d
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams322d ago0xb19660…7e5123
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams322d ago0xd1c1fb…b591b3
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams322d ago0x41b3d0…37efde
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams323d ago0xc0ccb7…d36fb4
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams323d ago0x975cd2…e4ab89
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams323d ago0x3e980b…db7c68
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams323d ago0x6d161c…a2f2db
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams323d ago0x16aca9…dd2985
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams323d ago0x00dd91…c326f5
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams323d ago0xb98787…0f9efb
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams323d ago0xe7f7f1…052c99

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.