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,397,991 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
0x2fc6…befe0xe055…939fEthereumEthereum$1,760.4770%0x6351…0d6248d ago0xd1171f…fe32e1
0x2fc6…befe0xe055…939fEthereumEthereum$5,523.3470%0x6351…0d6248d ago0x832794…03585f
0x2fc6…befe0xe055…939fEthereumEthereum$647.4670%0x6351…0d6248d ago0x46f118…17b322
0x805a…7c810xe055…939fEthereumEthereum$5,000.0070%0x07ae…0e6749d ago0xaf6ae6…86be90
0x2fc6…befe0xe055…939fEthereumEthereum$675.1270%0x6351…0d6251d ago0xb561fa…1595d1
0x2fc6…befe0xe055…939fEthereumEthereum$65.4370%0x6351…0d6251d ago0x00d621…ab109c
0x2d18…be6d0xe055…939fEthereumEthereum$0.0870%0xf1d1…d41071d ago0xa5174e…f557c8
0x2d18…be6d0xe055…939fEthereumEthereum$0.1370%0x6639…1aa478d ago0x585606…c4640b
0x38bf…51ff0xe055…939fEthereumEthereum$2.0020%Payer-submitted89d ago0x9d917a…8c08c3
0xee55…51260xe055…939fEthereumEthereum$30.0020%Payer-submitted90d ago0x696fc9…e52003
0xa54d…49f50xe055…939fEthereumEthereum$183.8150%Payer-submitted100d ago0x5fce67…8c41b5
0xa54d…49f50xe055…939fEthereumEthereum$172.2450%Payer-submitted100d ago0x261cc5…30f728
0xa54d…49f50xe055…939fEthereumEthereum$679.3950%Payer-submitted100d ago0x29554b…32d6e6
0xa54d…49f50xe055…939fEthereumEthereum$192.8820%Payer-submitted100d ago0x5647ec…5fff3c
0xa54d…49f50xe055…939fEthereumEthereum$227.4720%Payer-submitted100d ago0x310018…6e8353
0xa54d…49f50xe055…939fEthereumEthereum$84.0520%Payer-submitted100d ago0xee1a21…215fb5
0xa54d…49f50xe055…939fEthereumEthereum$95.9320%Payer-submitted101d ago0x4c0f76…ed80fc
0xa54d…49f50xe055…939fEthereumEthereum$248.6420%Payer-submitted101d ago0x6ae870…32bceb
0xa54d…49f50xe055…939fEthereumEthereum$1,470.4220%Payer-submitted101d ago0xd0501b…edd969
0xa54d…49f50xe055…939fEthereumEthereum$1,499.8620%Payer-submitted101d ago0x1566f3…84a729
0xa54d…49f50xe055…939fEthereumEthereum$3.0320%Payer-submitted101d ago0xb7ca97…6ab156
0xa54d…49f50xe055…939fEthereumEthereum$605.5420%Payer-submitted101d ago0x966d80…8694dd
0xa54d…49f50xe055…939fEthereumEthereum$1,112.3620%Payer-submitted101d ago0x9c4ae1…b4721d
0xa54d…49f50xe055…939fEthereumEthereum$1.5720%Payer-submitted101d ago0x14061d…e48f53
0xa54d…49f50xe055…939fEthereumEthereum$175.9620%Payer-submitted101d ago0xe334fb…31f6af

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.