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%daydreams352d ago0x84136d…220fae
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams352d ago0xb2f5b2…16ca3b
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams352d ago0xeeb7a4…2ab95d
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams352d ago0xabad68…dc394a
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams352d ago0x978561…2e29f5
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams352d ago0x4c18f4…594524
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams352d ago0x4f0f97…ff8f21
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams353d ago0xd9fc5c…b99262
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams353d ago0x5a6dc6…c47b7c
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams353d ago0xa813a9…ca721f
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams353d ago0x182515…1f1813
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams353d ago0x6d9456…a4a009
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams353d ago0x01da7a…f9915e
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams353d ago0x19f441…f6cee6
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams354d ago0xfc0169…ef346b
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams355d ago0xe1cce2…834b8b
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams355d ago0x4f44f3…7c9f03
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams355d ago0x753eb2…830a90
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams356d ago0x58a872…6cb35f
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams356d ago0x9deb81…9d5475
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams356d ago0x40505c…5494f7
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams357d ago0x0191a8…2da4d4
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams357d ago0xffd49b…83933c
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams357d ago0x1fdb97…7b9c38
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams357d ago0x8c33ad…6e6de6

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.