> For the complete documentation index, see [llms.txt](https://docs.nftx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nftx.io/v1.0/archive/old-tutorials/how-to-get-my-index-fund-listed-on-the-nftx-gallery.md).

# How to get my index fund listed on the NFTX Gallery?

You've set up your NFT Index Fund and want it to be visible on the NFTX Gallery for your community? We got you.

To prevent scam funds from being promoted on the NFTX site and because there are some image/content requirements for fund displays, we've created a **listing request process** for all fund creators to follow.

Estimates of your listing request to be picked up is currently set to 24 hours, with extra time required when further due dilligence is applicable.

Below we will move past all fields you're requested to fill in. While not all fields are required, **please fill in as many as possible** to make it easier for our product team to process your request.

**Link to Listing Request:** <https://docs.google.com/forms/d/e/1FAIpQLScnaUGFuz6-iyLTCeLhcLcFfxAdpPhGzGfxDtET7qgBIJO_xg/viewform>

## Listing Details:

### **Fund Name**

This is the fully written name you'd like the fund to have when listed on the Gallery.

To be consistent between the fund as listed on the NFTX Homepage and the Gallery listing, we recommend using the same fund name that appears under the **Ticker** field on the fund page.

![](/files/-MX96Ed9hiDV2ltvXSaK)

### **Vault ID**

Please supply the fund's VaultID number. When you're unsure what your fund's VaultID is, please follow the [How to create an NFT Index Fund tutorial. ](/v1.0/archive/old-tutorials/how-to-create-an-nft-index-fund.md)

You can also find the VaultID by checking the fund page. It is listed at the end of the **URL** and the VaultID will match the **Fund #** on the fund's page.

![](/files/-MX966PFAj_iUl8SnzJv)

### **Description**

Please describe your fund and its underlying NFT collateral. The more clear you are describing your project, the easier it will be for users to understand and interact with your fund(s) once listed.

![](/files/-MX96HYzvE9U6DcCLW9X)

### **Buy Fund URL**

If your Index Fund is also listed on an AMM (Automated Market Maker), often referred to as Decentralized Exchange (DEX), please provide a link to the pair on i.e. SushiSwap, Uniswap or Balancer.

If you fund has liquidity spread over multiple different exchanges, please supply a link an aggregator such as Matcha or 1inch instead.

If there is no listing on an AMM available for your Index Fund, we will create an **Add Liquidity** button that will direct users to SushiSwap where anyone can add liquidity to create a liquidity pool for your fund.

![](/files/-MX96KctRCR5VmVAwuTO)

### **Name**

To make it easier interacting with you when the DAO has further questions, please provide your name. This is not required.

### **Discord Username**

Similar to having a name, having a Discord username is great for us to quickly reach out to you once we have additional questions.

### **Email address**

Please provide an email address so that we can reach out when your listing request requires additional information.


---

# 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.nftx.io/v1.0/archive/old-tutorials/how-to-get-my-index-fund-listed-on-the-nftx-gallery.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.