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,398,118 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%fluxa65d ago0xbb465e…95a127
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa65d ago0x0f07ee…735f28
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa65d ago0x7f3dce…f5ecf6
0xebda…12290x9c95…e299BaseBase$0.001100%fluxa77d ago0x29b750…77ea3b
0xebda…12290x9c95…e299BaseBase$0.001100%fluxa77d ago0x74e2d4…df1d1f
0xebda…12290x9c95…e299BaseBase$0.001100%fluxa77d ago0x1fbaf7…ec57d1
0xebda…12290x9c95…e299BaseBase$0.001100%fluxa77d ago0x26d30b…33ef9a
0xebda…12290x9c95…e299BaseBase$0.001100%fluxa77d ago0x0f9d84…d46756
0xebda…12290x9c95…e299BaseBase$0.001100%fluxa77d ago0x680c1c…671b06
0xebda…12290x9c95…e299BaseBase$0.001100%fluxa77d ago0x280214…59e96c
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa77d ago0x7bb9de…a447ee
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa77d ago0xd664ed…e84d54
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa77d ago0x03a04c…4b188b
0xebda…12290x9c95…e299BaseBase$0.001100%fluxa77d ago0x0b4fe2…179671
0xebda…12290x9c95…e299BaseBase$0.001100%fluxa77d ago0x4daff9…b1899f
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa77d ago0xc173b3…0c83b4
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa77d ago0x759537…4ab9fd
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa78d ago0xdca712…085493
0xebda…12290x9c95…e299BaseBase$0.001100%fluxa78d ago0x0ebbb3…0f5685
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa78d ago0x6d1848…e47c86
0xebda…12290x9c95…e299BaseBase$0.001100%fluxa78d ago0x165a7f…58bc12
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa78d ago0xac4458…d83945
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa78d ago0x556663…d76f0e
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa78d ago0x28ee3d…04629e
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa78d ago0xa6b637…7f96b6

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.