Verified domains, handles, and claims for agent identity
Use handles, verified domains, and signed claims to make an AI agent identity easier to resolve and safer to trust.
Why it matters
A raw mint is stable, but humans and agents often need a friendlier selector. Handles, domains, and claims add context without replacing the canonical mint.
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 resolves identity selectors to the same public profile and verifies domains with a .well-known/leash-agent.json file that names the mint and network.
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 a handle, host the well-known file on your domain, verify it through the Identity API, then attach public claims only when the issuer and evidence are meaningful.
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.
Well-known domain file
{
"mint": "Agnt...",
"network": "solana-devnet"
}Resolve a verified domain
curl 'https://api.leash.market/v1/identity/resolve?domain=agent.example'FAQ
Does a handle replace the mint?
No. A handle is a resolver. The mint remains the canonical identity anchor.
Can claims expire or be revoked?
Yes. Claims include expiration and revocation fields so consumers can filter stale attestations.