> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/pro/platform/catalog.md).

# Catalog

### Overview

This guide will take you step by step through managing your music catalog, creating new releases, and ensuring they are properly set up for distribution. You’ll learn how to add tracks, upload artwork, configure metadata, and select distribution options. By the end of this guide, you will be fully equipped to manage your releases efficiently and accurately.

## Prerequisites

{% hint style="info" %}
Before you get started, make sure you have the following ready:
{% endhint %}

* Access to the Revelator platform with the necessary permissions.
* Audio files (WAV or MP3 format).
* Artwork files (JPG or PNG format, recommended dimensions).
* ISRC and ISWC codes if applicable.
* Composer, producer, and rights holder information.

## Guides

{% content-ref url="/pages/-MF0M5aNikYQKhPLMoQR" %}
[Releases](/pro/platform/catalog/managing-your-assets.md)
{% endcontent-ref %}

{% content-ref url="/pages/OThoh4SwBEXRhOT0CEvX" %}
[Tracks](/pro/platform/catalog/tracks.md)
{% endcontent-ref %}

{% content-ref url="/pages/LSixcKHaWiuNDauTm5mI" %}
[Videos](/pro/platform/catalog/create-a-video.md)
{% endcontent-ref %}

{% content-ref url="/pages/SCheJ4TahLfu0e0iQbJF" %}
[Collectibles](/pro/platform/catalog/collectibles.md)
{% endcontent-ref %}

{% content-ref url="/pages/rGiDDsnZIJpgtMGIkTn7" %}
[Contributors](/pro/platform/catalog/rights-holders.md)
{% endcontent-ref %}


---

# 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.revelator.com/pro/platform/catalog.md?ask=<question>&goal=<user_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.