> For the complete documentation index, see [llms.txt](https://whitepaper.rank.trading/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.rank.trading/platform-features/strat-metadata/types.md).

# Types

There are two types of no-code trading strategies: basic and premium. Basic Strats include basic  features such as limited TA tools and more. Premium Strats include everything a basic Strat has plus  additional features such as increased TA tools, maximum leverage and more. Both also have different&#x20;

activation thresholds, whereby a minimum investment deposit is required to invest in a Strat.&#x20;

*Basic*&#x20;

Basic Strats include access to a limited number of trading resources such as limited TA functions as  well as limited leverage. The minimum activation investment is: 1000 USDT.&#x20;

*Premium*&#x20;

Premium Strats include access to everything a basic Strat has as well as increased trading resources  such as a variety of TA functions, greater leverage, additional indicators, and more. The minimum activation investment is: 5000 USDT.

<br>


---

# 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://whitepaper.rank.trading/platform-features/strat-metadata/types.md?ask=<question>&goal=<endgoal>
```

`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.