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 $3069.68M Roundhouse has indexed across 1,403,034 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%daydreams346d ago0xf0fd8a…b7ef2f
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams346d ago0xb0d497…54c192
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams346d ago0x12742f…299047
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams346d ago0xcf632f…a33369
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams346d ago0x66081f…a14c48
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams347d ago0x4a6e60…4f4642
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams347d ago0xbe3f62…25fd75
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams347d ago0x8526be…f03ab3
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams347d ago0x0f488b…7268ed
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams347d ago0x4d449b…9a9316
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams347d ago0x66e245…3169e1
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams347d ago0x96de9f…910e29
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams348d ago0x7258bd…52a80e
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams348d ago0xed7d1f…72a390
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams348d ago0xcbffe4…5d23d9
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams348d ago0x1fede4…16c476
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams348d ago0xc6e2fa…eee9b0
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams348d ago0xedc233…c2c6dd
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams348d ago0x0fbbe2…6620f6
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams348d ago0xe1b717…7a57c9
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams348d ago0xc9b664…7dcc2e
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams348d ago0x4ff7e5…6779c7
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams349d ago0xd9bb0e…3b3fa6
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams349d ago0x52efe5…a5faf6
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams349d ago0x81382c…f804ed

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.