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%daydreams338d ago0xec1281…6e0423
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams338d ago0x60a01b…0f6bc4
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams338d ago0xb6373e…2854a4
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams338d ago0x61eecb…f84a87
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams338d ago0x44076b…8c38ed
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams340d ago0x2e177e…594a99
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams340d ago0xf369a0…05060f
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams340d ago0x66df8b…9eb4d4
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams340d ago0x735450…0e7421
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams340d ago0x49d3e1…1f543e
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams340d ago0x575986…a6b073
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams340d ago0x5bcc70…a08df9
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams340d ago0xe123e3…ab0f3e
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams340d ago0x040115…8450c7
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams340d ago0xab9d16…501025
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams340d ago0xa497cc…0e8ad6
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams341d ago0x5bbd73…2d5434
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams341d ago0xc32857…566df0
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams341d ago0xec4c44…9b8d1a
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams341d ago0x4fb228…998662
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams341d ago0x8ea79f…906fe9
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams341d ago0xa10abc…fe998a
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams341d ago0xd45b4f…996c69
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams341d ago0xf3f33d…726fea
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams341d ago0x40a24f…cb4530

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.