AgentReport

aquatic019.eth

0x285fbe8d062a1441b41519f5ce410ad2c1c1c6c1Explorer
Aquatic019.eth
Paid out
$14,899.28↑ 106%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
18↓ 13%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $14,899.28 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — 0.0005% of it.

Whole-history totals from the index rollup, which can be up to 30 minutes behind.

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

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%$14,899.28181

$14,899.28 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.

  • 0xb1c6…3924 · last paid 3d ago
    $14,899.28
    18 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
0xb1c6…3924$14,899.28$0.00183d 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 18 observed settlements.

Organic volume $14,899.28 of $14,899.28 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
aquatic019.eth0xb1c6…3924EthereumEthereum$12.5970%0xb1c6…39243d ago0x993b6d…6a32da
aquatic019.eth0xb1c6…3924EthereumEthereum$3,062.9770%0xb1c6…39243d ago0x447a81…1e7050
aquatic019.eth0xb1c6…3924EthereumEthereum$22.2470%0xb1c6…39243d ago0x7c2e9e…6ad978
aquatic019.eth0xb1c6…3924EthereumEthereum$6,001.1770%0xb1c6…39243d ago0x16e8bb…0292f1
aquatic019.eth0xb1c6…3924EthereumEthereum$143.9270%0xb1c6…39244d ago0xec1eb3…5662bb
aquatic019.eth0xb1c6…3924EthereumEthereum$90.1970%0xb1c6…39244d ago0x3b6fed…500c61
aquatic019.eth0xb1c6…3924EthereumEthereum$13.6970%0xb1c6…39246d ago0x29bafc…c036c5
aquatic019.eth0xb1c6…3924EthereumEthereum$18.1070%0xb1c6…39248d ago0xb16985…c857b1
aquatic019.eth0xb1c6…3924EthereumEthereum$11.2970%0xb1c6…39248d ago0x559df5…33624e
aquatic019.eth0xb1c6…3924EthereumEthereum$11.1170%0xb1c6…39248d ago0x856100…d6a2bd
aquatic019.eth0xb1c6…3924EthereumEthereum$229.7670%0xb1c6…39248d ago0x9ae3e8…e25976
aquatic019.eth0xb1c6…3924EthereumEthereum$382.5470%0xb1c6…392410d ago0x55113b…1d0f6e
aquatic019.eth0xb1c6…3924EthereumEthereum$2,533.0570%0xb1c6…392411d ago0xb3ffe5…631902
aquatic019.eth0xb1c6…3924EthereumEthereum$1,050.2470%0xb1c6…392411d ago0xd9df22…4a70b8
aquatic019.eth0xb1c6…3924EthereumEthereum$310.0070%0xb1c6…392411d ago0x250ee0…fe026a
aquatic019.eth0xb1c6…3924EthereumEthereum$2.0870%0xb1c6…392414d ago0xe5d84a…90ec2a
aquatic019.eth0xb1c6…3924EthereumEthereum$999.1270%0xb1c6…392416d ago0xfc3660…05cc3e
aquatic019.eth0xb1c6…3924EthereumEthereum$5.2170%0xb1c6…392416d ago0xdb3c74…af2d65

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 aquatic019.eth has actually paid for over the free read API. No key, no account.

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

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: aquatic019.eth

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