Choose the right starting route
Use this section when you know your role but do not yet know which DerivaDEX section owns the answer you need.What this page helps you decide
| If your first question is… | Best first route | Why |
|---|---|---|
| what DerivaDEX is and how to think about it | What is DerivaDEX? | start from the platform model before choosing a workflow |
| how to get to one first successful outcome quickly | Platform Quickstart | shortest action-oriented route across UI, API, and governance entry cases |
| whether markets, limits, or visibility rules make the action possible | Supported Markets and Constraints | public product, quota, and visibility boundaries before you invest in the wrong path |
| which route matches your role | Docs by Audience | role-first routing for traders, builders, operators, governance readers, and institutions |
- What is DerivaDEX? gives the shortest platform overview before you choose a deeper route.
- Platform Quickstart gives the shortest safe route into UI trading, API trading, or governance participation.
- Supported Markets and Constraints points to the exact product, limit, and visibility references that bound what you can do.
- Docs by Audience groups the current public routes by trader, builder, operator, governance, token-holder, and institutional needs.
- For Traders starts from product usage, market structure, and risk context.
- For Builders starts from transport choice, source artifacts, and integration boundaries.
- For Node Operators starts from operator-facing scope, restricted surfaces, and operational context.
- For Governance and Compliance starts from governance, safety, and transparency questions.
Continue into the right section
After audience routing, continue into the section that matches intent:- Tutorials for guided first-success workflows
- How-to Guides for specific implementation tasks
- Reference for limits, enums, formulas, and execution rules
- Explanation for architecture and mechanism rationale
- Community & Support for FAQ and troubleshooting
Common routing mistakes this page prevents
| Mistake | Better route |
|---|---|
| starting with API family pages when you really need a first-success lesson | Tutorials |
| starting with explanation when you actually need exact limits, event names, or contract values | Reference |
| starting with builders or operators when the real question is whether the product supports the market or action at all | Supported Markets and Constraints |
| assuming restricted or product-specific surfaces are public just because you can name them | For Builders or For Node Operators before reading the relevant API boundary page |
Launch-node routes
Use the launch nodes below when you want a narrower first stop than the general audience router:- Platform Quickstart for the shortest action-oriented entry path
- Supported Markets and Constraints for product, risk, quota, and visibility boundaries
- Docs by Audience for curated reader-specific entry routes