AgentReport

0x2ebc…bfeb

0x2ebc0cb9cfad1cfb999c65313d0eb7c4789dbfebExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
269
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 (269)

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.032691

$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
    269 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.00269276d 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 269 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams323d ago0x1e0e8d…c0b348
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams323d ago0xef7c0f…d2099b
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams323d ago0xdac174…93e0ca
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams324d ago0xbba291…fa0da8
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams324d ago0xe68f53…f1d6c2
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams324d ago0x4f24b6…1b869a
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams324d ago0x46a3fc…a713be
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams324d ago0xe2d839…ed4907
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams324d ago0x8bbb98…567acf
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams324d ago0x5a3e9e…3d5b12
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams324d ago0x2bdea6…ca16d9
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams324d ago0x179a83…ef963e
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams324d ago0xbad7a5…024501
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams325d ago0xd23e05…ad7e4d
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams325d ago0xb54576…e0a199
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x5b0ff4…5c9bad
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams325d ago0xb2dbea…b02565
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams325d ago0xf28590…9b3c45
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x83cc96…c5b43f
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x26f1c0…f2d858
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x66096e…c889a7
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x855c34…1188e3
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x6b9e87…fc1b4c
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x071ebc…989bea
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams326d ago0xe5ef16…f3afbb

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 0x2ebc…bfeb has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x2ebc0cb9cfad1cfb999c65313d0eb7c4789dbfeb

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: 0x2ebc…bfeb

curl -s 'https://api.roundhouseai.io/v0/agents/0x2ebc0cb9cfad1cfb999c65313d0eb7c4789dbfeb'
curl -s 'https://api.roundhouseai.io/v0/entities/0x2ebc0cb9cfad1cfb999c65313d0eb7c4789dbfeb/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.