AgentReport

0x73df…af31

0x73df15576c935d94848759d988c33119fd03af31Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
256
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 (256)

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

$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
    256 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.00256277d 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 256 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams338d ago0xf35ae1…1e8fea
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams338d ago0x3fdf7c…81e007
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams338d ago0x893369…e461cd
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams338d ago0xaa9651…cfc6dc
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams338d ago0xe04e77…310a03
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0xf7b96d…59107b
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0xfa848e…b3679f
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0x51dfbe…b58e0e
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0x9212d0…5f7586
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0x3ac09c…d72ae0
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0x89f6bb…34b99b
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0x1c62ac…47aebb
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0xc1141b…9bf872
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0xda2586…296936
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0xe3c1a9…2d21ab
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0x000fce…3b6737
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams340d ago0x35542a…15cacc
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams341d ago0xb044c6…4d909b
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams341d ago0xde156d…c02246
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams341d ago0x916416…93dd4c
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams341d ago0xcb0dff…3c5fed
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams341d ago0x37e4be…f5582e
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams341d ago0x00ed7d…51222d
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams341d ago0x4c3d1c…502c0c
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams341d ago0x94260d…c4c49c

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

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

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: 0x73df…af31

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