> 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/disclaimer.md). # Disclaimer **Tokens launched on Neuriio are memes with no promise of value.** * A token is not equity, shares, debt, a security, or a claim on any person, company, revenue or asset. * Creators owe holders nothing. Creators receive no token allocation and no share of any company's revenue through Neuriio; they earn only their share of trading fees. * Nothing on Neuriio, in these docs or in any creator's profile is investment, financial, legal or tax advice. * Token prices can go to zero. Only use funds you can afford to lose. * Neuriio is software running on public blockchains. Transactions can't be reversed, and smart contracts can have bugs despite testing and review. * Neuriio is currently on **Elysium testnet**. Testnet tokens and testnet HYPE have no value. * You're responsible for following the laws where you live. Neuriio may not be available everywhere. --- # 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/disclaimer.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.