Repository navigation
feat(scx-ai): add six SCX.ai models and update Qwen3.8-Max pricing - #45502
bhuvan2134686 wants to merge 1 commit into
Conversation
Add cost map rows for DeepSeek-V4.1-flash, GLM-5.2-Fast, GLM-5.3, GLM-5.3-Fast, GLM-5.3-Flash and Kimi-K3, and move scx-ai/Qwen3.8-Max to SCX.ai's current rates. Without a row, LiteLLM routes these models but rejects tool calls and records zero spend.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
| "scx-ai/DeepSeek-V4.1-flash", | ||
| "scx-ai/GLM-5.2", | ||
| "scx-ai/GLM-5.2-Fast", | ||
| "scx-ai/GLM-5.3", | ||
| "scx-ai/GLM-5.3-Fast", | ||
| "scx-ai/GLM-5.3-Flash", | ||
| "scx-ai/Kimi-K3", |
There was a problem hiding this comment.
The expanded test only compares maps. AGENTS.md requires regression coverage before merging; add tool-support and cached-cost tests using loaded rates
Context Used: AGENTS.md (source)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
| "scx-ai/GLM-5.2", | ||
| "scx-ai/GLM-5.2-Fast", | ||
| "scx-ai/GLM-5.3", | ||
| "scx-ai/GLM-5.3-Fast", |
There was a problem hiding this comment.
GLM-5.3-Fast lacks live QA because the key lacks access. Repository rules require real-provider proof before merging; add proxy results with an authorized key
Rule Used: Flag if the PR has no proof of e2e testing (if e2e testing is applicable here. If it's like an AGENTS.md change or something then probably no need to have e2e test proof) that either doesn't exist, claims that the box that it was trying to run in doe... (source)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
TLDR
Problem this solves:
UnsupportedParamsErrorscx-ai/Qwen3.8-Maxstill carries SCX.ai's old ratesHow it solves it:
scx-ai/Qwen3.8-Maxto SCX.ai's current ratesIntentional product change:
scx-ai/Qwen3.8-Maxspend is now reported at 1.408 / 4.235 / 0.176 USD per 1M input, output and cached tokens, down from 1.65 / 4.99 / 0.21Rows
Rates are SCX.ai's API prices in USD per 1M tokens. Context windows come from SCX.ai's model listing. Output limits are the ones the endpoint enforces where it validates
max_tokens(GLM-5.2-Fast and GLM-5.3 reject anything above 131072) and the published limit otherwise. Vision, JSON schema, tool calling and prompt caching were each checked with live requests toapi.scx.aion every model except GLM-5.3-Fast (see Caveats)scx-ai/DeepSeek-V4.1-flashscx-ai/GLM-5.2-Fastscx-ai/GLM-5.3scx-ai/GLM-5.3-Fastscx-ai/GLM-5.3-Flashscx-ai/Kimi-K3scx-ai/Qwen3.8-Max(updated)All of them support tool calling, reasoning and prompt caching. GLM-5.3 and DeepSeek-V4.1-flash are marked without JSON schema support because the endpoint does not honour
response_formatof typejson_schemaon them, while plain JSON mode worksThe page listing these models on docs.litellm.ai is updated in BerriAI/litellm-docs#2204
I work at SCX.ai
User Flow
Before: a developer calling a new SCX.ai model with tools through the proxy gets a 400 and no spend is recorded
"model": "scx-ai/GLM-5.3"and atoolsarrayUnsupportedParamsError: scx-ai does not support parameters: ['tools']x-litellm-response-costheader reads 0, and GET http://localhost:4000/model/info shows no prices for the modelAfter: the same request returns a tool call and is charged at SCX.ai's rates
"model": "scx-ai/GLM-5.3"and atoolsarrayget_weathertool callx-litellm-response-costheader reads 0.0002656, which is 160 x 0.93 + 40 x 2.92 USD per 1M tokens, and GET http://localhost:4000/model/info shows those pricesPre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
uv run pytest tests/unit/<your_test_file>.py -v. Leave the suites (make test-unit-*,make test-unit) to CI: it finishes in ~15 minutes where a laptop takes an hour or more@greptileaito re-request a review after pushing changes)Delays in PR merge?
If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).
Screenshots / Proof of Fix
Both runs use this config, with
SCX_API_KEYand a randomLITELLM_MASTER_KEYexported, andLITELLM_LOCAL_MODEL_COST_MAP=Trueso the proxy reads the cost map from the checkoutBefore (4df5006)
Model info
Tool call and spend
After (5c4d4e8)
Model info
Tool call and spend
Type
New Feature
Caveats (if any)
Low
Final Attestation