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%daydreams349d ago0x5c2c9c…c522b4
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams349d ago0xdd69f2…c39b9c
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams350d ago0x4b8f06…ca12a0
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams350d ago0x16b8fe…1afeac
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams350d ago0x29018e…c1ede5
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams350d ago0x8bb679…1faa6a
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams350d ago0x4c4c33…3617f6
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams351d ago0xdfef3f…334686
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams351d ago0xd57e32…04901b
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams351d ago0x8747ca…a95c66
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams351d ago0x534f3a…6c63c9
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams351d ago0x55bfc8…2fc3b8
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams351d ago0x6d07d1…bd0079
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams351d ago0x45a671…1a2763
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams352d ago0xe2a192…1bb53c
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams352d ago0x2ef300…080e33
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams352d ago0x78d319…13f324
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams352d ago0x58c8d0…0531ae
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams352d ago0x0969a2…e6d9f1
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams352d ago0x2fce51…e683c7
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams352d ago0x927165…8253d3
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams353d ago0xc85632…34473b
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams353d ago0x3e9415…d6d010
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams353d ago0x7279a0…fb23d8
0x73df…af310x6482…b779BaseBase$0.0001100%daydreams353d ago0x281bbf…476932

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.