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,396 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 276d 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.00256276d 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%daydreams326d ago0xc4ff79…2abe44
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams326d ago0xd891f7…c3df48
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams326d ago0x2d57d9…d399ab
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams326d ago0x32e81e…1ef80a
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams326d ago0x406ffb…848788
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams326d ago0x2876f7…9a114c
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams326d ago0xaaa323…4488f9
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams327d ago0x0789ba…8d1d22
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams327d ago0x20c0bc…7b7f12
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams327d ago0x34dfe9…acd730
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams327d ago0xad2fca…6573b3
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams327d ago0xe0a256…5a3c15
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams327d ago0x3eeaf6…ecba92
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams327d ago0x7cd5a1…c12d93
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams327d ago0xdb0a2a…c6b713
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams327d ago0x42bfb0…aa0cce
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams328d ago0x65a220…01bd2c
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams328d ago0x019f89…53c39f
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams328d ago0xd48dd6…75fb61
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams328d ago0x2bbfc6…cce17e
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams336d ago0xc27962…e96e68
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams337d ago0x9d7da0…38c457
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams337d ago0xa7a3e8…5e4972
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams337d ago0xfe3335…c4c114
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams338d ago0x94d63d…3f95c2

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.