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.77M Roundhouse has indexed across 1,332,130 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%virtuals347d ago0x634f80…7fed15
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals347d ago0x704c11…4b2fe9
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0xa210f7…90506a
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x17fcea…0630a2
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x82eaca…e21de8
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0xa30d24…d22a95
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0xa4b5ae…fed99a
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x649db7…d90f81
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x2b3aba…7d7787
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x0fb3d9…aebc7c
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x97ccd4…8e38b0
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0xf676da…8a85a0
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x154372…46d8db
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x737412…39c49c
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0xc53bd3…e024f1
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x2a3134…17758d
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0xc3b373…d23d5a
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x7a4104…f30924
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x69cdb5…b2efe7
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x6a796b…308fb2
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x11dd95…2da9ae
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x5bd480…e3fa9b
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x302c55…361649
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0x05e5d7…5782fc
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals348d ago0xe7bde9…d9f52b

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.