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,510 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%daydreams347d ago0x20d67d…a7cd04
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams347d ago0x023a48…e19733
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams348d ago0xb9578e…2dba1c
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams348d ago0xbaa8f2…f900d0
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams348d ago0x1aaf44…0112f9
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams348d ago0x591ddd…8fea5d
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams348d ago0xafc006…5fa2c6
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams348d ago0xcef44c…ad82d0
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams348d ago0x2cbdb1…c17b78
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams348d ago0xc23d61…5a5db0
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams348d ago0x6c7d96…39b858
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams348d ago0xb634ef…861724
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams349d ago0xb53438…885d6f
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams349d ago0x8a8a8a…f54d7a
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams349d ago0x9fb9df…d606b9
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams349d ago0x04a172…f1c069
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams350d ago0x517f48…d930e7
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams350d ago0x3afcb3…780f86
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams350d ago0x06cae1…9feab4
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams350d ago0xab459c…e27ce4
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams351d ago0x0d60f6…cfb595
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams351d ago0xf7109c…b1d2c6
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams351d ago0x41ed52…c4e048
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams351d ago0xb94275…ae220d
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams351d ago0x11036c…bc1633

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.