AgentReport

0xe055…939f

0xe0554a476a092703abdb3ef35c80e0d76d32939fExplorer
Paid out
$0.00
Last 7d vs prior 7d
Received
$1,295,321.93↓ 21%
Last 7d vs prior 7d
Settlements
2753↓ 3.9%
Last 7d vs prior 7d
25
Distinct counterparties
Over the whole indexed history

Paid $0.00 of the $3060.46M Roundhouse has indexed across 1,398,118 wallets.

Chains (from the recent scan): Ethereum (1000)

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
0xa54d…49f5$0.00$253,435.74740100d agoGraph
0x2fc6…befe$0.00$234,007.662172h agoGraph
0xa9ac…deae$0.00$25,000.00133d agoGraph
0x3be9…575c$0.00$20,719.95213d agoGraph
0x80cc…c82d$0.00$5,057.14144d agoGraph
0x805a…7c81$0.00$5,000.00149d agoGraph
0x6c22…da50$0.00$2,814.08142d agoGraph
0x67fc…3a0b$0.00$2,000.43110d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

Not enough of this address's history was examined to assess it: self_dealing and counterparty_concentration and single_counterparty were computed over the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap), so nothing found there rules anything out. This is an incomplete check, not a clean record.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa54d…49f50xe055…939fEthereumEthereum$148.1720%Payer-submitted101d ago0x36706e…610dda
0xa54d…49f50xe055…939fEthereumEthereum$64.1620%Payer-submitted101d ago0x4979ad…34e3bb
0xa54d…49f50xe055…939fEthereumEthereum$784.9720%Payer-submitted101d ago0x06da3a…0b9055
0xa54d…49f50xe055…939fEthereumEthereum$562.9920%Payer-submitted101d ago0x08c62e…86dd10
0xa54d…49f50xe055…939fEthereumEthereum$1,197.0920%Payer-submitted101d ago0x1af234…cda8d5
0xa54d…49f50xe055…939fEthereumEthereum$98.7850%Payer-submitted101d ago0xc6b877…2851fc
0xa54d…49f50xe055…939fEthereumEthereum$155.7250%Payer-submitted101d ago0x9a25a0…976a9c
0xa54d…49f50xe055…939fEthereumEthereum$98.9950%Payer-submitted101d ago0x90d63e…305f89
0xa54d…49f50xe055…939fEthereumEthereum$98.9120%Payer-submitted101d ago0xa9ff25…11a656
0xa54d…49f50xe055…939fEthereumEthereum$99.7820%Payer-submitted101d ago0xdbded1…0b6580
0xa54d…49f50xe055…939fEthereumEthereum$99.7120%Payer-submitted101d ago0x0a017f…2f0726
0xa54d…49f50xe055…939fEthereumEthereum$198.2420%Payer-submitted101d ago0xc0113a…aca23e
0xa54d…49f50xe055…939fEthereumEthereum$72.3420%Payer-submitted101d ago0xe28ed1…674ad2
0xa54d…49f50xe055…939fEthereumEthereum$162.2420%Payer-submitted101d ago0xd9d311…67edc7
0xa54d…49f50xe055…939fEthereumEthereum$1,211.1120%Payer-submitted101d ago0x00871a…a2c5d0
0xa54d…49f50xe055…939fEthereumEthereum$553.7420%Payer-submitted101d ago0xb4b496…2aea49
0xa54d…49f50xe055…939fEthereumEthereum$99.6020%Payer-submitted101d ago0x93be08…3274fc
0xa54d…49f50xe055…939fEthereumEthereum$441.1320%Payer-submitted101d ago0xbb1c9f…91e3c3
0xa54d…49f50xe055…939fEthereumEthereum$48.6120%Payer-submitted101d ago0x409b4c…614460
0xa54d…49f50xe055…939fEthereumEthereum$27.0620%Payer-submitted101d ago0x7eb0f9…e07e1f
0xa54d…49f50xe055…939fEthereumEthereum$262.6120%Payer-submitted101d ago0x13f7a7…69953f
0xa54d…49f50xe055…939fEthereumEthereum$252.3620%Payer-submitted101d ago0xbdc856…66767c
0xa54d…49f50xe055…939fEthereumEthereum$114.0520%Payer-submitted101d ago0xa34a69…f9b2dc
0xa54d…49f50xe055…939fEthereumEthereum$57.4920%Payer-submitted101d ago0x71e78c…f360a0
0xa54d…49f50xe055…939fEthereumEthereum$137.8420%Payer-submitted101d ago0xe67c43…46c02d

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 0xe055…939f has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0xe0554a476a092703abdb3ef35c80e0d76d32939f

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: 0xe055…939f

curl -s 'https://api.roundhouseai.io/v0/agents/0xe0554a476a092703abdb3ef35c80e0d76d32939f'
curl -s 'https://api.roundhouseai.io/v0/entities/0xe0554a476a092703abdb3ef35c80e0d76d32939f/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.