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,722 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 277d 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.00269277d 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%daydreams357d ago0x293444…ba37d7
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams358d ago0xe69026…591d72
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams358d ago0x135b96…1cd08c
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams358d ago0xfea29c…7c6543
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams358d ago0x3cdcbf…7f6440
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams359d ago0x1ab766…2df032
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams359d ago0x34004e…4cd395
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams359d ago0xe0cc9b…fed998
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams360d ago0xc85b18…4a60f4
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams360d ago0xed1c66…bd3111
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams361d ago0xfa4554…378001
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams361d ago0xd21081…c0d4bf
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams361d ago0x5ea45e…c03d67
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams361d ago0xbfcdc1…88d7c0
0xe524…79ad0x6482…b779BaseBase$0.0001100%payAI361d ago0xc137a2…bf539b
0xe524…79ad0x6482…b779BaseBase$0.0001100%payAI362d ago0xb6281f…319777
0xe524…79ad0x6482…b779BaseBase$0.0001100%payAI362d ago0xe5c962…9ff7a9
0xe524…79ad0x6482…b779BaseBase$0.0001100%payAI362d ago0x05320f…ab5818
0xe524…79ad0x6482…b779BaseBase$0.0001100%payAI362d ago0x10b072…be4390
0xe524…79ad0x6482…b779BaseBase$0.0001100%payAI362d ago0x30fb57…434de9
0xe524…79ad0x6482…b779BaseBase$0.0001100%payAI362d ago0xa3e8db…bfe4c9
0xe524…79ad0x6482…b779BaseBase$0.0001100%payAI362d ago0x36f1c5…040a79
0xe524…79ad0x6482…b779BaseBase$0.0001100%payAI362d ago0x254693…835ba3
0xe524…79ad0x6482…b779BaseBase$0.0001100%payAI362d ago0x225da2…9a321c
0xe524…79ad0x6482…b779BaseBase$0.0001100%payAI362d ago0x8ede2d…dfb058

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.