AgentReport

0x694c…f30b

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

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,689 wallets — less than 0.0001% of it.

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

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

$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 276d ago
    $0.03
    285 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.00285276d 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 285 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams351d ago0x70229e…270937
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams351d ago0x16acd4…391a46
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams352d ago0x4f2b68…ed1bda
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams352d ago0xe33800…61e1c5
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams352d ago0x39b518…916896
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams352d ago0x30cfba…483706
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams352d ago0x165221…4ffa5f
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams352d ago0x3890b6…4548ad
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams352d ago0x10be5c…58ddd7
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams352d ago0xdee4b8…eced95
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams352d ago0x933fd8…427611
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams353d ago0x885ab8…549fd7
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams353d ago0x98d165…004ea1
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams354d ago0xe21dd0…c48366
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams354d ago0x41e592…2878d7
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams355d ago0x6382f2…90d671
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams355d ago0x12af7b…ef4473
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams355d ago0xe5cdee…ed4f7c
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams355d ago0xa6bc44…2b0f42
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams355d ago0x2381c5…8fff87
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams355d ago0x3c587e…5c2bf5
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams356d ago0x372b0e…5354e0
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams356d ago0xa76400…ecbfc5
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams356d ago0x259899…abcf4a
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams356d ago0xdad3a9…e4821b

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

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

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: 0x694c…f30b

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