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%daydreams348d ago0x1e082e…564481
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams348d ago0xdfe52d…690477
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams348d ago0xc83167…8fccec
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams348d ago0x2ccd7f…a71e17
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams349d ago0xd5ae26…2e29dd
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams349d ago0x0a7f38…3f3190
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams349d ago0x25ba98…b117b3
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams349d ago0x46005e…50df53
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams349d ago0xf6ff43…9bba83
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams349d ago0xf17fc4…2c5dd1
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams350d ago0x1a97d0…2424a4
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams350d ago0x43e822…a6c7d7
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams350d ago0xb9d192…e16482
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams350d ago0xaf6cdd…0efbde
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams350d ago0xc7582c…778c2b
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams350d ago0x54f38c…3e9794
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams351d ago0x17eb3e…aa7f8a
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams351d ago0x61b3de…c79bfc
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams351d ago0xb32e01…5aa561
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams351d ago0x986fc0…3d283a
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams351d ago0xb182a3…1acad0
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams351d ago0xf322e1…f68d04
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams352d ago0x5a7cc1…0c0df0
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams352d ago0x7a1242…15af50
0xe524…79ad0x6482…b779BaseBase$0.0001100%daydreams352d ago0xd3803d…41defd

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.