**Description:** Currently, API keys for LLMs are set directly in the code. This approach requires code changes whenever keys need to be updated, which is inconvenient and can introduce security risks if the keys are accidentally committed to version control. **Proposed Solution:** * Use a `.env` file to store sensitive credentials like API keys. * Load these values at runtime using an environment variable manager (e.g., `python-dotenv` for Python projects). * Reference these variables in the code using `os.environ` to securely access the API keys. **Benefits:** * Improves security by keeping keys out of the source code. * Makes it easier to update keys without modifying the codebase. * Facilitates deployment across different environments (development, staging, production) with minimal changes. **Additional Notes:** If this change is implemented, documentation should be updated to guide users on setting up their `.env` file and ensuring it is included in `.gitignore`.