AgentReport

0x0991…974a

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

Paid $0.03 of the $3067.00M Roundhouse has indexed across 1,400,982 wallets — less than 0.0001% of it.

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

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

$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 276d ago
    $0.03
    258 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.00258276d 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 258 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams323d ago0x2033d1…ec37a0
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams323d ago0x90914d…6aa3f3
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams323d ago0xa3eb1d…e20bfd
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams323d ago0xf604a5…4c04dc
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams323d ago0x313980…4a4dd3
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams324d ago0x6058b5…78ba37
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams324d ago0x4fd732…036cba
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams324d ago0xe3a4ff…cae8f0
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams324d ago0x540150…c03c3d
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams324d ago0xc8ef17…d5eacd
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams324d ago0xcbf66c…7fb06e
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams324d ago0xe8c55d…b69bf4
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams324d ago0x27013b…26222c
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams324d ago0xcdc8ab…ffa21f
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams324d ago0x88b5ee…792792
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams324d ago0x003fe1…6ce74d
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams325d ago0x8cc28c…067d91
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams325d ago0x539938…fe034a
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams325d ago0x3ca448…fbe04d
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams325d ago0xfdaebb…b1f04e
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams325d ago0x7df481…3fde1c
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams325d ago0xaed947…e456d4
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams325d ago0x37d809…1fc141
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams325d ago0x336803…a1a6a2
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams325d ago0xd9b77d…ffbe93

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

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

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: 0x0991…974a

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