AgentReport

0xa760…5d0e

0xa760ae5ae39a25915a654b50fbffaaf0ca595d0eExplorer
Paid out
$48,548.52
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
226
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $48,548.52 of the $3063.39M Roundhouse has indexed across 1,398,970 wallets — 0.0016% of it.

Chains (from the recent scan): Ethereum (225) · Base (1)

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%$48,548.522261

$48,548.52 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 5d ago
    $48,548.52
    226 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$48,548.52$0.002265d 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 226 observed settlements.

Organic volume $48,548.52 of $48,548.52 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa760…5d0e0x7dbb…59e0EthereumEthereum$44.6870%0x323a…a4f2283d ago0x7478bc…67c5cf
0xa760…5d0e0x7dbb…59e0EthereumEthereum$63.5870%0x323a…a4f2283d ago0x01d179…af4f3b
0xa760…5d0e0x7dbb…59e0EthereumEthereum$83.3570%0x323a…a4f2286d ago0x0d1834…1b3dd7
0xa760…5d0e0x7dbb…59e0EthereumEthereum$20.3770%0x323a…a4f2287d ago0x4e0de8…f68ac6
0xa760…5d0e0x7dbb…59e0EthereumEthereum$84.6770%0x323a…a4f2287d ago0xf508ee…c08593
0xa760…5d0e0x7dbb…59e0EthereumEthereum$27.6070%0x323a…a4f2288d ago0xfa47b0…30f559
0xa760…5d0e0x7dbb…59e0EthereumEthereum$6.1770%0x323a…a4f2288d ago0x1eff1b…751fe9
0xa760…5d0e0x7dbb…59e0EthereumEthereum$4.4170%0x323a…a4f2288d ago0x55f859…55eb05
0xa760…5d0e0x7dbb…59e0EthereumEthereum$129.8570%0x323a…a4f2288d ago0xd50be5…89b72f
0xa760…5d0e0x7dbb…59e0EthereumEthereum$33.6470%0x323a…a4f2291d ago0x3c46ba…0ad6a2
0xa760…5d0e0x7dbb…59e0EthereumEthereum$73.9570%0x323a…a4f2293d ago0x1cf181…9f9a11
0xa760…5d0e0x7dbb…59e0EthereumEthereum$19.7970%0x323a…a4f2295d ago0x48818b…e69ae3
0xa760…5d0e0x7dbb…59e0EthereumEthereum$21.5670%0x323a…a4f2295d ago0x13553d…2453df
0xa760…5d0e0x7dbb…59e0EthereumEthereum$36.2770%0x323a…a4f2296d ago0x22733a…8bda59
0xa760…5d0e0x7dbb…59e0EthereumEthereum$59.7970%0x323a…a4f2298d ago0x777cd8…37ba8d
0xa760…5d0e0x7dbb…59e0EthereumEthereum$72.0570%0x323a…a4f2298d ago0xf12400…b15479
0xa760…5d0e0x7dbb…59e0EthereumEthereum$48.9270%0x323a…a4f2300d ago0x29815d…f29093
0xa760…5d0e0x7dbb…59e0EthereumEthereum$43.8570%0x323a…a4f2300d ago0xc1a8a0…5b0f37
0xa760…5d0e0x7dbb…59e0EthereumEthereum$6.7070%0x323a…a4f2300d ago0xce4f1b…143cb1
0xa760…5d0e0x7dbb…59e0EthereumEthereum$22.8170%0x323a…a4f2300d ago0x1cf3f1…fcaa0c
0xa760…5d0e0x7dbb…59e0EthereumEthereum$24.3870%0x323a…a4f2303d ago0x1d5584…4a8c9b
0xa760…5d0e0x7dbb…59e0EthereumEthereum$72.1570%0x323a…a4f2305d ago0x4b871d…3c220f
0xa760…5d0e0x7dbb…59e0EthereumEthereum$53.4370%0x323a…a4f2305d ago0x29fd3b…ff4e57
0xa760…5d0e0x7dbb…59e0EthereumEthereum$75.2370%0x323a…a4f2308d ago0x8fa71f…cb9c86
0xa760…5d0e0x7dbb…59e0EthereumEthereum$360.5270%0x323a…a4f2310d ago0xa39d48…3a9942

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

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

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: 0xa760…5d0e

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