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 $846.93M Roundhouse has indexed across 1,330,416 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 321d 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.00333321d 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%virtuals342d ago0x985471…7bc2a4
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals342d ago0x50ad89…1e9891
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals342d ago0x4f354c…3846ed
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals342d ago0x677d75…f9ff20
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals342d ago0x4d5bd9…be4ba4
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals342d ago0x6eeae3…3ff67d
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0xc4b0b2…23d485
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x28c928…1b7ecb
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x33140d…06e6de
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x94c7d3…aa91cc
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x98393b…80c638
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0xa61506…a4a0bc
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0xa3b083…37d742
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x135313…be1ab4
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x8ddadc…5072f5
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x937e28…4e16f5
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x95b6c0…59d32c
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0xb464f0…64eabc
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x670632…e129b5
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x6aa4a2…f0a095
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x6b6b4a…5c7e46
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x6ae985…cdedaa
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0xb46b16…c20c84
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x9cce05…9db4eb
0x900a…cc9f0xef43…6c7fBase$4.00100%virtuals344d ago0x2225a2…0b4139

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.