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%daydreams323d ago0x7770c9…d7df27
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams324d ago0x17875e…dcc97a
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams324d ago0xab5716…668c91
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams324d ago0x754f74…095638
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams324d ago0x6ccc20…ee63ec
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams324d ago0xab4a45…d813fc
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams324d ago0xbbfe3d…0b7abc
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams324d ago0x881c7d…bcc9d2
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams324d ago0xda2dff…1d14e0
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams324d ago0x836af8…27f5a3
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams324d ago0x24fdf7…8f36b3
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams324d ago0x140b3c…4bbe2e
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams325d ago0x3ef344…09eaa8
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams325d ago0x5e822e…5caefc
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams325d ago0x28ded3…71f0a7
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams325d ago0x22e5bd…b0c05e
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams325d ago0x54bbbf…0e7750
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams325d ago0x81c68f…ec806b
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams325d ago0xa289cd…8a3c35
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams325d ago0x5913ee…69700a
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams325d ago0xcd1f8f…e04339
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams325d ago0x2ea32f…c4ebc6
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams326d ago0x9a7a11…39af9b
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams326d ago0x1a84c0…a74efd
0xebad…fb230x6482…b779BaseBase$0.0001100%daydreams326d ago0x20c003…0628c9

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.