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.64M Roundhouse has indexed across 1,331,342 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.0001100%payAI271d ago0xaa78bc…2a7136
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0x144545…3a0046
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0x2760bd…b41ff3
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0xd9d810…9e2dd5
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0xdd85ee…04076a
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0xd684af…46c227
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0x16de7f…c8a4ee
0x9a8f…16e30x8324…fd0eBase$0.01100%payAI272d ago0xe6bd81…516cb9
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0x4c5743…19b214
0x9a8f…16e30x0495…eed9Base$0.0001100%heurist272d ago0x0bd89b…198f07
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0xd6f24e…6812f6
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0x1251d8…898858
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0xd3ae1d…b975f9
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0x6de140…ab9094
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0x60af29…b9764a
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0xa88e53…377a16
0x9a8f…16e30x8324…fd0eBase$0.01100%payAI272d ago0x61e83a…67ce81
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0xae641d…53c0f8
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0xda416a…728379
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0x86dcb5…64db28
0x9a8f…16e30x8324…fd0eBase$0.01100%payAI272d ago0xb83771…23b0dd
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0x9df71a…eb1bdd
0x9a8f…16e30x0495…eed9Base$0.0001100%payAI272d ago0xcbad84…fd4caa
0x9a8f…16e30x0495…eed9Base$0.0001100%heurist272d ago0xc3f362…a270ba
0x9a8f…16e30x8324…fd0eBase$0.01100%payAI272d ago0x86ce6a…433b8a

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.