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%daydreams337d ago0xe5910c…9b90b5
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams337d ago0x247f43…6aab14
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams338d ago0x39663e…a4ad10
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams338d ago0xf60c38…a0bc65
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams338d ago0x8e658c…c247db
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams338d ago0x441a65…1133ab
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams338d ago0x656a06…18717a
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams338d ago0x01cff3…edbd54
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams338d ago0x912dd4…6ff197
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams338d ago0x62d530…b32701
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams340d ago0x6d8001…b7e806
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams340d ago0xd28dc8…5be160
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams340d ago0x0e00d8…e2a3fb
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams340d ago0x459cb3…3c1a41
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams340d ago0x0fa1f0…c675f9
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams340d ago0xfdc6cd…99dd0f
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams340d ago0xde64c2…1c4af6
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams340d ago0x758553…bfb883
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams340d ago0x102559…3e33ad
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams340d ago0x9485ef…4a13f2
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams340d ago0x391a05…c9f678
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams341d ago0x891a82…3e4330
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams341d ago0x014f02…5d7562
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams341d ago0x6999c9…091703
0xe9c5…c8280x6482…b779BaseBase$0.0001100%daydreams341d ago0xa15ba4…b104c2

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.