AgentReport

0xae84…499c

0xae84d345ee275e6941041156a04729267245499cExplorer
Paid out
$42,479.57↓ 100%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
143↓ 100%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $42,479.57 of the $3067.84M Roundhouse has indexed across 1,402,228 wallets — 0.0014% of it.

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

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%$42,479.571431

$42,479.57 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.

  • 0x7dbb…59e0 · last paid 7d ago
    $42,479.57
    143 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
0x7dbb…59e0$42,479.57$0.001437d 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 143 observed settlements.

Organic volume $42,479.57 of $42,479.57 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xae84…499c0x7dbb…59e0EthereumEthereum$59.4270%0x323a…a4f294d ago0x908af7…343be9
0xae84…499c0x7dbb…59e0EthereumEthereum$248.7770%0x323a…a4f297d ago0x80a74f…4a1805
0xae84…499c0x7dbb…59e0EthereumEthereum$38.2670%0x323a…a4f299d ago0x64891f…afaa79
0xae84…499c0x7dbb…59e0EthereumEthereum$84.3970%0x323a…a4f2100d ago0x9e1818…fc5765
0xae84…499c0x7dbb…59e0EthereumEthereum$1,014.2470%0x323a…a4f2104d ago0x931581…01196a
0xae84…499c0x7dbb…59e0EthereumEthereum$27.0270%0x323a…a4f2118d ago0x09b53a…e97f81
0xae84…499c0x7dbb…59e0EthereumEthereum$29.8070%0x323a…a4f2139d ago0xd1e5a3…f14117
0xae84…499c0x7dbb…59e0EthereumEthereum$26.7270%0x323a…a4f2142d ago0xaa9f83…425b7c
0xae84…499c0x7dbb…59e0EthereumEthereum$845.0670%0x323a…a4f2145d ago0x43c50d…eee716
0xae84…499c0x7dbb…59e0EthereumEthereum$20.7670%0x323a…a4f2152d ago0xfdc743…2bf66f
0xae84…499c0x7dbb…59e0EthereumEthereum$58.7670%0x323a…a4f2181d ago0xf5c3ba…7c8b0d
0xae84…499c0x7dbb…59e0EthereumEthereum$17.3870%0x323a…a4f2182d ago0xc5afc1…9e4d7c
0xae84…499c0x7dbb…59e0EthereumEthereum$33.9170%0x323a…a4f2184d ago0x88f219…2f4663
0xae84…499c0x7dbb…59e0EthereumEthereum$1,000.0270%0x323a…a4f2188d ago0x980f34…6c5819
0xae84…499c0x7dbb…59e0EthereumEthereum$131.5670%0x323a…a4f2199d ago0x4ae353…0a9a0d
0xae84…499c0x7dbb…59e0EthereumEthereum$57.2070%0x323a…a4f2200d ago0xc7b9b3…4ae8ef
0xae84…499c0x7dbb…59e0EthereumEthereum$460.4550%0x323a…a4f2201d ago0x69b709…56a073
0xae84…499c0x7dbb…59e0EthereumEthereum$38.0070%0x323a…a4f2210d ago0xdef5e7…bae0f1
0xae84…499c0x7dbb…59e0EthereumEthereum$1,450.0070%0x323a…a4f2210d ago0xebacaa…cf5e89
0xae84…499c0x7dbb…59e0EthereumEthereum$2,169.0070%0x323a…a4f2211d ago0x0bad2b…993776
0xae84…499c0x7dbb…59e0EthereumEthereum$374.4570%0x323a…a4f2215d ago0x3bc91f…55e8b3
0xae84…499c0x7dbb…59e0EthereumEthereum$581.7970%0x323a…a4f2216d ago0x33da4f…facad0
0xae84…499c0x7dbb…59e0EthereumEthereum$256.5850%0x323a…a4f2220d ago0xb0a865…ffb647
0xae84…499c0x7dbb…59e0EthereumEthereum$30.4270%0x323a…a4f2223d ago0x54e9b8…dd8b0c
0xae84…499c0x7dbb…59e0EthereumEthereum$74.4370%0x323a…a4f2226d ago0x3669d9…e2f5a1

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

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

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: 0xae84…499c

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