AgentReport

0x6809…4fb2

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

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,722 wallets — less than 0.0001% of it.

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

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

$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
    257 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.00257277d 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 257 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams338d ago0x396197…d30057
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams338d ago0x5595f8…4b09e7
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams338d ago0x1e4540…938041
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams338d ago0x1cef9a…0667f7
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0xce7a0f…6bd909
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0x38dce5…25ecac
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0x208595…83eb0f
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0xd00d26…86ec64
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0x6e59b9…c354b7
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0xb8c5ff…79a8ce
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0x05688d…301bfc
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0x31b83a…568a45
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0x4b2cc1…65f6d6
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0x814237…8d5e88
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0x7fe7c4…6c19ed
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams340d ago0x494a41…40d98b
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams341d ago0x676e18…104813
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams341d ago0x8190cc…66b697
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams341d ago0x71713c…da9d00
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams341d ago0x6d294e…2a27cc
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams341d ago0x8a9600…129b78
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams341d ago0xcdb487…20aa81
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams341d ago0x960953…60ccb1
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams341d ago0xf47ffb…d75398
0x6809…4fb20x6482…b779BaseBase$0.0001100%daydreams341d ago0xb7cc2e…f7a227

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

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

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: 0x6809…4fb2

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