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%fluxa63d ago0x913148…f56195
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x56ab35…7569ed
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x7c0a9c…fb082e
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x0abdb7…b9a541
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x0fd077…a5f776
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x39ee9c…0a0b43
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x3ab1c4…836913
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x669dbd…75ca85
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xe1db54…0f2860
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x6ccb35…7df3fe
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x483b11…1d7128
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x31781d…af2806
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x4cc845…adfd7f
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xd2ddf6…c05401
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xd7378a…8c4428
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xe06a80…2f4709
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x65716f…be5e22
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x8cd378…3f1fa4
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x9a62f5…c49039
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x15c203…d4c5a0
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x737f12…5cc678
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x743d6f…e4a73d
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0x200312…feb3d2
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa63d ago0xd5bfac…42138d
0xebda…12290xfe80…47eeBaseBase$0.001100%fluxa64d ago0x168a90…16aa8a

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.