> For the complete documentation index, see [llms.txt](https://docs.cloudeka.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudeka.ai/deka-gpu/deka-gpu-registry/how-to-store-and-manage-artifacts-in-deka-registry/verify-artifacts.md).

# Verify Artifacts

After pushing artifacts, you can verify that they are available in the Service Portal AI.

### Verify Docker Images

1. Open the registry details page.

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

2. Select the **Repository** tab.

<figure><img src="/files/97TNmUL7slRQPGq8iNaD" alt=""><figcaption></figcaption></figure>

3. Check that your Docker image appears in the list. You can click the repository name to view image details such as tags and digest.

### Verify Helm Charts

1. From the registry details page, select the **Helm Charts** tab.

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

2. Check that your Helm chart appears in the list. You can click the chart name to view details such as version and metadata.

{% hint style="warning" %}
If the artifact does not appear, make sure the push process completed successfully.
{% endhint %}


---

# 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.cloudeka.ai/deka-gpu/deka-gpu-registry/how-to-store-and-manage-artifacts-in-deka-registry/verify-artifacts.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.
