### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

DeepSeek charge different rates for the same model depending on the time window:

off-peak hours: lower input/output token cost peak hours: standard or higher input/output token cost Currently, LiteLLM's model_info pricing fields appear to be static, such as:

input_cost_per_token output_cost_per_token cache_read_input_token_cost This makes it difficult to represent providers whose pricing changes by time period while keeping LiteLLM's built-in cost tracking accurate.

### Motivation, pitch

<img width="1074" height="1116" alt="Image" src="https://github.com/user-attachments/assets/8e8ab465-21d6-4c1a-8332-fa4f8f571b60" />

### What part of LiteLLM is this about?

Proxy

### LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

Yes

### Twitter / LinkedIn details

_No response_