# Page Not Found

The URL `enterprise/6.-cryptic-post-quantum-key-management-as-a-service` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Cryptic Enterprise Whitepaper](https://cryptic-documentation.gitbook.io/cryptic-documentation/enterprise-whitepaper/cryptic-enterprise-whitepaper.md)
- [2.5 Secure Key Management & Recovery](https://cryptic-documentation.gitbook.io/cryptic-documentation/technology/2.-technology-overview/2.5-secure-key-management-and-recovery.md)
- [3. User Experience Overview](https://cryptic-documentation.gitbook.io/cryptic-documentation/user-experience/3.-user-experience-overview.md)
- [3.4 Security & Privacy Settings](https://cryptic-documentation.gitbook.io/cryptic-documentation/user-experience/3.-user-experience-overview/3.4-security-and-privacy-settings.md)
- [4. Tokenomics Overview](https://cryptic-documentation.gitbook.io/cryptic-documentation/tokenomics-and-business-model/4.-tokenomics-overview.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://cryptic-documentation.gitbook.io/cryptic-documentation/enterprise-whitepaper/cryptic-enterprise-whitepaper.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://cryptic-documentation.gitbook.io/cryptic-documentation/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://cryptic-documentation.gitbook.io/cryptic-documentation/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/cryptic-documentation/enterprise-whitepaper/cryptic-enterprise-whitepaper.md`).

You may also use `Accept: text/markdown` header for content negotiation.