AgentReport

0x9ad0…4e75

0x9ad0da41b0d2b022ececf62fcde8685cb5c94e75Explorer
Paid out
$33.92
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21655
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $33.92 of the $847.73M Roundhouse has indexed across 1,331,971 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (1000)

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.761,0002

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 1,000 most recent settlements of 21,655 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MayJunJulAugSepOct
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x0495…eed9$2.31$0.00855257d agoGraph
0x8324…fd0e$1.45$0.00145270d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

61% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI273d ago0xd9792f…853d9e
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI273d ago0x77cb7a…05e189
0x9ad0…4e750x8324…fd0eBase$0.01100%payAI273d ago0x19df24…eb7e4e
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI273d ago0x568986…ac8b82
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI273d ago0x9545b8…a8bfc1
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI273d ago0xce9f2d…2fcd13
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI273d ago0x936a41…c38f13
0x9ad0…4e750x8324…fd0eBase$0.01100%payAI273d ago0x5c63fd…607208
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI273d ago0x637021…d88f0e
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI273d ago0x9d834c…82a464
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0x558221…0e7a2b
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0xf43c6e…6a8496
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0x76dbdf…33a80a
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0x959e07…1857a8
0x9ad0…4e750x8324…fd0eBase$0.01100%payAI274d ago0x38f8e4…c8e349
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0xe0cf02…5f1562
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0xa7521a…5f5ee0
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0xbd8f20…270afa
0x9ad0…4e750x8324…fd0eBase$0.01100%payAI274d ago0xa0c0d7…248aa2
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0xfab98b…70c419
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0x6b6be7…b29e56
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0x7fa138…5a377b
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0x90932e…ccd215
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0x83f331…fd00f0
0x9ad0…4e750x0495…eed9Base$0.0001100%payAI274d ago0x44fbfa…85751d

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

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

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: 0x9ad0…4e75

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