AgentReport

0x0098…cc89

0x009848f50f88a04e4949f09d620c3474e37acc89Explorer
Paid out
$0.84
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
835
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.84 of the $3067.43M Roundhouse has indexed across 1,401,742 wallets — less than 0.0001% of it.

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

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%$0.848352

$0.84 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.

  • 0xfe80…47ee · last paid 39d ago
    $0.66
    655 calls

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

  • 0x9c95…e299 · last paid 77d ago
    $0.18
    180 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

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xfe80…47ee$0.66$0.0065539d agoGraph
0x9c95…e299$0.18$0.0018077d agoGraph

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

Data quality

78% of observed volume is with a single counterparty, in all 835 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x688a7d…ed3e28
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x7e755e…0e09d4
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xcf33ec…cac23e
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xadfe81…dea548
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x28a4a8…405076
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xef016c…61f779
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x4dfa73…3cbd0a
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x2cade9…8f09b6
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xa7f1e7…7e25f5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x4d60f9…6e6eb1
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xc4317c…7719b8
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xd1be9e…ba64a5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x700093…71efe4
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xce92c0…70fc57
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xf36fea…78c127
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xcc7509…57d766
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xf2c571…924fd7
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xf8a629…3140d2
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x768221…16977c
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x846ba9…8189b4
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x096a9a…f2845a
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x12f682…0c3edb
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x213624…19c9a5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x14c429…7c051d
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x0d85ae…be9ac1

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

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

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: 0x0098…cc89

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