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,401,091 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%daydreams337d ago0xfed12e…f836d7
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams338d ago0x06b9e2…03d3e9
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams338d ago0xf9f745…b093b4
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams338d ago0x4819e7…830055
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams338d ago0xbf71c4…3ab3a2
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams338d ago0xcff3d8…888296
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams339d ago0x1bc30a…9da1c0
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams339d ago0x7d67ac…074981
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams339d ago0x4e61a6…633281
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams339d ago0xa2013e…4b66e1
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams339d ago0xa9c370…4438bc
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x2430a2…857d30
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x4bd51c…071023
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x8db2a9…c1cd24
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x723eaa…7aa461
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x7c0fc3…9fe4ac
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x51c3c7…4f6fe2
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x35c3e8…5e9d54
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xb8c444…deba51
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xf58dac…a0aa34
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x88b118…ce2e04
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams341d ago0x80fb4e…e6805c
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams341d ago0x482da2…6d293a
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams341d ago0x8b2a42…8bbc8f
0x79ee…809a0x6482…b779BaseBase$0.0001100%daydreams341d ago0x98366f…8771d7

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.