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,401,091 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%daydreams343d ago0xfd198a…10cc4b
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams343d ago0x744785…294bde
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams344d ago0xd5a4d5…776d6c
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x3ad1b0…ece73d
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa5301e…4334f0
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x95a316…43880d
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x94a6d0…132955
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x919adf…83c165
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams344d ago0xada7d1…dbe72e
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x96c27f…cceff3
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams344d ago0xfb7446…93a46d
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x707b46…cff39a
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams344d ago0x18e28f…9292a8
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x5b8f09…fdebec
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x014abc…391d68
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x790e01…0ee225
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe9b1b3…126ab3
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe030e5…8113c1
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x75fd39…bc4ebf
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xa81559…47364d
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x3fa2d6…690ab5
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xf42beb…3aa4f6
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0x1320a3…d37232
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xa2b50c…bc959b
0x0991…974a0x6482…b779BaseBase$0.0001100%daydreams345d ago0xbbe0a3…c67c6a

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.