Support map
Use this section when you are blocked and need the right recovery route.Use this page when
| If you need… | Use this page because… |
|---|---|
| the fastest public route for a docs, trading, API, or AI-access problem | it compresses the support surface into one symptom-first map |
| to know whether to self-serve or escalate | it distinguishes FAQ, troubleshooting, support channels, release notes, community resources, and AI-tooling guidance |
| to confirm whether a route or behavior changed recently | it points to the changelog before you assume the docs are stale |
Start with the symptom
| If you are blocked on… | Start here | Then use |
|---|---|---|
| a common product or integration question | FAQ | Troubleshooting if the answer is not enough |
| a concrete failure, unexpected API response, or confusing trading outcome | Troubleshooting | Support Channels if self-serve recovery is insufficient |
| needing an official escalation path | Support Channels | Community Resources for public discussion surfaces |
| evaluating the public docs as an institution or regulated diligence reader | Institutional Resources | Support Channels when public docs are not enough |
| finding the public institutional onboarding or market-maker-evaluation baseline | Institutional Onboarding Public Baseline or Market Maker Evaluation and Program Boundaries | Institutional Resources for the broader institutional map |
| finding the broader builder and contribution surface | Developer Ecosystem | For Builders for task-specific technical routing |
| choosing the right public contribution path before opening work | Open Source Contribution Paths | Developer Ecosystem for the wider builder map |
| following the current public trading-learning path | Trading Education Resources | Tutorials for guided first-success lessons |
| wanting to confirm whether docs or product behavior changed recently | Release Notes / Changelog | the relevant section route for current canonical guidance |
| finding the right public AI-tooling access path | Use DerivaDEX Docs with AI Tools | Support Channels if the published AI access path appears inconsistent |
hosted docs returning the wrong boundary behavior, such as retired /api-specs/* URLs serving raw JSON or YAML | Support Channels | include the exact URL, observed content type, and the public route you expected |
- FAQ
- Troubleshooting
- Support Channels
- Release Notes / Changelog
- Community Resources
- Institutional Resources
- Institutional Onboarding Public Baseline
- Market Maker Evaluation and Program Boundaries
- Developer Ecosystem
- Open Source Contribution Paths
- Trading Education Resources
- Use DerivaDEX Docs with AI Tools
Escalate by problem type
| Problem type | Best route |
|---|---|
| likely docs mismatch or missing public explanation | FAQ, then Support Channels |
| concrete failure or unstable workflow | Troubleshooting |
| need the official discussion or governance/community surface | Community Resources |
| need public diligence or market-maker-evaluation routing | Institutional Resources |
| need the public institutional onboarding baseline or the public market-maker-program boundary | Institutional Onboarding Public Baseline or Market Maker Evaluation and Program Boundaries |
| need the broader public builder and contribution map | Developer Ecosystem |
| need the public contribution workflow map before choosing code, docs, or governance work | Open Source Contribution Paths |
| need the current trading-learning route map | Trading Education Resources |
| need MCP or AI-tooling access guidance | Use DerivaDEX Docs with AI Tools |
| need to know whether recent docs hardening or route changes already covered the issue | Release Notes / Changelog |
Escalation rule
Use the public docs first when the answer should come from published product, API, safety, or governance material. Escalate only after checking the relevant canonical route, especially when the question depends on:- restricted-surface visibility
- hosted-doc deployment drift
- an apparent mismatch between two public docs pages
- a missing public explanation for a documented behavior
Domain note
The canonical current public docs domain isdocs.derivadex.com. Treat docs.derivadex.io as legacy continuity rather than the first authority when the two domains diverge.