AgentReport

0xaae4…e535

0xaae4e6f1fc0fd8fb21f33b6bb3d2603c1081e535Explorer
Paid out
$934.50
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
72
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $934.50 of the $3064.22M Roundhouse has indexed across 1,399,483 wallets — less than 0.0001% of it.

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

Chains (from the recent scan): Base (72)

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%$934.50722

$934.50 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.

  • 0x47c5…4fc3 · last paid 44d ago
    $469.35
    39 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x0e3d…7757 · last paid 78d ago
    $465.15
    33 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
0x47c5…4fc3$469.35$0.003944d agoGraph
0x0e3d…7757$465.15$0.003378d agoGraph

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

Data quality

50% of observed volume is with a single counterparty, in all 72 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xaae4…e5350x47c5…4fc3BaseBase$17.8570%0x9ea2…605a44d ago0xb55e30…1ca45c
0xaae4…e5350x47c5…4fc3BaseBase$19.9570%0x9307…e92a44d ago0x969b5a…8954e0
0xaae4…e5350x47c5…4fc3BaseBase$13.6570%0x1f7e…db9644d ago0xbe33d0…9af0bd
0xaae4…e5350x47c5…4fc3BaseBase$12.6070%0x8494…2e4444d ago0xa10933…569386
0xaae4…e5350x47c5…4fc3BaseBase$19.9570%0x8100…1de567d ago0xc6036f…1a1ef4
0xaae4…e5350x47c5…4fc3BaseBase$18.9070%0x817a…63b567d ago0x661368…b4f9e9
0xaae4…e5350x47c5…4fc3BaseBase$15.7570%0xa0c6…2cb469d ago0x884227…e74810
0xaae4…e5350x47c5…4fc3BaseBase$10.5070%0xd50e…07b969d ago0x4548a6…7d9b88
0xaae4…e5350x47c5…4fc3BaseBase$10.5070%0x8107…169970d ago0x62cccc…b1f9f9
0xaae4…e5350x47c5…4fc3BaseBase$10.5070%0x9510…bc1270d ago0x1cb964…cf8edd
0xaae4…e5350x47c5…4fc3BaseBase$16.8070%0x0881…8de270d ago0x209d89…bd0e06
0xaae4…e5350x47c5…4fc3BaseBase$15.7570%0x811a…c8aa71d ago0xafaddd…fb424f
0xaae4…e5350x47c5…4fc3BaseBase$10.5070%0x1bc6…2f9071d ago0xd21f9f…ac566d
0xaae4…e5350x47c5…4fc3BaseBase$10.5070%0x160a…c89171d ago0xb4a07b…acf8e6
0xaae4…e5350x47c5…4fc3BaseBase$11.5570%0x9ee1…38b071d ago0x6ff77c…a1ba24
0xaae4…e5350x47c5…4fc3BaseBase$12.6070%0x55b3…f1a071d ago0x0b3440…2cde3d
0xaae4…e5350x47c5…4fc3BaseBase$12.6070%0x4a3c…710272d ago0x97b10c…c24fc9
0xaae4…e5350x47c5…4fc3BaseBase$10.5070%0xc86d…b47f72d ago0xdd9ce8…41dd85
0xaae4…e5350x47c5…4fc3BaseBase$10.5070%0x0b7e…f08e72d ago0xdf9e2c…3bc5ac
0xaae4…e5350x47c5…4fc3BaseBase$11.5570%0x0156…b0f573d ago0x3f1590…9c5437
0xaae4…e5350x47c5…4fc3BaseBase$10.5070%0x59e8…d82373d ago0x8c8453…5d4fe1
0xaae4…e5350x47c5…4fc3BaseBase$8.4070%0x4ec9…366173d ago0xdd3f0a…59adb2
0xaae4…e5350x47c5…4fc3BaseBase$10.5070%0x54b0…438474d ago0xcbea67…cf097d
0xaae4…e5350x47c5…4fc3BaseBase$9.4570%0x850e…501774d ago0x26f4f6…b4cbf6
0xaae4…e5350x47c5…4fc3BaseBase$10.5070%0x2837…f76774d ago0xb6d183…1d8ea4

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

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

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: 0xaae4…e535

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