AgentReport

0x9a72…d5dd

0x9a7266437235f4e1680662ea6e8b6cb2ba98d5ddExplorer
Paid out
$33.80
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21556
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $33.80 of the $846.93M Roundhouse has indexed across 1,330,416 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.431,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,556 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$1.95$0.00852256d agoGraph
0x8324…fd0e$1.48$0.00148269d agoGraph

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

Data quality

57% 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
0x9a72…d5dd0x8324…fd0eBase$0.01100%payAI270d ago0x1f33aa…ac2c5f
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0x85e0fc…54e957
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0x2bb84b…1f6ba8
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0xd9fae9…691bf9
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0xba025b…c9f07b
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0xfd4a92…073526
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0x5bea03…6a912f
0x9a72…d5dd0x8324…fd0eBase$0.01100%payAI270d ago0xffe163…eb78dd
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0x1068b8…36aada
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0x0e4806…a981ba
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0xd8cec1…30d415
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0x606068…74561a
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0xa6597d…c7c2f6
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0x2cb66a…eaae52
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0x3ec06a…6babf3
0x9a72…d5dd0x8324…fd0eBase$0.01100%payAI270d ago0x4e4fbe…57d50f
0x9a72…d5dd0x0495…eed9Base$0.0001100%heurist270d ago0x77a901…320dc5
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0xb36cd7…5af345
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0x6e9f04…773094
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0x638990…a6446b
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0xecb79e…3c451c
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0xb36d2b…975b65
0x9a72…d5dd0x8324…fd0eBase$0.01100%payAI270d ago0xd52d66…27dc19
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI270d ago0x2b1d3e…9c5014
0x9a72…d5dd0x0495…eed9Base$0.0001100%payAI271d ago0xabf758…e4c726

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

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

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: 0x9a72…d5dd

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