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%fluxa69d ago0x51b5d2…33f1ce
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0xd47232…7bc5c9
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x16342c…2cf392
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x581de9…8d3256
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x68165c…2ac58c
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x4080cc…630be1
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x9d100e…a1b0e5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0xa39f17…596668
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x7ddebb…7e8819
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x19d52f…96863d
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x437144…39584e
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x4f279a…f91288
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0xde8a57…41cf2f
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0xa91292…1d0f75
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0xfc6c52…5843f8
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0xd8538c…ec93e4
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x2a9462…65eb7d
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x7b8464…536be5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x8682f6…0c78c6
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x115f2d…0b1277
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa69d ago0x0b35df…40c704
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x1cedca…1049c5
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0xe7507d…ac6175
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x24b87d…07338e
0x0098…cc890xfe80…47eeBaseBase$0.001100%fluxa70d ago0x820ddd…857a00

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.