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%daydreams325d ago0x2cd9c9…0a8b04
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x8f4799…a8c75b
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x7ef748…c8b9f7
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x2654e9…a35959
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x92e5a7…24f694
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x626e11…93e970
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x3d3d47…9057ad
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams326d ago0xbaf8c8…ab229c
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams326d ago0xd470a1…01d5e5
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x5577bd…33aed4
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xa97e47…c86d25
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xb8715b…addcd0
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams327d ago0x7c474b…696077
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams327d ago0x1b91e4…ae9f78
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xd9821f…9c5b0e
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams327d ago0x46f0ac…58b30c
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xb1b3ef…91752d
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xc98cc7…6e86ef
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams328d ago0x01b221…abebe1
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams328d ago0x126cf9…63c5a8
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams328d ago0x2cb2aa…0a2192
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams335d ago0xd2151d…cafaae
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams337d ago0x8641b0…df375b
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams337d ago0x070b07…219e64
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams337d ago0x0ab99d…d65178

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.