AgentReport

0xe9c5…c828

0xe9c51feaac82f881f764184bf706cb95463bc828Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
258
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,722 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (258)

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.032581

$0.03 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.

  • 0x6482…b779 · last paid 277d ago
    $0.03
    258 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
0x6482…b779$0.03$0.00258277d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 258 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams326d ago0x6a8215…68947a
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams326d ago0x06ca2b…22b098
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams326d ago0x3e4c55…2b482f
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams326d ago0xf69e71…8458e0
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams326d ago0xa4ba32…d44a75
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams326d ago0xd9ed44…006edf
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams326d ago0x2741f7…993b72
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams326d ago0x5e8aaa…317869
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams327d ago0x2a2755…cb9918
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams327d ago0x3cb07a…830ae4
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams327d ago0x36fbed…0a4468
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams327d ago0x22ffbc…a6d4ae
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams327d ago0x303bfd…f61e89
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams327d ago0x0d0588…d49c1f
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams327d ago0x8e20b8…7df6bb
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams327d ago0xea6196…a62977
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams328d ago0xfc34c5…9d5cfb
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams328d ago0xc158f7…d6520c
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams328d ago0x5e7adf…64a6bf
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams328d ago0x6926d9…b2798d
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams328d ago0x1d4e2f…f4a632
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams328d ago0x99d3f5…b203f3
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams328d ago0xdbe827…e5feb5
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams336d ago0xcaf70d…30c9ad
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams337d ago0xabdbed…8c8969

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 0xe9c5…c828 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0xe9c51feaac82f881f764184bf706cb95463bc828

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: 0xe9c5…c828

curl -s 'https://api.roundhouseai.io/v0/agents/0xe9c51feaac82f881f764184bf706cb95463bc828'
curl -s 'https://api.roundhouseai.io/v0/entities/0xe9c51feaac82f881f764184bf706cb95463bc828/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.