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.00M Roundhouse has indexed across 1,400,982 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%daydreams326d ago0xb0c33e…1a3689
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x48926e…08bcf1
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x9f7e90…fdc94d
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams326d ago0xbab335…ae902b
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x8f50e1…9c4801
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x35292f…a479c9
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x533976…2878ef
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams326d ago0xb4c709…9303de
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams327d ago0x2e05c6…d04f85
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xbf13ce…75ed89
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xbfbe6a…dd2562
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams327d ago0x346826…0852f1
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams327d ago0x5b80e8…3cffdc
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xe665f2…4eda2a
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams327d ago0x5a4967…d2484c
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams328d ago0x61a547…4231a9
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams328d ago0x8d0d32…b4bc42
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams328d ago0xdc7c60…29f952
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams335d ago0x9c8780…e226e7
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams337d ago0x698d8b…53f50f
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams337d ago0x5b3cc9…e3e0be
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams337d ago0xeed368…5e77b2
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams337d ago0xc1a405…0f49de
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams337d ago0x2f24aa…489173
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams337d ago0xf8d92e…5b75c4

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.