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 $3070.29M Roundhouse has indexed across 1,403,290 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%daydreams344d ago0xd6281a…5ef25f
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams344d ago0x13518b…8b1b54
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams344d ago0x6d916b…888737
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams344d ago0xd32604…79eee6
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams344d ago0x09b514…84ee0a
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams344d ago0x3c5359…b9c50b
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams344d ago0xcfc30d…37d12b
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams344d ago0x3093a5…f4f0b4
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams344d ago0x9ad85f…2c514f
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams344d ago0x8f8d27…bae771
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams344d ago0xed4f7c…0a2c96
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams345d ago0x71d469…536f2d
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams345d ago0x771ee2…cf8a3b
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams345d ago0xba8b4a…fed139
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams345d ago0xdeba23…e978df
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams345d ago0x351ecd…4aea8d
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams345d ago0x2ddb97…839bdb
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams345d ago0xcbeaba…e80d81
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams345d ago0x7d48a0…8c0430
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams345d ago0x667ad7…07def4
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams345d ago0x1759da…3a667c
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams345d ago0x0ac173…37c5bb
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams346d ago0x247103…dc82a6
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams346d ago0x8efa79…f54c6f
0xee00…68a00x6482…b779BaseBase$0.0001100%daydreams346d ago0x4e2c6f…4dff5d

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.