AgentReport

0xee49…ca85

0xee49acad924277d6ce934d6c9904e391689fca85Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
268
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,396 wallets — less than 0.0001% of it.

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

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

$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 276d ago
    $0.03
    268 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.00268276d 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 268 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams337d ago0x38636d…5b3c4c
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams337d ago0x7a6480…228da3
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams337d ago0xeada9a…f30c78
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams337d ago0x25fa61…8e0bf9
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams338d ago0x93c6e9…5fe751
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams338d ago0x5da130…3b7e4f
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams338d ago0xb72848…1bd156
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams338d ago0x250510…e2593e
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams338d ago0xa21209…7f2d1a
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams338d ago0x9e3043…1c0af5
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams338d ago0xd20c25…b23797
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams338d ago0xb820f6…e21c63
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams339d ago0x0557f2…f77f1e
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0x0378ba…5fe17e
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0xb67947…9eedb2
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0x7adef6…a9287c
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0x9ea4a5…b3b85a
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0x8de956…f66187
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0x407d66…ac48a7
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0xae2ac4…c856ed
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0x392811…aa07e5
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0xc71e12…7bbd92
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0xfdab88…015536
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0x395e39…420a6a
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams340d ago0xfa813b…42f955

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

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

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: 0xee49…ca85

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