AgentReport

0x3d9a…1216

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

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

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

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

$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
    276 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.00276276d 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 276 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams351d ago0xa7152b…918695
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams352d ago0x662949…f497fd
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams352d ago0x9c037d…f20df6
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams352d ago0x1ffd48…478d3a
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams352d ago0x65a7d9…377fdc
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams352d ago0x059f4a…b3cdc7
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams352d ago0xe85903…df5675
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams352d ago0x925676…c7620d
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams353d ago0x1466f0…591c97
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams353d ago0xf8073e…122661
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams353d ago0x025264…08ca89
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams353d ago0xae59c5…6a1fe2
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams353d ago0xeffd2d…9289cd
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams353d ago0x7532d3…3fdb3e
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams354d ago0x90e50e…6d5c3a
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams354d ago0xa7f557…a10844
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams355d ago0xda591b…a580ff
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams355d ago0x560f86…629a7c
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams355d ago0xbff240…5cbdd2
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams355d ago0x763b76…dce72f
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams355d ago0x0a53ce…7e9db0
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams356d ago0x12dd45…68b7c1
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams356d ago0x40fe30…304b69
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams356d ago0xd82f99…9e9580
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams357d ago0xc185b6…f15f64

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

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

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: 0x3d9a…1216

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