> For the complete documentation index, see [llms.txt](https://docs.evedex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.evedex.com/readme.md). # EVEDEX Whitepaper The modern crypto market lacks quality and simple solutions that can help people get rich and achieve life-changing success. For years, the cryptocurrency audience has been convinced that to be successful, they simply need to invest in a specific coin—without being warned about the risks. At the same time, major players prevent users from peacefully earning their Bitcoin and Ether. Deposit leaks, account freezes, clunky interfaces, slow speeds—it seems like someone big out there simply doesn't want more people to rise. That's why at EVEDEX, we are developing an ecosystem of services that allows every user to focus on the most important thing—**making money**—while worrying about nothing else. At EVEDEX, we believe the only way to achieve life-changing success is through consistent work and education. We focus on providing services for smart trading, education, and offer trading opportunities with crypto assets that have been tested by time and the market. Low fees, a convenient and sleek interface, high speeds, security, and a reliable team—you don't need anything else but yourself to **achieve success**. --- # 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.evedex.com/readme.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.