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%daydreams343d ago0x322944…914bed
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams343d ago0x40907c…faef2f
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams343d ago0x48c722…42b290
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams343d ago0x9eae91…fb0617
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams343d ago0x47c180…831629
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams343d ago0x569a64…6681e2
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams344d ago0x31d289…95e7b0
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams344d ago0x2e0fff…06788c
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams344d ago0x94b0ec…5f2e9d
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams344d ago0xf9d55a…54a2fd
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams344d ago0x254116…b809d1
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams344d ago0x711199…ce26e0
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams344d ago0x521227…821a19
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams344d ago0x487c39…75723c
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams344d ago0xf41c5f…28437b
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams344d ago0x658dbe…bacf10
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams344d ago0xcfcf87…870df5
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams345d ago0x1345c9…7f7cbb
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams345d ago0x92e623…85d946
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams345d ago0x61bb1e…1a67d9
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams345d ago0xb106ab…76b5bd
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams345d ago0x4ca82d…744fcc
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams345d ago0x8d8747…20160b
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams345d ago0x5614e8…19961e
0x3d9a…12160x6482…b779BaseBase$0.0001100%daydreams345d ago0x34d777…3fae8e

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.