## What problem is this solving?

Today LiteLLM Proxy appears to support outbound proxying mainly via **process-level / environment-level** proxy settings such as:

- `HTTP_PROXY` - `HTTPS_PROXY` - `ALL_PROXY` - `AIOHTTP_TRUST_ENV`

That works for a **single global egress path**, but it does not solve a common deployment need:

> Different upstream models/providers need to use different outbound proxies.

Examples: - some model deployments must go through a SOCKS5 proxy - some should use direct outbound traffic - some should use a different HTTP/SOCKS proxy depending on provider, region, compliance, or network topology

Right now the practical workaround seems to be running **multiple LiteLLM Proxy instances** and splitting traffic externally, which adds operational complexity.

---

## Requested feature

Please support **per-model outbound proxy configuration** in `config.yaml` for LiteLLM Proxy.

For example, something like this:

```yaml model_list: - model_name: openai-via-socks5 litellm_params: model: openai/gpt-4o api_key: os.environ/OPENAI_API_KEY outbound_proxy: socks5://127.0.0.1:1080

- model_name: anthropic-direct litellm_params: model…