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 $3059.84M Roundhouse has indexed across 1,397,384 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%fluxa61d ago0xb80f03…b395e9
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa61d ago0xffc589…fd11df
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa61d ago0x61fa3d…e94ecb
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa61d ago0x5511ad…a8298e
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa61d ago0xfc4e9e…36a50a
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa61d ago0xc181f2…d82c56
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa61d ago0x25afa2…a4eb20
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa61d ago0x8091b2…6244a9
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa61d ago0x3f55e8…27c80c
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x239e3b…38eb42
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x1e1fa4…03fa9c
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xe7e7ce…1ae831
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xc342b4…dc276f
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xbf663e…37b0fe
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x9df844…eba405
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xd99e36…790726
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x978bf1…8c1c0b
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x4268f3…6a0e1a
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xe17f81…e4c42a
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xa55c97…a78ef5
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x296ad5…1a01cc
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x9d440c…88d64f
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0x5f3401…ba3837
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xaba69f…2fda2d
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xcfa0c7…826d9a

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.