AgentReport

0x900a…cc9f

0x900a789a46da8d13784090d749b8172cfeadcc9fExplorer
Paid out
$3,096.00
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
333
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $3,096.00 of the $847.71M Roundhouse has indexed across 1,331,836 wallets — 0.0004% of it.

Chains (from the recent scan): Base (333)

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,096.003331

$3,096.00 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0xef43…6c7f · last paid 322d ago
    $3,096.00
    333 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

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
0xef43…6c7f$3,096.00$0.00333322d 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 all 333 observed settlements.

Organic volume $3,096.00 of $3,096.00 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0x421c65…cfd2f0
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0x168c70…b25f6f
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0xf3dbbb…552aac
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0x46311b…75a0ff
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0x8e67e2…d583e3
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0xa7791c…ae1c1a
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0x1231e5…a832e0
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0xc59463…a52186
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0xafcfd8…806ef1
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0x440f29…a734ca
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0xe754ff…73f8cf
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0x5ae7ee…a707e8
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0xfae1ad…bf1a14
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0x003914…470651
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0xe2f128…a46d6f
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0xfc4674…493f34
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0xd425a6…7091d6
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals346d ago0x426f94…e7a0d8
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals347d ago0x586b5a…13f1cf
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals347d ago0x20e00e…fd346d
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals347d ago0x7ea399…f822dc
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals347d ago0xa90725…d78472
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals347d ago0x5a7bee…ba8525
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals347d ago0xd2ac1c…f56d56
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals347d ago0xfdfcca…a09fc2

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

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

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: 0x900a…cc9f

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