AgentReport

0xae18…4d1c

0xae18ac6baa121457e3bd92908b2b1378f8a34d1cExplorer
Paid out
$3,300.07↑ 166%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
87↑ 120%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $3,300.07 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — 0.0001% of it.

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

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%$3,300.07871

$3,300.07 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 2d ago
    $3,300.07
    87 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$3,300.07$0.00872d 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 87 observed settlements.

Organic volume $3,300.07 of $3,300.07 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xae18…4d1c0x7dbb…59e0EthereumEthereum$4.0870%0x323a…a4f249d ago0xd7c90e…e38d71
0xae18…4d1c0x7dbb…59e0EthereumEthereum$143.1270%0x323a…a4f251d ago0x6bcfa6…eeaaca
0xae18…4d1c0x7dbb…59e0EthereumEthereum$3.8270%0x323a…a4f251d ago0x3bca4b…bf71de
0xae18…4d1c0x7dbb…59e0EthereumEthereum$19.7870%0x323a…a4f252d ago0xc2335d…d53527
0xae18…4d1c0x7dbb…59e0EthereumEthereum$98.7270%0x323a…a4f253d ago0x2e257c…5dced5
0xae18…4d1c0x7dbb…59e0EthereumEthereum$65.2270%0x323a…a4f257d ago0x388cf4…af7f39
0xae18…4d1c0x7dbb…59e0EthereumEthereum$16.5570%0x323a…a4f258d ago0x59e4a9…816b70
0xae18…4d1c0x7dbb…59e0EthereumEthereum$43.2970%0x323a…a4f259d ago0xa1e19c…b50f88
0xae18…4d1c0x7dbb…59e0EthereumEthereum$30.8370%0x323a…a4f259d ago0x412a1f…ae14df
0xae18…4d1c0x7dbb…59e0EthereumEthereum$34.5470%0x323a…a4f259d ago0xc09b46…ad1be9
0xae18…4d1c0x7dbb…59e0EthereumEthereum$13.2370%0x323a…a4f260d ago0x7c9455…9110f0
0xae18…4d1c0x7dbb…59e0EthereumEthereum$16.4170%0x323a…a4f260d ago0x22a306…1fb710
0xae18…4d1c0x7dbb…59e0EthereumEthereum$3.9570%0x323a…a4f261d ago0x753867…da903c
0xae18…4d1c0x7dbb…59e0EthereumEthereum$17.2150%0x323a…a4f261d ago0x01d77d…fd5f90
0xae18…4d1c0x7dbb…59e0EthereumEthereum$6.5370%0x323a…a4f261d ago0x6531f3…20b8e5
0xae18…4d1c0x7dbb…59e0EthereumEthereum$11.0970%0x323a…a4f264d ago0x65bf47…9de125
0xae18…4d1c0x7dbb…59e0EthereumEthereum$14.4570%0x323a…a4f265d ago0x4493a7…d718f9
0xae18…4d1c0x7dbb…59e0EthereumEthereum$36.1470%0x323a…a4f266d ago0xe841da…7c888f
0xae18…4d1c0x7dbb…59e0EthereumEthereum$18.8570%0x323a…a4f266d ago0x24e603…934f51
0xae18…4d1c0x7dbb…59e0EthereumEthereum$76.2570%0x323a…a4f267d ago0xff3848…e9dbad
0xae18…4d1c0x7dbb…59e0EthereumEthereum$14.4370%0x323a…a4f270d ago0x111a66…1dcad8
0xae18…4d1c0x7dbb…59e0EthereumEthereum$108.2770%0x323a…a4f273d ago0xec675a…fb4d6d
0xae18…4d1c0x7dbb…59e0EthereumEthereum$26.0770%0x323a…a4f274d ago0xf5d40a…e60349
0xae18…4d1c0x7dbb…59e0EthereumEthereum$24.3970%0x323a…a4f278d ago0x0a2bb8…be0a04
0xae18…4d1c0x7dbb…59e0EthereumEthereum$39.5570%0x323a…a4f280d ago0xc2f9b4…b4d1f9

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

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

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: 0xae18…4d1c

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