feat: add FuturMix as named OpenAI-compatible provider

[FuturMix]

Summary

Adds FuturMix.ai as a named OpenAI-compatible provider in providers.json.

FuturMix is a enterprise AI agent platform that provides OpenAI-compatible access to 22+ models (Claude, GPT, Gemini) . Adding it as a named provider allows users to use futurmix/ prefix for model routing.

Changes

• Added futurmix entry to litellm/llms/openai_like/providers.json

Usage

Once merged, users can call FuturMix models with:

import litellm

response = litellm.completion(
 model="futurmix/claude-sonnet-4-20250514",
 messages=[{"role": "user", "content": "Hello"}],
 api_key="your-futurmix-key"
)

Environment variable: FUTURMIX_API_KEY

Testing

import os
os.environ["FUTURMIX_API_KEY"] = "sk-..."

# Chat completion
response = litellm.completion(
 model="futurmix/gpt-4o",
 messages=[{"role": "user", "content": "test"}]
)

# Streaming
for chunk in litellm.completion(
 model="futurmix/claude-sonnet-4-20250514",
 messages=[{"role": "user", "content": "test"}],
 stream=True
):
 print(chunk.choices[0].delta.content or "", end="")

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

FuturMix seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[veria-ai]

Low: No security issues

This PR adds a new entry to the OpenAI-compatible providers JSON registry for FuturMix. It follows the identical pattern as all existing entries (HTTPS base URL, env-var-based API key). No code changes, no new logic paths, no security concerns.

---

Status: 0 open
Risk: 1/10

Posted by Veria AI · 2026-04-25T04:25:01.709Z

[greptile-apps]

Greptile Summary

This PR registers FuturMix as a named OpenAI-compatible provider by adding a single entry to litellm/llms/openai_like/providers.json. The entry follows the established structure exactly and all four fields used (base_url, api_key_env, api_base_env, param_mappings) are fully supported by json_loader.py and dynamic_config.py.

Confidence Score: 5/5

This PR is safe to merge — it is a minimal, non-breaking addition of a single JSON provider entry.

The change is a single JSON entry that follows the identical pattern of existing providers. All fields are already handled by the loader, no logic is touched, and there are no backwards-incompatible changes.

No files require special attention.

Important Files Changed

Filename	Overview
litellm/llms/openai_like/providers.json	Adds futurmix provider entry following the established pattern; all fields (base_url, api_key_env, api_base_env, param_mappings) are supported by the JSON loader and consistent with existing entries.

Sequence Diagram

sequenceDiagram
    participant User
    participant LiteLLM
    participant ProvidersJSON as providers.json
    participant DynamicConfig as dynamic_config.py
    participant FuturMix as FuturMix API (futurmix.ai/v1)

    User->>LiteLLM: completion(model="futurmix/gpt-4o", ...)
    LiteLLM->>ProvidersJSON: lookup "futurmix" entry
    ProvidersJSON-->>LiteLLM: base_url, api_key_env, param_mappings
    LiteLLM->>DynamicConfig: resolve base_url & api_key (FUTURMIX_API_KEY)
    DynamicConfig-->>LiteLLM: resolved config
    LiteLLM->>FuturMix: POST /v1/chat/completions (OpenAI-compatible)
    FuturMix-->>LiteLLM: response
    LiteLLM-->>User: ModelResponse

Loading

_{Reviews (1): Last reviewed commit: "feat: add FuturMix as named OpenAI-compa..." | Re-trigger Greptile}

[FuturMix]

Closing in favor of #26504, re-submitted from personal account to resolve CLA signing.