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.00M Roundhouse has indexed across 1,401,091 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%daydreams325d ago0x2d4c7f…85c40f
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams326d ago0x270474…d631f8
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams326d ago0x11c7e1…b44609
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams326d ago0xd57435…fd2e6a
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams326d ago0x09c4e5…edd757
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams326d ago0x82ceb2…53827d
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams326d ago0x51e6d2…b97b46
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams326d ago0xb4b084…d1afaf
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams326d ago0x63d0a0…a58216
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams326d ago0xdc0f33…507657
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams326d ago0xddff72…ffbf4f
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams327d ago0x6f3c57…02cf69
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams327d ago0x825741…a05213
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams327d ago0x04cd85…fe036c
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams327d ago0x10cc20…5aa97a
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams327d ago0xaafa1d…6ccc9b
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams327d ago0xaa0d11…e247b3
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams327d ago0x49b60e…63a143
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams327d ago0x54e258…85b029
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams327d ago0x9d8028…9066c2
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams328d ago0x4b6061…97ebf8
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams328d ago0x806711…a222f5
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams335d ago0x3ecb14…6adb25
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams335d ago0x5de1c0…07909e
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams337d ago0x4f7185…deebfd

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.