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,722 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%daydreams352d ago0x0c9879…f04aeb
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams352d ago0x8faf89…3fda9d
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams352d ago0xb03d2d…182ca0
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams352d ago0x423ff1…a5371a
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams352d ago0xa8742b…fb1f28
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams352d ago0x790196…c5b55b
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams352d ago0x2204cb…9c3451
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams352d ago0xe13aa1…e7cc1f
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams352d ago0xb7a8cb…6fa96c
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams353d ago0x262eab…d97ba1
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams353d ago0x8267a7…64c127
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams353d ago0x880d0a…b25e69
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams353d ago0xa6532b…7ca549
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams353d ago0x3a1810…50664f
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams353d ago0x42d686…0096fb
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams353d ago0xe4cc51…2315dd
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams354d ago0x2eb862…28dffb
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams355d ago0x878da5…10e4be
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams355d ago0xd47be3…5352ad
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams355d ago0xb5fc31…d44eee
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams355d ago0xe48eae…bf9266
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams357d ago0x3f2902…2bcc34
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams358d ago0x72a608…a685c4
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams358d ago0x732560…d47fe4
0xee49…ca850x6482…b779BaseBase$0.0001100%daydreams358d ago0x96cace…5e389b

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.