> For the complete documentation index, see [llms.txt](https://dexrise.gitbook.io/dexrise-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dexrise.gitbook.io/dexrise-documentation/listing-fees-and-requirements/overview.md).

# Listing Overview

This section is for **project teams and developers** who want to launch their services on DEXRise. It consolidates everything you need in one place: the **listing fees**, the **requirements**, and the **application process** for all four services.

{% hint style="info" %}
Listing fees and requirements are **separate from user-facing fees**. For example, the [trading fees](/dexrise-documentation/trading/trading-fees.md) that users pay when swapping are unrelated to the pair listing fees on this page.
{% endhint %}

## Listing fee schedule

| Service                                                                         | Listing fee | Additional fees                       |
| ------------------------------------------------------------------------------- | ----------- | ------------------------------------- |
| **Trading pair** — traditional listing                                          | $100        | —                                     |
| **Trading pair** — zero-liquidity listing (with Floor Price Protection support) | $3,000      | —                                     |
| **Staking pool**                                                                | $50         | —                                     |
| **Presale event**                                                               | $50         | 1% of the tokens sold                 |
| **Airdrop event**                                                               | $20         | **Free on Binance Smart Chain (BSC)** |

Each service has its own page with the full requirements:

| Service                                  | Page                                                                                            |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------- |
| List a trading pair (two listing models) | [Trading Pair Listing](/dexrise-documentation/listing-fees-and-requirements/trading-listing.md) |
| List a staking pool                      | [Staking Pool Listing](/dexrise-documentation/listing-fees-and-requirements/staking-listing.md) |
| Launch a presale                         | [Presale Listing](/dexrise-documentation/listing-fees-and-requirements/presale-listing.md)      |
| Run an airdrop                           | [Airdrop Listing](/dexrise-documentation/listing-fees-and-requirements/airdrop-listing.md)      |

## Shared requirements across services

| Requirement          | Details                                                                                                                                                                                                                                                                              |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Application form** | Every listing starts with the listing request form: [**Listing Application Form**](https://forms.gle/V89E1Nd4eq4N2wtZA)                                                                                                                                                              |
| **Token provision**  | The project provides its tokens for the service it is listing — liquidity for trading pairs, the reward pool for staking, the sale quantity for presales, the event quantity for airdrops                                                                                            |
| **Standard tokens**  | [Staking](/dexrise-documentation/listing-fees-and-requirements/staking-listing.md) and [presale](/dexrise-documentation/listing-fees-and-requirements/presale-listing.md) listings support **standard tokens only** — Fee-on-Transfer tokens and similar mechanics are not supported |
| **Decimals limit**   | Trading pair listings do not support any token with **more than 18 decimals**                                                                                                                                                                                                        |

## How to apply

1. **Review the requirements** for the service you want to list ([trading](/dexrise-documentation/listing-fees-and-requirements/trading-listing.md) / [staking](/dexrise-documentation/listing-fees-and-requirements/staking-listing.md) / [presale](/dexrise-documentation/listing-fees-and-requirements/presale-listing.md) / [airdrop](/dexrise-documentation/listing-fees-and-requirements/airdrop-listing.md)).
2. **Prepare your tokens** — the quantity your service requires, per the requirements on its page.
3. **Submit the** [**listing application form**](https://forms.gle/V89E1Nd4eq4N2wtZA).
4. If you need help or have questions before applying, reach out through the [official DEXRise channels](/dexrise-documentation/support/contact.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dexrise.gitbook.io/dexrise-documentation/listing-fees-and-requirements/overview.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.