> For the complete documentation index, see [llms.txt](https://rawlianalytics.gitbook.io/rawli-analytics-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rawlianalytics.gitbook.io/rawli-analytics-docs/basics/editor.md). # CORE FEATURES RAWLI Analytics is designed around two foundational pillars that work together to create an intelligent, liquid, and highly accessible ecosystem. It features RawliDEX, a perpetual DEX with an agentic trading terminal powered by autonomous AI agents and RawliCast, an AI analytics companion that studies market data, sentiments, and historical patterns to offer prediction suggestions. Each component complements the others, resulting in a unified platform where users can forecast events, stake their assets, earn rewards, automate strategies, and interact with high-level intelligence tools that amplify their prediction capabilities. \ The platform core features include: • RawliDex • Staking • RawliCast • Prediction Market • Governance --- # 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://rawlianalytics.gitbook.io/rawli-analytics-docs/basics/editor.md?ask=&goal= ``` `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.