AgentReport

0xf383…80a9

0xf38374dbcc5da0331514b758fec19b03f41880a9Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
278
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.25M Roundhouse has indexed across 1,401,192 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (278)

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.032781

$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 276d ago
    $0.03
    278 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.00278276d 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 278 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams348d ago0xca09ee…4dd9c8
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams348d ago0x89941a…493f87
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams348d ago0xc32de9…747209
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams348d ago0x480d2f…0f752f
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams348d ago0x904c67…20eb21
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams348d ago0xa82ad7…556019
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams348d ago0x750dbd…58453a
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams348d ago0x7a42bc…24f221
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams348d ago0x8e0aeb…379aad
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams348d ago0xd0e3d5…a29b4c
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams349d ago0xb5b440…8dac42
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams349d ago0x4798dd…d68fee
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams349d ago0x9fc716…8fc942
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams349d ago0x975e52…3b1fcd
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams350d ago0xe50712…d910fb
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams350d ago0xd4d43a…d2c062
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams350d ago0xcbd6a5…561fb5
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams350d ago0x4ef7b2…eec809
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams350d ago0x36820e…0a3a39
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams350d ago0x3a325c…08608b
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams351d ago0x41436b…0df99f
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams351d ago0x93a841…0cd900
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams351d ago0xf3c719…c9bae4
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams351d ago0x231d7b…07d4e3
0xf383…80a90x6482…b779BaseBase$0.0001100%daydreams351d ago0x39a463…34563d

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 0xf383…80a9 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0xf38374dbcc5da0331514b758fec19b03f41880a9

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: 0xf383…80a9

curl -s 'https://api.roundhouseai.io/v0/agents/0xf38374dbcc5da0331514b758fec19b03f41880a9'
curl -s 'https://api.roundhouseai.io/v0/entities/0xf38374dbcc5da0331514b758fec19b03f41880a9/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.