AgentReport

0x9a0a…30f2

0x9a0a8748e6e634eff9e4d96b3905b2b809e630f2Explorer
Paid out
$34.30
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21751
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $34.30 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.761,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,751 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.33$0.00857257d agoGraph
0x8324…fd0e$1.43$0.00143270d 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
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI274d ago0x5a0e68…1cedb0
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI274d ago0x26a745…e32c40
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI274d ago0x241bd0…6614c6
0x9a0a…30f20x8324…fd0eBase$0.01100%payAI274d ago0xba41ed…89b984
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI274d ago0xd02411…51e547
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI274d ago0x7ce6ea…2401a3
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI274d ago0x048cd4…5eae2e
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI274d ago0x787097…53261b
0x9a0a…30f20x8324…fd0eBase$0.01100%payAI274d ago0xa93502…b7eb0b
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI274d ago0xf8e681…ca2240
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI274d ago0x26a85e…d5bbc9
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI274d ago0xcbe4ce…240382
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI275d ago0x6eeeb0…b50767
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI275d ago0x8963ba…9c737d
0x9a0a…30f20x8324…fd0eBase$0.01100%payAI275d ago0x173a25…0865f0
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI275d ago0xcd5ae4…8fb149
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI275d ago0xc391db…a0e40f
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI275d ago0x3c8352…fa25ab
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI275d ago0xb7d9ea…a1db0c
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI275d ago0xd84785…f80fbc
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI275d ago0xa4f692…c0abc7
0x9a0a…30f20x8324…fd0eBase$0.01100%payAI275d ago0xd80d25…8f4489
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI275d ago0x145705…0b0422
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI275d ago0xcf014f…46e9cd
0x9a0a…30f20x0495…eed9Base$0.0001100%payAI275d ago0xece627…b65edb

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

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

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: 0x9a0a…30f2

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