add xiaomi provider in tui

[HoangP8]

In dev branch when using TUI, we have 69 different providers now, but lack xiaomi with mimo-v2-flash. pls add

[mirrobot-agent]

@HoangP8 Thank you for submitting this issue. I am now beginning my analysis and will report back shortly.

[mirrobot-agent]

Initial Analysis Report

Summary: Feature request to add Xiaomi provider with the mimo-v2-flash model to the TUI's available providers.

Issue Validation: Partially Confirmed — The request is valid, but requires additional information about Xiaomi's API compatibility.

Reproducibility Assessment: Not Applicable — This is a feature request, not a bug.

Root Cause Analysis:
After thorough codebase analysis, I found:

1. No existing Xiaomi/MIMO support — No references to "xiaomi" or "mimo" exist in the codebase.

2. Provider architecture supports two paths:

   • Built-in providers (in src/rotator_library/providers/) — e.g., OpenAI, Gemini, Anthropic
   • Dynamic OpenAI-compatible providers — automatically created when PROVIDER_API_BASE env vars are set

3. Relevant files for implementation:

   • src/proxy_app/provider_urls.py:5-30 — Hardcoded provider URL mappings
   • src/rotator_library/providers/__init__.py:94-132 — Dynamic provider registration
   • src/rotator_library/providers/openai_compatible_provider.py — Generic OpenAI-compatible implementation

Suggested Labels:

• enhancement — This is a new feature request
• needs-more-info — Implementation depends on Xiaomi API specification details

Proposed Next Steps:

If Xiaomi has an OpenAI-compatible API, users can already add it as a custom provider using environment variables:

# Add to .env
XIAOMI_API_BASE="https://api.xiaomi.ai/v1"  # Replace with actual URL
XIAOMI_API_KEY_1="your-xiaomi-api-key"
XIAOMI_MODELS='["mimo-v2-flash"]'

If a hardcoded provider is preferred, the implementation would require:

1. Add Xiaomi to PROVIDER_URL_MAP in src/proxy_app/provider_urls.py
2. Update .env.example with Xiaomi configuration examples
3. Optionally create a dedicated provider if Xiaomi has non-standard API behavior

Missing Information (Required from Issue Filer):

1. Xiaomi API Documentation URL — What is the official API endpoint?
2. API Compatibility — Is Xiaomi's MiMo API OpenAI-compatible (uses /v1/chat/completions format)?
3. Authentication Method — Does it use standard Bearer token authentication?
4. Model Naming — Is mimo-v2-flash the exact model identifier to use in API requests?

Note: The claim of "69 different providers" likely refers to models available through existing providers (e.g., OpenRouter provides 50+ models), not 69 separate provider integrations.

This analysis was generated by an AI assistant.

[Mirrowel]

Need to update the lists. Xiaomi is supported by litellm.

[Mirrowel]

Addressed in 1282216 on dev branch.

Note: Almost all, if not all, api key providers are using Litellm library dependency. I will eventually remove it as i build up my own implementations, but for now - you are at it's mercy.

[HoangP8]

Thank you, will check on latest commit!