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 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%daydreams341d ago0xe1029e…45d1a1
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams341d ago0xa47c38…f1a4a8
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams341d ago0xe6ea66…70764e
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams341d ago0x499c30…fb99b0
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams341d ago0xa405a5…bd698c
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams341d ago0xfc993f…198035
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams341d ago0x30bcca…91d2ed
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams341d ago0x006a99…4d407e
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams342d ago0x850997…a9b856
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams342d ago0xfa8d24…03c847
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams342d ago0x502487…ad2a3d
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams342d ago0x7d6e7e…facb7a
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams342d ago0x5461bc…8a2ed5
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams342d ago0x008378…65b86c
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams342d ago0xba9a70…59d56b
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams342d ago0x0143bf…a9bf44
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams342d ago0xff45a4…7c1164
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams342d ago0xad5704…bbcbbf
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams343d ago0xe004a2…002f67
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams343d ago0x3e1299…d1a06f
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams343d ago0x5455cf…8c990e
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams343d ago0x2c046a…88372f
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams343d ago0xed7cb0…3fb68f
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams343d ago0x06c70c…9868d3
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams343d ago0x61f18c…6f90c3

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.