AgentReport

0x9444…5a0d

0x9444d066359f529a836a07c78ebdf6818c6a5a0dExplorer
Paid out
$11.62
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
3298
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $11.62 of the $847.14M Roundhouse has indexed across 1,330,737 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.601,0001

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 1 of 1 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 1,000 most recent settlements of 3,298 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$3.60$0.001,000293d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Organic volume $3.60 of $3.60 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x9444…5a0d0x0495…eed9Base$0.0001100%payAI294d ago0x0e38c0…c574e9
0x9444…5a0d0x0495…eed9Base$0.0001100%payAI294d ago0x53a3a9…dca968
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0x453160…c62f2e
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0x3cd1e3…88828f
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0x620cd7…6da835
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0x3d4a01…c82c2e
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0xe52aef…07f50f
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0xc57250…84ad7b
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0x19b5ad…501bc7
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0xaee23b…8366c9
0x9444…5a0d0x0495…eed9Base$0.0001100%payAI294d ago0x3c12a7…5020ac
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0x13bb84…084050
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0x550ce6…a3a00c
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0xfd318a…36586c
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0x4201a8…1e8f36
0x9444…5a0d0x0495…eed9Base$0.01100%payAI294d ago0x9755c2…81f7d8
0x9444…5a0d0x0495…eed9Base$0.0001100%payAI295d ago0xf80dd9…032814
0x9444…5a0d0x0495…eed9Base$0.0001100%payAI295d ago0x799311…c28e61
0x9444…5a0d0x0495…eed9Base$0.01100%payAI295d ago0x16ab17…32d301
0x9444…5a0d0x0495…eed9Base$0.0001100%payAI295d ago0xc8ecd7…2a92a2
0x9444…5a0d0x0495…eed9Base$0.01100%payAI295d ago0xd593c6…fb073f
0x9444…5a0d0x0495…eed9Base$0.0001100%payAI295d ago0x48b286…eb0e8d
0x9444…5a0d0x0495…eed9Base$0.01100%payAI295d ago0xe71204…5ea667
0x9444…5a0d0x0495…eed9Base$0.0001100%payAI295d ago0x12fa5f…c5cd1c
0x9444…5a0d0x0495…eed9Base$0.0001100%payAI295d ago0x166879…ecee0e

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

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

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: 0x9444…5a0d

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