AgentReport

0xe524…79ad

0xe52412f90e27e0acc2b0d99e2dc0e9b833fe79adExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
269
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,396 wallets — less than 0.0001% of it.

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

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

$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
    269 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.00269276d 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 269 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams337d ago0x5f4924…e32369
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams337d ago0xedf52b…9bedd8
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams337d ago0x7bb87b…6cd60d
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams338d ago0x5c0b01…aaca47
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams338d ago0xc21d53…125fc3
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams338d ago0xc0832a…8cb85f
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams338d ago0x30a943…5ec4d8
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams338d ago0x7e8cd2…4756e8
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams338d ago0xa55879…b20a3f
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams338d ago0xfc4784…8778cd
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams338d ago0xc6f697…d4fa0f
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams339d ago0x0f89f4…087688
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams340d ago0x6b2406…2dd099
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams340d ago0x97237a…9758c7
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams340d ago0xf1f3aa…c95013
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams340d ago0x33f302…b692e6
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams340d ago0x785a42…6decd8
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams340d ago0x6fdae0…7dad40
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams340d ago0x002671…60cd85
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams340d ago0xd8f46d…c0e0b6
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams340d ago0x9f6bed…abd01e
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams340d ago0xbdda5b…2a2e42
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams340d ago0x224acd…27502d
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams341d ago0x3a2f91…7e5f2f
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams341d ago0xc32299…0c0e4e

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

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

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: 0xe524…79ad

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