AgentReport

0x8931…af49

0x89312009c091fa3242419dece7aa039266f3af49Explorer
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 $3068.58M Roundhouse has indexed across 1,402,563 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 277d 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.00258277d 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
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams353d ago0x771f81…e4636c
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams353d ago0x9de698…387093
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams353d ago0x0fd1d1…44c227
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams353d ago0x152b03…ec5dd1
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams353d ago0x92b77d…9998e6
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams353d ago0x2b67b5…583878
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams353d ago0xbb4922…346c28
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams354d ago0x72d606…3c97a1
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams355d ago0x506570…de8689
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams355d ago0x1ee6f1…d628b9
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams355d ago0x7c475a…ac89c4
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams356d ago0x739dad…d074b3
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams356d ago0xb272c2…961519
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams356d ago0x1bdbfe…53884a
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams356d ago0x07f5a7…ffddd7
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams357d ago0xf8ee67…41c9e7
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams358d ago0x40ee30…90f470
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams358d ago0x371658…d7b0d9
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams358d ago0xff7553…80e58d
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams358d ago0x2b9074…738e1a
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams358d ago0x1df365…c3b9c5
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams359d ago0x118e52…b85dd1
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams359d ago0xe74056…c1956d
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams359d ago0x55bce2…4d568c
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams360d ago0x81c075…e51c78

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

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

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: 0x8931…af49

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