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.46M Roundhouse has indexed across 1,397,861 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 ago0xcbc861…47252c
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xce67a5…f70b40
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa62d ago0xc4467a…5a9d92
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xdb4e54…419db7
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x8e5def…0ba87c
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x36846c…7c9269
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x1dc83c…f5b118
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x09b3ec…0bff00
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x88ce18…c86388
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xb8a017…9640c3
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xd2e3b6…7a448e
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x3c7b17…a31bca
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x846d06…f0006d
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x6291ea…b2c6c8
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x0453ac…2db6cf
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x7d22c4…5a9193
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xd981da…45c726
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x691dd2…03b62a
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x4c9ba7…391372
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x511ba0…d89428
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xf38b4d…65393b
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xeb92f8…029215
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xd4b811…b632d8
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x5309bc…0dd9e3
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xf4103d…43da9b

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.