AgentReport

0x8a0f…9dd8

0x8a0f40a2c881f2ba01681a5ab75316f0039a9dd8Explorer
Paid out
$3,959.10
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
101
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $3,959.10 of the $3110.54M Roundhouse has indexed across 1,414,059 wallets — 0.0001% of it.

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

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,959.101011

$3,959.10 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.

  • 0x4c1d…acbd · last paid 22d ago
    $3,959.10
    101 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
0x4c1d…acbd$3,959.10$0.0010122d 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 101 observed settlements.

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$20.0070%0x7513…c9a858d ago0x0d6267…613ea6
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$20.0070%0x7513…c9a859d ago0x86320b…b24830
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$12.0170%0x7513…c9a860d ago0xb38428…16fe48
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$75.0070%0x7513…c9a860d ago0xd5dd57…eab19e
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$70.0070%0x7513…c9a862d ago0xdcef9a…5a5b06
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$10.0270%0x7513…c9a863d ago0x9a9577…6c5a54
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$101.4070%0x7513…c9a867d ago0xc6e342…d67f56
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$11.0070%0x7513…c9a867d ago0xcd5a8d…c75bf2
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$106.0070%0x7513…c9a867d ago0xa38511…4111e2
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$90.0070%0x7513…c9a871d ago0x81e269…b919b1
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$10.1070%0x7513…c9a872d ago0x341875…3d332a
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$40.0070%0x7513…c9a873d ago0xd1383d…8b8e8e
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$50.0070%0x7513…c9a873d ago0x7802b5…a350d8
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$10.2070%0x7513…c9a874d ago0x1aa28b…85bf4b
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$19.5070%0x7513…c9a874d ago0xc899ab…8c1ad5
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$10.2070%0x7513…c9a874d ago0xc2387b…6b20f6
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$50.0070%0x7513…c9a874d ago0xcd86b4…f8abb3
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$20.0070%0x7513…c9a875d ago0x75e14a…05030c
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$21.0070%0x7513…c9a875d ago0x0ad06d…d575a5
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$10.0570%0x7513…c9a875d ago0xfa2482…10d48c
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$10.2070%0x7513…c9a875d ago0xaa87a2…c562f9
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$49.0070%0x7513…c9a876d ago0xd9e1cf…16e3c4
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$20.0070%0x7513…c9a876d ago0x4e24de…495636
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$30.0270%0x7513…c9a877d ago0x642a12…f689b3
0x8a0f…9dd80x4c1d…acbdEthereumEthereum$25.0370%0x7513…c9a877d ago0x125bc4…1c440b

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

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

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: 0x8a0f…9dd8

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