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 $848.16M Roundhouse has indexed across 1,333,657 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%payAI277d ago0x39b3dd…0ea286
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0xa9666b…e704f0
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0xc386ab…439349
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0xf6ee29…d5fb28
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0x3b0797…a5ba91
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0x74a2f3…53ac4c
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0x32e8b6…8d5f89
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0x67f76b…6d527c
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0x65609f…0ef02f
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0x0fc5dd…90133f
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0x52b223…975519
0x9b14…e9e60x8324…fd0eBase$0.01100%payAI277d ago0xf2ebe6…859e15
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0x3adb4c…ed63de
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0x3a3a6a…c45782
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI277d ago0x95e3d3…fc5eb0
0x9b14…e9e60x8324…fd0eBase$0.01100%payAI278d ago0x736a49…f60267
0x9b14…e9e60x8324…fd0eBase$0.01100%payAI278d ago0xb2f95f…13d0be
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI278d ago0x96041e…6c1a3b
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI278d ago0xc5ef0a…784fee
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI278d ago0x3536e1…d9751a
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI278d ago0x37266c…4bbceb
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI278d ago0x08ca25…41e3f0
0x9b14…e9e60x8324…fd0eBase$0.01100%payAI278d ago0x0b811c…e2d7fd
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI278d ago0xb22835…45a1d2
0x9b14…e9e60x0495…eed9Base$0.0001100%payAI278d ago0x5fbfdd…2c3d4e

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.