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%fluxa66d ago0x9cc684…a54cf7
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0xf3fdcc…a427d1
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x3e81f0…4452f1
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0xaed29a…a20057
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x5d6aeb…f85321
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0xe85fca…9cb425
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x60565b…c44011
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x0d8705…0a09d5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x235e83…5cb051
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0xe475a9…2c2bcb
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x11709c…3b93e6
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x894125…f4adc5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x55ef64…ed1085
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x777bc4…866d6b
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x57cef0…f793ff
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x57970c…dd52c5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0xd61870…78eb9a
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0xbd5ce3…aff782
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0xe6e536…7f5c1f
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x8d6d55…a2cea7
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa66d ago0x414527…2c0b86
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0xdf11a3…85d553
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0xe01b4f…b3e1e5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x44820f…3fb0f0
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa67d ago0x349ae3…6dc8ab

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.