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

# Documentation

Welcome to the complete documentation for Cryptic, the infrastructure layer for AI-native communication, cryptographic identity, and crypto-native payments.

Cryptic combines post-quantum secure communication, encrypted data transfer, non-custodial wallet functionality, native payment rails, confidential AI workflows, and developer infrastructure into one connected product stack.

Cryptic is not building another chat application. It is building the secure coordination layer where humans, teams, wallets, applications, and AI agents can communicate, verify identity, approve actions, move value, and interact through cryptographic rails.

#### The platform is built around three layers:

**Cryptic Mobile — Live**\
The consumer entry point for secure communication, wallet functionality, crypto-native payments, card access, and everyday use.

**Cryptic Desktop — Beta**\
The secure command layer for communication, wallet management, confidential AI workflows, swaps, DeFi activity, encrypted storage, and ecosystem integrations.

**Cryptic SDK — In Final Stage of Development**\
The developer infrastructure layer for encrypted communication, cryptographic identity, key management, payment rails, and future agent systems.

#### What Is Cryptic?

Cryptic is a cryptographic identity, secure communication, and crypto-native payments ecosystem designed for the post-quantum and AI-native era.

Rather than fragmenting trust across separate communication tools, wallets, payment rails, DeFi interfaces, storage platforms, identity systems, and AI workflows, Cryptic brings these layers into one integrated product stack.

At the foundation is Cryptic’s cryptographic identity model. When a user creates a Cryptic account, they generate a collection of cryptographic keys across EVM, Solana, Dilithium, and Kyber. Together, these keys form the basis for secure communication, encrypted data transfer, wallet functionality, payment coordination, and future human-to-agent or agent-to-agent workflows.

At the infrastructure level, Cryptic provides developer-accessible rails for encrypted communication, cryptographic identity, key management, payment flows, and future agentic systems through the Cryptic SDK.

At the product level, Cryptic Mobile and Cryptic Desktop turn that infrastructure into usable applications for individuals, teams, developers, protocols, wallets, applications, and crypto-native communities.

#### Cryptic Enables

**Post-quantum secure communication**\
Secure communication and encrypted data transfer using modern post-quantum cryptography, including ML-KEM and ML-DSA based security.

**Cryptographic identity**\
A sovereign identity layer built around EVM keys, Solana keys, Dilithium keys, and Kyber keys, giving users a secure base for communication, wallet access, approvals, and coordination.

**Crypto-native payments and settlement**\
Wallet functionality and native payment flows designed to make digital value movement faster, simpler, and more natural inside secure communication environments.

**Non-custodial key sovereignty**\
User-controlled wallet and identity infrastructure designed so users remain in control of their keys, assets, approvals, and financial actions.

**Desktop financial workflows**\
A secure command layer where users can communicate, coordinate, manage wallets, swap tokens, interact with DeFi, use confidential AI workflows, store encrypted data, and operate across crypto-native tools without jumping between disconnected systems.

**Developer and ecosystem infrastructure**\
SDK infrastructure that allows developers, apps, protocols, wallets, teams, and agent frameworks to integrate encrypted communication, cryptographic identity, key management, payment rails, and future agent systems into their own products.

**Agentic coordination**\
Infrastructure for future human-to-agent and agent-to-agent communication, where agents can exchange encrypted data, verify identity, request approvals, and coordinate value movement through secure cryptographic rails.

Cryptic is not another messenger.

It is not just another wallet.

It is the cryptographic identity, secure communication, and payment infrastructure layer behind a growing product stack for users, teams, developers, wallets, applications, and AI agents.

#### Why This Documentation Matters

Cryptic is being built for a world where communication, identity, payments, data transfer, AI workflows, and financial coordination are becoming increasingly connected.

As quantum computing creates long-term risk for today’s encryption standards, and as crypto-native and AI-native workflows become more complex, users, teams, developers, and applications need infrastructure that protects both communication and value movement.

This documentation provides guidance for:

* Users navigating secure communication, wallet functionality, payments, card access, encrypted storage, and privacy settings
* Developers integrating encrypted communication, cryptographic identity, key management, payment rails, and agent infrastructure through the Cryptic SDK
* Partners exploring integrations across storage, DeFi, payments, onboarding, wallets, AI infrastructure, agent frameworks, and ecosystem tools
* Investors and stakeholders evaluating Cryptic’s product stack, business model, roadmap, token utility, traction, and long-term infrastructure opportunity

#### Quick Navigation <a href="#quick-navigation" id="quick-navigation"></a>

**New to Cryptic?** Start with [**Project Overview**](/cryptic-documentation/project/1.-project-overview.md) to understand our mission and market opportunity.                                                                                                                                                                  **Technical Implementation?** Jump to [**Technology Overview**](/cryptic-documentation/technology/2.-technology-overview.md) for architecture and security details.                                                             &#x20;

**Ready to Use Cryptic?** Check out our [**User Experience & Guides**](/cryptic-documentation/user-experience/3.-user-experience-overview.md) for step-by-step walkthroughs.                                                                       &#x20;

**Understanding Tokenomics?** Review our [**Business Model**](/cryptic-documentation/tokenomics-and-business-model/4.-tokenomics-overview.md) and token utility framework.     \
&#x20;                                                                                                                                                                                            \
**Go-to-Market Strategy?** Explore our [**Strategic Approach**](/cryptic-documentation/marketing/5.-marketing-overview.md) to user acquisition and partnerships.

> *Cryptic is building post-quantum secure communication and crypto-native payments across SDK, Desktop, and Mobile infrastructure.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cryptic-documentation.gitbook.io/cryptic-documentation/welcome/documentation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
