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,563 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 277d 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.00268277d 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%daydreams348d ago0x5a22d8…b9486f
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams348d ago0x42226a…cc4c24
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams348d ago0x0cf44d…1e68b9
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams348d ago0x1414a4…849579
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams348d ago0xd7e5bb…d269c9
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams348d ago0x9282f3…cd033a
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams348d ago0x309ccf…f1c73e
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams348d ago0xc1247d…116fa8
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams348d ago0xf35e89…26c0e6
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams349d ago0xd5c534…8b1340
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams349d ago0x4c91df…161c41
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams349d ago0xe80455…ddee12
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams349d ago0xcf7548…64fd0f
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams349d ago0xe0e362…7f94a3
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams350d ago0xa35fea…9a93b4
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams350d ago0x13ed26…588d86
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams350d ago0x4b168e…610173
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams350d ago0xe8352b…be93d4
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams350d ago0xe0639e…15481b
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams350d ago0x391a3d…c98981
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams350d ago0x8c1ae3…eead17
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams351d ago0xc6b340…a8b462
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams351d ago0xc6366f…1171d2
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams351d ago0x0b34af…c82e81
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams351d ago0x073d84…0fb479

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.