> For the complete documentation index, see [llms.txt](https://docs.urbit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.urbit.org/urbit-os/kernel/jael.md). # Jael Guide to Jael, Arvo's vane for networking key infrastructure. Jael is Arvo's module for networking key infrastructure. The main purpose of Jael is keeping track of [Azimuth](/urbit-id/what-is-urbit-id.md)-related information. This includes: * Every known Urbit ship's public keys. * Every known Urbit ship's [key revision number and continuity breach number](/urbit-id/life-and-rift.md). * Every known Urbit ship's sponsor. It also handles the local ship's private keys, keeps track of galaxy domain prexifes, and performs some tasks related to booting the local ship for the first time. The database of PKI information that Jael maintains is used by other modules and applications for identity validation, encryption, decryption, and other cryptographic functions. In particular, [Ames](/urbit-os/kernel/ames.md) uses the information stored in Jael to encrypt packets it sends to other ships, and to decrypt and validate packets it receives from them. Jael has a few tasks you can use to interact with it. In particular, its [`%public-keys` task](/urbit-os/kernel/jael/tasks.md#public-keys) allows an application or thread to subscribe for PKI updates for a set of ships. --- # 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://docs.urbit.org/urbit-os/kernel/jael.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.