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%daydreams344d ago0x930009…d21d9c
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams344d ago0xa84892…788dc5
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams344d ago0xae776d…7d32b1
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams344d ago0xea5a1f…90bd9a
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams344d ago0x00a80e…9a02f5
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams344d ago0x76ccd5…04198c
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams344d ago0x9851ae…a51938
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0x54dae8…2718d4
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0x891199…d015f0
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0xf80bc9…3a1d89
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0x1ef7f4…9044d1
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0x7bc1a7…1f713c
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0xcbb2fc…7d8ae1
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0x6991d7…e27e60
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0x371aa1…8cb9ff
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0x0360ad…a183de
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0xe56abf…a9bf1e
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0x757ae7…29f047
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams345d ago0x49d72e…450d1c
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams346d ago0x713455…f2f089
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams346d ago0x56ad79…d4274e
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams346d ago0x5ea469…cb65d8
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams346d ago0x08029d…ff6ae4
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams346d ago0x7320af…d67ada
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams346d ago0x678745…896334

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.