AgentReport

0x9b14…e9e6

0x9b1478d8b0cc7828003f56d6280ed7bf8f04e9e6Explorer
Paid out
$34.29
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21874
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $34.29 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.811,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,874 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.37$0.00856257d agoGraph
0x8324…fd0e$1.44$0.00144270d agoGraph

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

Data quality

62% 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
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x92d97f…e016d8
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x62764e…851a85
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0xf7232e…46bc83
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x8eb332…85d2e6
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0xade882…92b541
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x74afcf…93e407
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x7d3332…58ce20
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x3c0fd6…0ecddd
0x9b14…e9e60x8324…fd0eBase$0.01100%payAI275d ago0x885641…a0c732
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x7866e3…5e4d05
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0xfe77a6…eabc8e
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x603811…0ebd3e
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0xe050c1…82acc2
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x3f7adb…1077d4
0x9b14…e9e60x8324…fd0eBase$0.01100%payAI275d ago0x5f67e8…3bd37f
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0xe463da…53344f
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x34f4ce…68069d
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x01745b…7aa604
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0xc9d006…d1cff7
0x9b14…e9e60x8324…fd0eBase$0.01100%payAI275d ago0x64f50a…ea6491
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0xc9aefe…71ba33
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x3a7e6e…c10f6c
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x044f27…340cfe
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI275d ago0x78396f…416da0
0x9b14…e9e60x8324…fd0eBase$0.01100%payAI275d ago0xf9bfe9…2af754

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

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

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: 0x9b14…e9e6

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