Overview
Julep leverages LiteLLM to seamlessly connect you to a wide array of Language Models (LLMs). This integration offers incredible flexibility, allowing you to tap into models from various providers with a straightforward, unified interface.With our unified API, switching between different providers is a breeze, ensuring you maintain consistent functionality across the board.
Available Models
While we provide API keys for quick testing and development, youβll need to use your own API keys when deploying to production. This ensures you have full control over your usage and billing.
Anthropic
Here are the Anthropic models supported by Julep:OpenAI
Here are the OpenAI models supported by Julep:Groq
Here are the Groq models supported by Julep:OpenRouter
Here are the OpenRouter models supported by Julep:Amazon Nova
Here are the Amazon Nova models supported by Julep:Embedding
Here are the embedding models supported by Julep:Though the models mentioned above support different embedding dimensions, Julep uses fixed 1024 dimensions for all embedding models for now. We plan to support different dimensions in the future.
Supported Parameters
Following are a list of different parameters that can be used to control the behavior of the models.Core Parameters
Core Parameters
Penalty Parameters
Penalty Parameters
Advanced Controls
Advanced Controls
Not all parameters are supported by every model. Please refer to the LiteLLM documentation for more details.Response Format Support: The
response_format parameter is supported by OpenAI, Azure OpenAI, Google AI Studio (Gemini), Vertex AI, Bedrock, Anthropic, Groq, xAI (Grok-2+), Databricks, and Ollama. For the most up-to-date list, check the LiteLLM JSON Mode documentation.Best Practices:
- Start with default values and adjust based on your needs
- Use temperature (0.0 - 1.0) for most cases
- Avoid setting multiple penalty parameters simultaneously
- Test different combinations for optimal results
Usage Guidelines
Consider Model Selection Criteria
- 1. Your budget and cost constraints
- 2. How fast you need responses
- 3. The quality youβre aiming for
- 4. The context window size you require
Follow Best Practices
- 1. Start with smaller models for development and testing
- 2. Use larger context windows only when necessary
- 3. Keep an eye on token usage to manage costs