> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/quick-onboarding/adding-a-registry.md).
# Adding a Registry
**a. Resources > Registry**
Click on the “Resources” tab from the left-hand menu. Select the Registries
**b. Create New Registry**
The screen updates to a view showing available registries. Click on “Attach New Registry”.
**c. Select Provider**
Select the provider from which you want to integrate your registry onto Ozone. For this onboarding guide, let us go ahead with Google GCR
**d. Onboard your Registry**
Give a name and description for your registry. To integrate from GCR, upload a file into the field “Json Key for Project”. For more information on generating this key, click on the bottom-right link.
Click on “Create” after filling the required details. Your registries will now be visible in the registry view screen while navigating from the “Resources” tab from the menu.
---
# 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.ozone.one/ozone-end-user-guide/quick-onboarding/adding-a-registry.md?ask=&goal=
```
`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.