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,991 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%fluxa64d ago0x1a56a4…a1b043
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0xe86077…bd3a2d
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0xd82ddb…15af0a
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0xd3af68…ec9d17
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0xebfb9a…c26f91
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x070921…5b2843
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x52282e…cac0a5
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0xddaf21…58b49b
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x33afe2…085502
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x22cf2a…70c9e2
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x8c151c…e8b06b
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x8ed9bc…598a60
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0xb6fbda…9666e9
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0xcf06d1…958da8
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x4106bf…1eee4e
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x735355…c72889
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0xd2be35…cd1a04
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x54707c…db5d31
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0xbcdaa4…c0e077
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0xf1d4c4…89a67a
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x3e0542…c4bc4d
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x207136…2b59f3
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0xfa7a13…c612d7
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x23a277…484baa
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x903123…aa3cff

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.