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.00M Roundhouse has indexed across 1,400,982 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 38d 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.0065538d 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%fluxa65d ago0xfe1d83…17f159
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa65d ago0x277297…ad309b
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa65d ago0xc1c955…1dfa6e
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa65d ago0xe48af2…88a567
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa65d ago0x2cff63…089864
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa65d ago0xe944f3…7dd9b6
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa65d ago0x3d8619…51a652
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa65d ago0xa743a2…54a61d
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa65d ago0xec426b…da109a
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa65d ago0xeb7197…073779
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x9c6b07…e01073
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x7f83fb…6b0237
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x52747a…93311f
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x40c143…a440a4
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x6cf0e7…34f654
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x377785…bb4534
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x22f1b7…f7e2ae
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x26fcfc…9ca8f3
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x0fdeef…eb088b
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x3d9b4d…a64a54
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0xde1753…230d01
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0xbe9613…2265c6
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0xa8e821…633039
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x218d99…1ae37f
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x25d295…ddf122

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.