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%daydreams345d ago0xfcf5a3…7beec8
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x68a688…7ba262
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams345d ago0xea3ac3…2c94c4
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x44f806…5acaa5
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x30235f…10abea
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams345d ago0xb475f0…3d848a
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x3c9198…7b89cf
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x686fdb…4b4e6d
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams345d ago0xa2950a…d26abe
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams345d ago0xdb564c…900be3
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x32a38f…aaac5d
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams346d ago0x844756…6e92b6
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams346d ago0xae6e12…1b5ae7
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams346d ago0xa73a15…f3cdb9
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams346d ago0x7a5e7d…e95fa1
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams346d ago0x609a33…1343fc
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams346d ago0xf75fd1…505ac0
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams346d ago0x1c940c…356487
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams346d ago0xeaa37c…ed4377
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams346d ago0xbd765a…c1b87f
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams346d ago0xd33c81…1fc841
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams346d ago0xebe410…fc3ea1
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams347d ago0xea95b7…4e04c4
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams347d ago0x02a189…05c3c4
0x694c…f30b0x6482…b779BaseBase$0.0001100%daydreams347d ago0x0cc53a…be772e

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.