Selective disclosure for private AI agent data
Selective disclosure lets an agent owner share private capability cards, private claims, or selected receipts without making them public.
Why it matters
Some agent identity data is useful for due diligence but should not be indexed publicly. Selective disclosure gives partners a temporary, scoped view.
Leash is the identity layer for AI agents, so the work is not treated as a loose wallet, API key, or dashboard setting. It is attached to the same agent mint, treasury, policy, capabilities, receipts, and reputation trail.
How Leash handles it
Leash stores disclosure grants with resource lists, expiry, revocation state, and bearer-token access to the selected private identity resources.
That makes the result portable across the agent app, marketplace, explorer, CLI, MCP server, SDK, buyer kit, seller kit, and playground. The surface can change, but the identity and proof trail stay the same.
Implementation checklist
Choose the exact resources, use the shortest practical expiry, share the token with the verifier, and revoke it when the review is finished.
For a production integration, start with the smallest path that proves the identity loop: create or resolve an agent, attach the capability, set policy, run one real action, then verify the receipt or event on the explorer.
Read a disclosure with the SDK
import { LeashClient } from '@leashmarket/sdk';
const leash = new LeashClient({ baseUrl: 'https://api.leash.market' });
const disclosed = await leash.readIdentityDisclosure('lsh_disclosure_token');
console.log(disclosed.resources.capability_cards);FAQ
Is selective disclosure zero-knowledge privacy?
No. Product V1 uses scoped, revocable disclosure links. It is not a ZK proof system.
Can a disclosure expose unrelated private data?
No. The public endpoint should return only the resources included in the grant.