> For the complete documentation index, see [llms.txt](https://docs.neuriio.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neuriio.xyz/trust/creator-rules.md). # Creator Rules Your token is a way for people to back you and what you do. These rules keep it that way. Profiles that break them can be hidden from Neuriio. ## Do * Be who you say you are. Your token is tied to your X account. * Use your profile to say what you do and link to your real work. * Talk about your token as a meme your community can back and trade. ## Don't * **Promise returns.** No "this will 10x", price targets or "guaranteed" anything. * **Promise pumps or buybacks.** Don't say you or anyone will buy to push the price up. * **Present the token as an investment**, equity, shares, revenue share or a claim on you or your company. * **Impersonate** a person, project or company. * **Coordinate manipulation**, such as wash trading or organised pump-and-dumps. * **Post illegal or harmful content** in your profile or on the feed. ## What happens if you break them Neuriio can hide your profile and token from the app. Because tokens live on-chain, holders can still sell, and your pool's liquidity stays locked. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.neuriio.xyz/trust/creator-rules.md?ask=&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 `build a script that syncs our docs to a CMS` 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.