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,255 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%daydreams335d ago0xb85298…742b5a
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams337d ago0xbcdc6d…fb5d4b
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams337d ago0xe57fb1…603508
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams337d ago0x3ed5a0…cbfe8f
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams337d ago0x8cbdfb…0cd4ff
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams337d ago0x7aabc2…c80ad3
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams337d ago0x84acf6…06279d
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams337d ago0xd648cd…57a061
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams337d ago0x5dbb6e…bb88e2
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams337d ago0xd86a95…f84204
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams338d ago0x716bcb…b9858c
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams338d ago0x294f10…278127
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams338d ago0x140074…7312c7
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams338d ago0x864ee4…16b50e
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams339d ago0xce69ce…76dd82
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams339d ago0x78b811…b506ff
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams339d ago0x09ea2b…82048a
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams339d ago0x05fd2d…4c198f
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams339d ago0x3f5f04…d41b8f
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams339d ago0x50e00d…be7323
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams339d ago0x72d87c…4d3d6f
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams339d ago0x88a805…51676e
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams340d ago0xf7406a…d4408d
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe4aa94…c95fb3
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams340d ago0x32bdd3…ccc125

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.