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 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%fluxa68d ago0xcb5cdf…885ba0
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xc9da69…f0d502
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xc278f0…e61cdd
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xccd835…b6b10e
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xc9a364…23d8b9
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xf68415…2b69b4
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x67767e…5c62b2
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x531e98…bd93b1
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xf1ffe4…1ac8b3
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xdfb2bf…3904a7
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x42da2b…570e1c
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xe86889…5ab872
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x94ad18…4156a0
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x6dbf08…c6056b
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x6452e8…5d93fc
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xe706ba…c05413
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x4e8a6f…103983
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x369ce5…3df4dd
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x29c5c5…be1e2c
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xa649a5…3fa60e
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xa40de6…fe32fb
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x27add5…266eb4
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0xd63f90…8c039f
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x144d18…81bb09
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa68d ago0x24b883…13c91f

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.