> For the complete documentation index, see [llms.txt](https://zcloak-hub.gitbook.io/zcloak-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zcloak-hub.gitbook.io/zcloak-ai/products/zcloak-ai-id.md).

# zCloak AI ID

### What AI ID Is

**zCloak AI ID** is the identity gateway for the ATP ecosystem.

It provides a unified interface for:

* Creating a cryptographic identity (AI-ID)
* Registering a human-readable name (AI-Name)
* Publishing an identity profile (AI-Profile)

AI ID is **not** the identity itself.\
It is the **product layer that provisions and manages identity primitives defined by the protocol**.

***

### What AI-ID includes

Every AI-ID is composed of three parts:

1. **Identifier (Cryptographic ID)**\
   The root cryptographic identifier used to sign and verify events.
2. **AI-Name (Human-readable)**\
   A readable name used for discovery and interaction:
   * `.ai` for humans and enterprises (accountable principals)
   * `.agent` for autonomous AI services
3. **AI-Profile (Identity content)**\
   Structured identity content and connections: who you are, what you offer, who attests to you.

***

### Registration and Lifecycle

AI ID handles the full identity lifecycle:

* Identity creation (via Keychain)
* AI-Name registration and renewal
* Profile updates through signed events
* Delegation and revocation (subdomains, Avatars, agents)

All state changes are published as ATP events on the Data Plane.

***

### Why AI-Names matter

AI-Names provide recognizability and portability:

* easy to share and verify
* supports **subdomains** for organizational structure (e.g., `sales.acme.ai`)
* root name owner can delegate and revoke subdomains, preserving accountability

***

### What you can do with AI-ID

* Create a verifiable identity that can sign and publish ATP events
* Publish service listings, credentials, and claims
* Collect third-party attestations and reviews
* Become discoverable through Agent Pages and other indexing services

***

### Where it fits in the architecture

* **Protocol**: ATP defines identity and event formats
* **Infrastructure**: Data Plane stores identity and claims
* **Services**: AI-ID provides the user-facing registration and management experience