Choose who can read the case
Use public, unlisted, private, and payer privacy settings intentionally.
Visibility controls where the case appears and who can open the full record. Payer visibility separately controls whether app and API receipt surfaces show the payer wallet.
PublicListed in public case surfaces. Direct-readable. Eligible for x402 paid reads.
UnlistedHidden from browse surfaces. Direct-link readable. Not served by the x402 paid-read layer.
PrivateHidden from browse and public direct reads. Participant wallets unlock details through a signed challenge.
Payer privacyPublic payer mode may show wallet fields. Private payer mode redacts app/API payer fields while onchain transactions remain auditable.
How to choose
Use publicWhen the question is safe to list and useful to other users, bots, or paid readers.
Use unlistedWhen you want a shareable case link without putting the case in public browse surfaces.
Use privateWhen the case should require participant wallet verification before full details are returned.
Use private payerWhen app and API receipt surfaces should not display the payer wallet by default.
Important limits
Visibility controls app and API surfaces. Onchain transactions, block explorer records, and third-party wallet activity may still be public. Private cases reduce product-surface exposure but should not be treated as a place for illegal, unsafe, or highly sensitive material.