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%daydreams326d ago0xab65ee…add14f
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams326d ago0xd9040c…60fba6
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams326d ago0x41ba83…aafb2d
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams326d ago0xd51616…064508
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams326d ago0x77cbf8…fec4f5
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams326d ago0x1a6102…f89eb4
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams326d ago0x7a059c…d9f6c2
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams326d ago0x7cdb7d…d63c5b
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams326d ago0x71a0f6…16b0f8
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams327d ago0x5cae9d…e56499
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams327d ago0x3db03a…abecc1
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams327d ago0xb69beb…018c53
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams327d ago0xeb85eb…112d8a
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams327d ago0xa5095c…cd76d9
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams327d ago0xe5eef0…5f5786
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams327d ago0xfd280b…984c16
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams328d ago0x4e32e5…bba646
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams328d ago0x050e58…2a95e0
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams328d ago0x5ccc8f…6e6db7
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams328d ago0x37442f…c51014
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams336d ago0x592595…da89fc
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams337d ago0x8768cb…c8d8a4
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams337d ago0x142846…3f3c77
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams337d ago0xbf64e5…1ba6ac
0x2ebc…bfeb0x6482…b779BaseBase$0.0001100%daydreams337d ago0x462339…8f0f03

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.