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%daydreams343d ago0x5487ab…8eb847
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams343d ago0xb30bf9…9a31fa
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams343d ago0xb52cdb…f7737c
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams343d ago0x3facee…083fe6
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams344d ago0x74ea3b…a645a3
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams344d ago0x2de74b…62130d
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams344d ago0x08fe7a…ecb4e3
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams344d ago0xc4fe8e…2c5036
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams344d ago0xdf47ef…2b63f3
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams344d ago0xb64941…6ab132
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams344d ago0x2f5ec5…e3bb0a
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams344d ago0x61f724…fddfa3
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams344d ago0xc2069c…0bf5a9
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams344d ago0x1cf547…51ff3e
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe250fc…f88ea7
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams345d ago0xcb3f66…4344b8
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams345d ago0x80ba46…d07369
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams345d ago0xed5190…531360
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams345d ago0x815be2…06350b
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams345d ago0x1971f4…e66d82
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams345d ago0x957890…3a62d9
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams345d ago0x759091…28ffd2
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams345d ago0xde8348…8473c0
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams345d ago0x673932…c88080
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams345d ago0xcc5082…e8cecf

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.