Models
llms
The llms section contains the configuration for the model. Each model is defined by the unique key (e.g. azure-uk-gpt35), and the following properties:
deployment_name: The name of the deployment in the model provider’s system.source: The type of the model provider. List of supported providers can be found here.type: Type of the source provider (text, image, video, …). List of supported providers and types can be found here.url: The URL of the model providerapi_key: The API key for the model provider. For more information on how to store secrets, see api keys section.cost_profile: The cost profile for the model. The cost profile defines the cost of the model. The cost profile is defined in thecost_profilessection.priority(optional): Priorities allow you to prefer certain models over others in the selected group. Check load balancing section for more details.
llm_groups
The llm_groups section contains the configuration for the model groups. Each group is defined by the unique key (e.g. gpt35), and the following properties:
models: The list of models that belong to the group. Models must be defined in thellmssection.
Groups are used by end users to select the model they want to use. The group is then used to select the model from the list of models. For example following code will select the model from the gpt35 group:
cost_profiles
The cost_profiles section contains the configuration for the cost profiles. Each cost profile is defined by the unique key (e.g. azure-gpt35-turbo), and the following properties:
id: The unique identifier of the cost profile.usd_per_1k_input_tokens: The cost of 1000 input tokens in USD.usd_per_1k_output_tokens: The cost of 1000 output tokens in USD.usd_per_1k_cached_input_tokens: Optional, the cost of 1000 cached output tokens in USD (tracked only for monitoring purposes at the moment)
Example of models configuration file: