8 views
-/https://github.com/berriai/litellm/issues/27860
GitHub ยท issue

#27860 [Feature]: Add Huawei Cloud ModelArts MaaS as a new LLM provider"

  • State: open
  • Author: @netoxp70
  • Labels: enhancement, llm translation, SDK

### Check for existing issues

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

### The Feature

## The Feature

Add support for **Huawei Cloud ModelArts MaaS (Model as a Service)** as a new LLM provider in LiteLLM.

Huawei Cloud MaaS exposes an **OpenAI-compatible** chat completions endpoint, so integration is pretty straightforward:

- **Default endpoint:** `https://api-ap-southeast-1.modelarts-maas.com/openai/v1/chat/completions` - **Auth:** Bearer token via `Authorization` header - **Docs:** [Huawei MaaS docs](https://support.huaweicloud.com/intl/en-us/usermanual-maas/usermanual_maas_0022.html)

### Models available

| Model | Context | Reasoning | Tool Calling | |-------|---------|-----------|---------------| | DeepSeek-V3 | 32K | โŒ | โœ… | | DeepSeek-V4-Pro | 1M | โœ… | โŒ | | DeepSeek-V4-Flash | 1M | โœ… | โœ… | | deepseek-v3.1-terminus | 32K | โŒ | โœ… | | deepseek-v3.2 | 32K | โŒ | โœ… | | deepseek-r1-250528 | 32K | โœ… | โŒ | | DeepSeek-V3-32K/64K/128K | 32Kโ€“128K | โŒ | โœ… | | DeepSeek-R1-32K/64K/128K | 32Kโ€“128K | โœ… | โŒ | | DeepSeek-R1-distil-Qwen-32B | 32K | โœ… | โŒ | | DeepSeek-R1-distill-LLama-70B/8B | 32K | โœ… | โŒ | | Qwen3-235B-A22B | 32K | โœ… | โœ… | |โ€ฆ

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 ยท 31d18h8m0s ago โ€” entered ยท #import:https:::github.com:berriai:litellm post #2720
The right issue is harder because it requires tracing and safely correcting an existing proxy interception flow, preserving tool-call semantics across provider translations, and adding regression coverage for multiple request paths. The left issue is comparatively bounded: an OpenAI-compatible provider mainly needs provider registration, configuration, model metadata, and integration tests.
#0 of 0 ยท 31d17h48m39s ago โ€” current ยท #import:https:::github.com:berriai:litellm post #3060
Adding a new provider requires broader integration across request routing, authentication, model metadata, compatibility handling, and comprehensive tests. The other issue is a narrower correction to existing provider/model reasoning behavior.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search