AgentReport

0x9a8f…16e3

0x9a8fd2b186ad5c5f4a88cac4e0f2f890bac016e3Explorer
Paid out
$34.73
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
22414
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $34.73 of the $847.23M Roundhouse has indexed across 1,330,946 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.521,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 22,414 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.06$0.00854256d agoGraph
0x8324…fd0e$1.46$0.00146269d agoGraph

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

Data quality

59% 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
0x9a8f…16e30x0495…eed9Base$0.10100%payAI256d ago0xd541f9…e58c6e
0x9a8f…16e30x0495…eed9Base$0.10100%payAI256d ago0xb9a138…cae994
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI269d ago0xc21901…188e93
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI269d ago0xb661a3…cda5c1
0x9a8f…16e30x8324…fd0eBase$0.01100%payAI269d ago0xf6bea9…80b68f
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI269d ago0x51db30…f8feac
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI269d ago0x2bdb09…e17593
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI269d ago0x711390…94c969
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI269d ago0xb1d560…3dcf6f
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI269d ago0x48439d…367531
0x9a8f…16e30x8324…fd0eBase$0.01100%payAI270d ago0x2ada02…b41481
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI270d ago0x18662a…2b5b82
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI270d ago0x599ff7…58f9b5
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI270d ago0xe1664b…aaf265
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI270d ago0x21b38e…e1f0fd
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI270d ago0xb89450…30daef
0x9a8f…16e30x0495…eed9Base$0.0001100%heurist270d ago0x193889…282044
0x9a8f…16e30x8324…fd0eBase$0.01100%payAI270d ago0xcbb0e6…37d543
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI270d ago0xd4cf60…9b2a42
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI270d ago0x408d6b…fcc503
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI270d ago0xf11527…b71e30
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI270d ago0x860576…77c1eb
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI270d ago0x695bf6…57b52b
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI270d ago0x964dc3…053fda
0x9a8f…16e30x8324…fd0eBase$0.01100%payAI270d ago0x4c040f…6fb392

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

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

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: 0x9a8f…16e3

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