> 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

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.

<figure><img src="/files/gK2XHyDDmraimNLzcVj8" alt=""><figcaption></figcaption></figure>

* 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

<figure><img src="/files/Gd5EhN971uBIZ21lS7zJ" alt=""><figcaption></figcaption></figure>

* On the **Package Registry tab**, click "create".

<figure><img src="/files/lJxTEnUqXwy1L7iEv4Ae" alt=""><figcaption></figcaption></figure>

* 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.

<figure><img src="/files/KUIwFtACqzdU3ZdXulZo" alt=""><figcaption></figcaption></figure>

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 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://docs.nalpeiron.com/zentitle2-docs/ui-administration/api-credentials/package-registry.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.
