AgentReport

0xee00…68a0

0xee006527eb66a6137a2442c50dd20e83034e68a0Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
265
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

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

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

$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
    265 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.00265277d 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 265 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams326d ago0xe197fc…353ac1
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams326d ago0x080eb9…4f5b02
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams326d ago0xf304d0…c6080a
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams326d ago0x6aa49e…5ac18d
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams326d ago0x0dc35e…3dee06
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams327d ago0x9b4a0b…0a2373
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams327d ago0xcede4b…863957
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams327d ago0x3760e3…fc5dbf
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams327d ago0x3dc0b8…33da41
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams327d ago0xde5867…04c835
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams327d ago0x70f1d8…2396f6
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams327d ago0xb8e389…bc0177
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams327d ago0xe9bed1…5cd393
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams327d ago0x177c24…8e39cc
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams328d ago0xbbb0f5…073751
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams328d ago0x45f0fa…2197d0
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams328d ago0xe5755f…864b14
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams336d ago0x3634b5…5542b4
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams337d ago0xdb2c17…6b4418
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams337d ago0xb25bab…0f7d5c
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams337d ago0xe8b1c7…ad44bb
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams338d ago0x35163c…f09843
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams338d ago0x09f5b7…de502d
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams338d ago0xbd3a8e…6eff97
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams338d ago0xdfdea6…7e57ca

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

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

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: 0xee00…68a0

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