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%daydreams342d ago0x85a9e9…1bcb44
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams342d ago0x8d8dff…e0b2b0
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams342d ago0x73d0cd…0da463
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams342d ago0xe8e643…efec25
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams342d ago0x841900…f81f6f
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams342d ago0xd481de…c44596
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams342d ago0xc6bf4b…a5d73d
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams342d ago0xaf8a1b…dd108f
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams342d ago0x315c6c…781767
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams342d ago0x3688f2…943b43
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams342d ago0x6635f0…977367
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams343d ago0x26e9c8…9320f2
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams343d ago0x39702d…f9b0f9
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams343d ago0x748e66…7f1524
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams343d ago0x8dd484…2af253
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams343d ago0x5baa43…f65c24
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams343d ago0x3c484f…275620
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams343d ago0x1554c4…73bf02
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams343d ago0xa21a21…62ab5e
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams343d ago0xbf68c0…0f2269
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams343d ago0xf21ad9…75ece1
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams343d ago0xd85c77…b7eaf1
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams344d ago0xf237db…eb36e0
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams344d ago0x06266f…15ca54
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams344d ago0x6af697…cc6e64

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.