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%daydreams337d ago0xd94d88…dba64f
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams337d ago0xe72946…ea57ba
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams337d ago0x6ce89f…471f0b
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams338d ago0x99ada3…59b381
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams338d ago0xb85772…4821b3
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams338d ago0xaaa236…dc6b86
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams338d ago0x1ef526…2de84a
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams338d ago0xf20a45…a38afd
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams339d ago0x33556d…295e68
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams339d ago0xb5ff74…62f288
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams339d ago0xd32e0d…867242
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams339d ago0x738219…60a227
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x30e6d7…5b5f61
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe1eda1…2a300a
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xc2067b…8f0cd8
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x742c0f…719fcf
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xbc35df…24f82b
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xff84a7…04be47
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x6770f2…76a3d2
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x3a172a…cec94a
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa8e110…f98836
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams340d ago0xf25561…1fdc33
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams340d ago0x3611af…8764b8
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams341d ago0xdb9c2f…fcfc0b
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams341d ago0xa33c62…8d9839

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.