> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.clossir.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.clossir.com/_mcp/server.

# Identity — Overview

01 / IDENTITY

Identity establishes *who* a party is and *which wallets* they control, then issues portable,
reusable attestations that the rest of the platform — Compliance, Asset Issuance, Lending —
reads on every action. Verify once; the proof travels across every chain.

## Where it fits (regulatory boundary)

Clossir provides the verification rails and attestation store. Issuers (or their KYC/KYB
providers) remain the responsible party for onboarding decisions and record-keeping. Clossir
never takes custody of identity documents beyond what the configured provider returns.

## Key features

* Reusable identity & wallet attestations, portable across chains
* Pluggable KYC/KYB providers; issuer-scoped onboarding policies
* Wallet binding — cryptographic proof a wallet belongs to a verified party
* Org-scoped, RLS-isolated records

## Use cases

* Investor onboarding before access to eligible assets
* Issuer / signer verification for governance actions
* Re-verification and attestation expiry / renewal

## How it works

A party completes verification through the configured provider; Clossir records the result as
an attestation and binds the party's wallet(s). Downstream products query the attestation
rather than re-running KYC.

## API

See [Identity — API](/products/identity/api) for the representative operations.

## Fees

*Fee documentation is coming soon.*

## Dependencies

Compliance reads Identity attestations to evaluate transfer eligibility.