AgentReport

0x79ee…809a

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

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,367 wallets — less than 0.0001% of it.

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

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

$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
    262 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.00262276d 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 262 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams352d ago0x4fade2…f8b155
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams352d ago0xac3ba2…0722d8
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams352d ago0xb5a63c…5744c5
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams353d ago0x2ca6f1…87d808
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams353d ago0x4a4bc3…ee2565
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams353d ago0x3c523e…968244
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams353d ago0x9c7a78…4f04bd
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams353d ago0x42cc96…f30665
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams354d ago0xa044de…4086a4
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams355d ago0x23f668…d9be16
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams355d ago0x2b844c…1d4122
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams355d ago0x0ea16a…5efcae
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams355d ago0x492414…4c9dcb
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams355d ago0xb1b95d…23e179
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams356d ago0x73da27…ad1cac
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams356d ago0x0e041e…128321
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams356d ago0x645248…1caa9e
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams356d ago0x9754d1…a3ea41
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams356d ago0x227500…6d0359
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams357d ago0x47807a…afcc35
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams357d ago0x80e4c4…784a08
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams357d ago0x8c9523…691ef1
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams357d ago0xcd181f…9a72b5
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams358d ago0x181169…8a35b0
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams358d ago0xc2eb8b…4a838c

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

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

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: 0x79ee…809a

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