> For the complete documentation index, see [llms.txt](https://academy.autonomys.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.autonomys.xyz/auto-suite/auto-id/auto-pki.md). # Auto PKI An overview of our framework for creating custom Auto ID registries **Auto PKI** is a framework for creating and deploying unique consortium-based instances of the Auto ID registry for industry or application-specific use cases. Consortium-based identity systems are designed to facilitate secure and trusted digital interactions between a group of organizations or entities within a specific industry or domain. These systems establish a shared framework for managing digital identities, enabling participating members to authenticate and authorize individuals or entities within the consortium. Examples of consortium-based identity systems include the banking industry's efforts to establish a shared know-your-customer (KYC) platform, and the shipping industry's initiatives to create a unified system for verifying the identities of vessels and their crew members. In a consortium-based identity system built using Auto PKI, consortium members agree on policies and standards to govern the issuance, management and verification of the custom Auto IDs within their ecosystem, establishing a trusted environment where identities are recognized and accepted across the consortium. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://academy.autonomys.xyz/auto-suite/auto-id/auto-pki.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.