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%daydreams341d ago0x77d90c…838edf
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams341d ago0xfadac2…c877f6
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x3e227d…8ce4d7
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x6f91b2…666481
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x16ed20…58f249
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xd003f1…7dc237
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xc6a22e…1f1464
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x3a8bd9…fb878b
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xfa6013…c2091c
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xf734ba…2adb6f
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x544237…0a0cc0
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xe2db8b…422807
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x6bbedd…724fff
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xeb4bf1…58b943
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x34f895…9d2b0e
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams343d ago0x408e01…3b5a08
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams343d ago0x0312eb…f3008d
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams343d ago0xcc180f…7f98e1
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams343d ago0x830efb…a7c73a
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams343d ago0xee9d38…ced037
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams343d ago0xea3a07…fd9ad2
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams343d ago0x2e751d…b52773
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams343d ago0x6e0e2d…4e208a
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams343d ago0xbd3d69…2b8202
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams343d ago0xab4e69…616605

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.