> For the complete documentation index, see [llms.txt](https://docs.popularex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.popularex.com/iv.-tokens-of-popularity-tops/creating-tops.md).

# Creating ToPs

Creating and launching a ToP on Populárex is the process of registering information about a unique Object of Popularity on the POPXChain and promoting it in the global ranking. The user who launches the ToP and casts the first vote becomes its first General Sponsor. Before launching, the user must fill in the information about the new Object of Popularity in compliance with all the rules.

There are three main rules on the platform when creating a token: Uniqueness, Publicity, and Authenticity:

* Uniqueness - each ToP must be unique, which means that only one unique Object of Popularity can correspond to one ToP, and only one ToP can correspond to one Object.
* Publicity - information about the Object must be open and accessible to the public.
* Authenticity - the data about the Object of Popularity must be accurate.

The community of Validators is responsible for checking the uniqueness and compliance of the created tokens with the platform's rules.

*This section is subject to additions and modifications. Stay tuned for updates.*


---

# 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.popularex.com/iv.-tokens-of-popularity-tops/creating-tops.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.