> 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/rawlidex.md).
# RawliDEX
**RAWLI DEX** is a perpetual decentralized exchange built on BNB Chain, designed to deliver high-performance derivatives trading with intelligent, automation-ready infrastructure. It serves as the first core product within the RAWLI ecosystem, setting the foundation for a broader DeFi hub focused on scalable, professional-grade trading systems.
\
Unlike early-generation perpetual DEXs that prioritize feature breadth over execution quality, RAWLI DEX is engineered around infrastructure efficiency, liquidity awareness, and intelligent market interaction. The platform is built to support active traders, advanced strategies, and autonomous trading agents operating in fast-moving derivatives markets.
\
It serves as the execution and liquidity layer of Rawli analytics and it is the trading engine of the ecosystem. At its core, RawliDEX allows users to trade perpetual contracts with high capital efficiency, deep liquidity, and minimal slippage. It supports multi-asset perpetual pairs and is built with a risk-optimized liquidity model that balances volatility exposure between liquidity providers and traders. This ensures that positions can be opened, managed, or closed smoothly, even during periods of intense market movement.
\
What makes RawliDEX fundamentally different from standard perpetual DEXs is its Agentic Trading integration. This layer of autonomous AI agents is engineered to assist, enhance, and automate users’ trading activities.
\
**Agentic Trading and Intelligent Automation**
\
A defining feature of RAWLI DEX is its support for agentic trading systems. Rather than treating automation as an external add-on, RAWLI integrates intelligent agents directly into the trading experience. These agents are capable of monitoring market conditions, analyzing liquidity flows, responding to volatility, and executing strategies based on predefined objectives.
\
Agentic trading on RAWLI DEX enables:
\
Continuous market monitoring without manual intervention
\
Data-driven execution strategies informed by market structure and liquidity signals
\
Adaptive risk management based on real-time conditions
\
A foundation for fully autonomous trading workflows as the ecosystem evolves
\
This approach shifts perpetual trading from reactive decision-making to proactive, system-assisted execution.
\
**Infrastructure-First Perpetual Trading**
\
RAWLI DEX is designed with a strong emphasis on trading infrastructure. Order execution, market responsiveness, and system reliability are treated as core concerns. By leveraging BNB Chain’s performance characteristics, RAWLI DEX enables low-latency transactions, cost-efficient execution, and scalable throughput, all of which are critical requirements for perpetual futures trading.
\
The exchange architecture is optimized to support:
\
Efficient price discovery and execution
\
Robust liquidity handling across volatile market conditions
\
Real-time market data availability for both human traders and automated systems
\
A modular backend that supports future product extensions within the RAWLI ecosystem
\
This infrastructure focus ensures RAWLI DEX can scale alongside growing user demand and increasingly sophisticated trading activity.
\
**Built on BNB Chain**
\
RAWLI DEX is deployed on BNB Chain, leveraging its high throughput, low transaction costs, and mature DeFi ecosystem. This choice enables efficient perpetual trading while maintaining accessibility for a broad range of users, from retail traders to advanced participants deploying automated strategies.
\
BNB Chain also provides strong composability with existing DeFi protocols, allowing RAWLI DEX to integrate liquidity, data feeds, and ecosystem tooling while remaining positioned for future cross-product expansion within RAWLI.
\
**Through RawliDEX, traders gain access to:**
\
● Seamless integration with RawliCast: Analytics → decision → execution in one unified flow
\
● Execution automation: Allowing positions to be opened, adjusted, or closed automatically based on real-time market conditions.
\
● Risk-aware AI modules: that track liquidation points, funding trends, and volatility clusters to help users avoid unfavorable conditions.
\
● Continuous on-chain data streaming: ensuring analyses and recommendations reflect real-time market realities, not delayed inputs.
\
By merging decentralized trading with autonomous agentic intelligence, RawliDEX enables users to trade with better accuracy, reduced emotional bias, and improved efficiency, setting a new industry standard for on-chain perpetual markets. The perpetual DEX comes with:
\
● Prediction-Optimized DEX:
\
Built specifically for prediction market liquidity and AMM-driven price discovery.
\
● Dashboard & Farming Points:
\
Users earn farming points through participation, which will be central to future DEX incentives and liquidity programs.
\
● Staking:
\
Designed to power liquidity, secure the platform, and reward long-term participation.
---
# 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/rawlidex.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.