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,563 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%daydreams345d ago0x14e3d0…2c0c49
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0x29219e…7a1a16
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0xfefb6a…093ad0
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0x33d71d…b8c5bf
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0xca55fa…1657ba
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0xdef8b3…7bc89e
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0xf15114…315881
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0x77a5a9…b3e68f
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0x9e0451…c31703
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0xf47b78…559236
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0x0c6140…32a6f2
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0xf13073…d61e76
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams346d ago0xeba91d…b7e4a5
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams347d ago0x82240c…cb91c5
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams347d ago0x62689d…939d22
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams347d ago0x9a3cbe…8076f2
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams347d ago0xf6595a…cd3fa8
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams347d ago0x8dc92e…abe5e5
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams347d ago0xef8688…c97242
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams348d ago0x18e71e…c248e4
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams348d ago0x293a9e…601283
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams348d ago0x6c4e9f…4671c4
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams348d ago0x93e0d6…e8c160
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams348d ago0xaa2234…62f038
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams348d ago0x556043…0085aa

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.