AgentReport

0xebda…1229

0xebda85fce911fff33d87822da0b262474e6a1229Explorer
Paid out
$0.65
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
653
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.65 of the $3060.21M Roundhouse has indexed across 1,397,717 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (653)

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

$0.65 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.

  • 0xfe80…47ee · last paid 45d ago
    $0.44
    437 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9c95…e299 · last paid 77d ago
    $0.22
    216 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
0xfe80…47ee$0.44$0.0043745d agoGraph
0x9c95…e299$0.22$0.0021677d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

67% of observed volume is with a single counterparty, in all 653 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xfffcf7…ffa930
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x5b754d…3933ba
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x0af1dd…acee5a
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xcb6218…a07768
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xf4ed19…3bb5b8
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xcfeac9…66a223
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x13f200…177433
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xc82cd6…56f880
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xaef3cc…18accf
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x0932d7…a7418f
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xbf7b9f…98756f
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xa111fc…0f9ec8
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xf0c89e…7f1f14
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x705e22…8dca98
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x4dee49…e95853
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xfdd291…4337cd
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x4c2443…79310c
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x30b1d3…6907bc
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x163c0c…372b2d
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x95868f…7d456f
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xc78545…ea5db7
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x5325ac…bbc0e3
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xdc6f40…aa249d
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xb2af60…f438eb
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xdd714e…d3e8de

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

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

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: 0xebda…1229

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