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 $3070.29M Roundhouse has indexed across 1,403,290 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%daydreams353d ago0xc4c9c0…177117
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams353d ago0x23b57f…29ede6
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams353d ago0x232266…930d53
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams353d ago0xc36656…497c95
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams354d ago0x68ad1c…a3ce2e
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams355d ago0x02f0a6…062e27
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams355d ago0x9e377b…8cc50a
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams356d ago0xac2520…9f213f
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams356d ago0x11d11b…41451a
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams356d ago0x33385c…f3d884
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams357d ago0x456b62…448285
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams357d ago0x0a65a2…8d2cdb
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams357d ago0xd96098…08548d
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams357d ago0x0ad64b…3ed75d
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams358d ago0xab9c3c…a5aead
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams358d ago0x8c8887…ee1539
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams358d ago0xd07e3c…bcdbbc
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams358d ago0x660786…6eccbd
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams359d ago0x500cfa…19269b
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams359d ago0x8da6f3…6f83a2
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams359d ago0x4edf4b…a171a3
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams359d ago0xf73ef6…c3c28f
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams359d ago0xcaf741…999de5
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams359d ago0x3f726a…687f39
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams360d ago0x70a8fc…6a84a4

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.