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,401,091 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%fluxa67d ago0x3e5fb6…030135
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0xd36e0e…92372b
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x7321e9…cd16e5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0xee3463…59ac68
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x935dbe…bfb5c9
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x59d805…42233c
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0xfdd8e8…3daeb0
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x176416…8f24ad
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x7b3176…58b641
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0xf274dc…467177
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x05c4cf…318937
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x784621…0f8704
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x5e5aff…d5c305
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x988100…25cdf2
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0xdfc7a6…a6d9c5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0xe691ac…caaf61
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x4fda07…763eb1
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x77341b…091dc7
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0xb5b9cd…c52c66
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x6cad55…9d4d34
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x443a1c…b1df9c
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0xeb2022…c1f23e
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x5cf275…4f94d1
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x7a156d…8bc9fe
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x3406c0…1dd040

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.