AgentReport

0xc9b3…4987

0xc9b3bb7cc6c52cd1cf7c7345d403c70ffe9a4987Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
261
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3070.29M Roundhouse has indexed across 1,403,290 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (261)

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.032611

$0.03 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.

  • 0x6482…b779 · last paid 277d ago
    $0.03
    261 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
0x6482…b779$0.03$0.00261277d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 261 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams352d ago0x74acbf…e6104b
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams352d ago0xcc2065…15e427
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams353d ago0xfe463c…6678f9
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams353d ago0x4fc722…ae2904
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams353d ago0x4e22b4…a9692f
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams353d ago0x240ec1…d47cb6
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams353d ago0xa722d0…f7043e
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams353d ago0x8c6ef0…c23393
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams353d ago0x638695…b3c0a8
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams353d ago0xdb9608…ed71e5
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams353d ago0x2c53ef…900b48
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams353d ago0x160e15…1fb089
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams355d ago0x946ae9…66a825
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams355d ago0x4032a7…009847
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams355d ago0xb974ab…3c19b5
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams355d ago0x4e43e0…e02481
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams356d ago0x94a5fa…6a7b80
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams356d ago0xc77106…b48686
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams356d ago0x2faef1…64e163
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams356d ago0xfbce04…b216a6
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams356d ago0xddd905…4446a8
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams356d ago0x665427…f922ae
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams357d ago0x212664…088832
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams357d ago0x565644…c21994
0xc9b3…49870x6482…b779BaseBase$0.0001100%daydreams357d ago0x84b697…e8bd0e

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 0xc9b3…4987 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0xc9b3bb7cc6c52cd1cf7c7345d403c70ffe9a4987

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: 0xc9b3…4987

curl -s 'https://api.roundhouseai.io/v0/agents/0xc9b3bb7cc6c52cd1cf7c7345d403c70ffe9a4987'
curl -s 'https://api.roundhouseai.io/v0/entities/0xc9b3bb7cc6c52cd1cf7c7345d403c70ffe9a4987/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.