AgentReport

0x9ba3…b0eb

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

Paid $34.29 of the $847.77M Roundhouse has indexed across 1,332,130 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.901,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,389 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.45$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

63% 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
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x601b6a…c4ead0
0x9ba3…b0eb0x8324…fd0eBase$0.01100%payAI275d ago0x67db30…bd8723
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0xb57583…cc0b2d
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0xe6f5d4…b4e751
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0xde7b6a…fd7e3f
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x3d55cf…204dd3
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x195d84…ba90ff
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0xcaa376…e91361
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0xd0082a…090665
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x4e25d5…6be97f
0x9ba3…b0eb0x8324…fd0eBase$0.01100%payAI275d ago0xd3a8a7…ba0a09
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x01e286…709b9d
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x36fa6b…adcc10
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0xc8e24b…bfef2d
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0xe34d42…9401b6
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x4713ab…f6d946
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x8c2924…f7a05c
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x1a3f3d…72deb0
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0xa3d098…560c2e
0x9ba3…b0eb0x8324…fd0eBase$0.01100%payAI275d ago0x5fcb2d…f9bbee
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x98cb83…2c2190
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x214500…0b77e3
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0x92955a…4d0f1e
0x9ba3…b0eb0x0495…eed9Base$0.0001100%payAI275d ago0xe3e6d7…d8a124
0x9ba3…b0eb0x8324…fd0eBase$0.01100%payAI275d ago0xdb2df8…2a770c

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

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

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: 0x9ba3…b0eb

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