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 $3067.84M Roundhouse has indexed across 1,402,228 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%daydreams323d ago0x3cd2cf…ba3c18
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams323d ago0xd7d7f8…a639aa
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams323d ago0xd9acbe…a471f4
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams323d ago0x1d5bd3…01adb3
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams324d ago0xb4c921…57e112
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams324d ago0xfc8686…d683c1
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams324d ago0xa52001…cba1d7
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams324d ago0xe4afda…04ba0d
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams324d ago0x4e0663…6f7294
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams324d ago0xa1d40f…e2feb0
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams324d ago0x413fca…f121c2
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams324d ago0xf9dac1…c98982
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams324d ago0x7dd430…ce2be4
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams325d ago0x0e2278…612b8a
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams325d ago0xb4aa18…a69e1d
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams325d ago0xcc0f4a…a850fe
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams325d ago0xa6f16c…7f26a9
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams325d ago0xfdbb12…3f9f2f
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams325d ago0xaa7e9d…00256d
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams325d ago0x814408…f74858
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams325d ago0x64ea52…fcf757
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams325d ago0x275be5…091a6c
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams325d ago0xa0a007…22a81c
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams325d ago0x2ac896…04c779
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams326d ago0xcc5efa…88abf3

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.