> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/ui-administration/api-credentials/package-registry.md).
# Package Registry
Self-provision the authentication credentials you need to download SDK packages and LLS Docker images from the Package Registry, limited to one active token per tenant.
Our SDK packages and LLS docker images are hosted in our Package Registry.
Our customers need authentication credentials to download them, which they can self-provision from this section.
* To get your credentials, navigate to the **Administration>API credentials** section.
* Then choose the third "**Package Registry**" tab to get started.
{% hint style="warning" %}
This tab is only visible if the user has the `API Admin` permission.
* Only **one token** can exist at a time per tenant.
* The **"Create"** button is disabled when a token already exists.
{% endhint %}
### Creating your credentials token
* On the **Package Registry tab**, click "create".
* This creates the token; you only need to copy these details to access the SDKs you need.
* This process does not require input; simply click the copy buttons next to the Username and Password and save them for later use.
The only other action on this tab is to delete the credentials to either get new ones or to remove them from your account.
#### Next Steps:
* To get our SDKs, please go to our documentation's ["developers" section here](/zentitle2-docs/developers/licensing-and-management-apis.md).
---
# 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.nalpeiron.com/zentitle2-docs/ui-administration/api-credentials/package-registry.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.
