AgentReport

0x4814…6ddb

0x48147ae6ae9fe1af3753528754a81d6a2def6ddbExplorer
Paid out
$98,625.79↓ 99%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
235↓ 86%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $98,625.79 of the $3060.21M Roundhouse has indexed across 1,397,717 wallets — 0.0032% of it.

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

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%$98,625.792351

$98,625.79 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 6d ago
    $98,625.79
    235 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$98,625.79$0.002356d 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 235 observed settlements.

Organic volume $98,625.79 of $98,625.79 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x4814…6ddb0x7dbb…59e0EthereumEthereum$341.2270%0x323a…a4f254d ago0x3b1f53…9a0c05
0x4814…6ddb0x7dbb…59e0EthereumEthereum$370.3270%0x323a…a4f254d ago0x1057d7…b4f379
0x4814…6ddb0x7dbb…59e0EthereumEthereum$50.0170%0x323a…a4f254d ago0xc2f216…c4fdaa
0x4814…6ddb0x7dbb…59e0EthereumEthereum$28.0770%0x323a…a4f255d ago0xbab98f…42a4c2
0x4814…6ddb0x7dbb…59e0EthereumEthereum$37.8470%0x323a…a4f263d ago0x9568a1…997bbb
0x4814…6ddb0x7dbb…59e0EthereumEthereum$51.9570%0x323a…a4f266d ago0x548f5c…3ee9d0
0x4814…6ddb0x7dbb…59e0EthereumEthereum$27.6270%0x323a…a4f268d ago0xaa3e33…ef651a
0x4814…6ddb0x7dbb…59e0EthereumEthereum$250.0870%0x323a…a4f268d ago0x24193d…415385
0x4814…6ddb0x7dbb…59e0EthereumEthereum$241.0370%0x323a…a4f268d ago0xa3bda7…df93b0
0x4814…6ddb0x7dbb…59e0EthereumEthereum$532.2270%0x323a…a4f268d ago0xde2aa2…4e6c89
0x4814…6ddb0x7dbb…59e0EthereumEthereum$661.1470%0x323a…a4f268d ago0xceba7b…f1ba4f
0x4814…6ddb0x7dbb…59e0EthereumEthereum$212.0370%0x323a…a4f268d ago0x91500d…200f89
0x4814…6ddb0x7dbb…59e0EthereumEthereum$102.0170%0x323a…a4f268d ago0x40e1cd…990946
0x4814…6ddb0x7dbb…59e0EthereumEthereum$335.0870%0x323a…a4f268d ago0x8d6700…7106f6
0x4814…6ddb0x7dbb…59e0EthereumEthereum$400.0670%0x323a…a4f269d ago0xa3731b…afc6dc
0x4814…6ddb0x7dbb…59e0EthereumEthereum$34.8170%0x323a…a4f273d ago0x4e1520…c08d2a
0x4814…6ddb0x7dbb…59e0EthereumEthereum$196.8170%0x323a…a4f285d ago0x3ca693…c2970d
0x4814…6ddb0x7dbb…59e0EthereumEthereum$151.3970%0x323a…a4f285d ago0x54002d…dc4501
0x4814…6ddb0x7dbb…59e0EthereumEthereum$67.0570%0x323a…a4f285d ago0x82ec93…e49641
0x4814…6ddb0x7dbb…59e0EthereumEthereum$3,455.0770%0x323a…a4f287d ago0x19dacc…3c5ac5
0x4814…6ddb0x7dbb…59e0EthereumEthereum$1,020.0970%0x323a…a4f297d ago0xfd1f1e…bac633
0x4814…6ddb0x7dbb…59e0EthereumEthereum$768.7570%0x323a…a4f298d ago0xebee5e…76126d
0x4814…6ddb0x7dbb…59e0EthereumEthereum$132.0350%0x323a…a4f2100d ago0x74a182…2d3b3f
0x4814…6ddb0x7dbb…59e0EthereumEthereum$185.0570%0x323a…a4f2100d ago0x864fd5…f33e3f
0x4814…6ddb0x7dbb…59e0EthereumEthereum$240.0470%0x323a…a4f2100d ago0x97516f…89a6b9

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

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

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: 0x4814…6ddb

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