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 $3067.84M Roundhouse has indexed across 1,402,228 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%daydreams326d ago0x78c9e0…0ca467
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams326d ago0x0c59d0…74cad6
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams326d ago0xdcc555…91fe12
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams326d ago0xe790ba…962dc5
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams326d ago0x6215ac…7bb532
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams326d ago0xf4f8a6…2845a0
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams326d ago0x6f84a0…7b0509
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams326d ago0xbb5ab0…62efe9
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams326d ago0x181f81…cd9941
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams326d ago0xe7c9f3…94b23b
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams327d ago0xc19e6f…926f83
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams327d ago0xe7d68e…61466e
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams327d ago0xa3881d…679eaf
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams327d ago0x02565e…f8a95e
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams327d ago0x8d069d…e66f82
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams327d ago0xb64163…e0380d
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams327d ago0xf3e1f2…ebda93
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams327d ago0x42f310…3c81cb
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams327d ago0x3675c2…ba3efa
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams328d ago0x252f38…3027a1
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams328d ago0x75b5f3…580625
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams328d ago0x26dd0d…50ccd2
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams328d ago0xb7b4a6…cc1d89
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams328d ago0x2caf72…d313d8
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams336d ago0x3ece73…6d1d60

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.