feat(llm): add Novita AI as a built-in provider - #755
Open
jax-novita wants to merge 3 commits into
Open
Conversation
Novita's endpoint (https://api.novita.ai/v3/openai) is OpenAI-compatible, so it registers like the other OpenAI-protocol providers (deepseek, kimi, z-ai, ...). Adds the registry entry, the matching name in the provider-order test, and the provider table in the en/zh/ja configuration docs. Model ids are taken from the live /v3/openai/models endpoint.
The registry entry, tests-adjacent docs tables (en/ja/zh configuration.md) used https://api.novita.ai/v3/openai. That path still resolves today, but Novita's current documentation (novita.ai/docs/guides/llm-api) no longer shows it; the current documented OpenAI-compatible endpoint is https://api.novita.ai/openai. Verified live 2026-08-01: both paths return identical /models and /chat/completions results, so this is a stale-citation fix, not a functional break.
The models listed for Novita were older ids that no longer reflect what the platform leads with. Point the recommendations at the three current flagships instead, each verified against api.novita.ai: moonshotai/kimi-k3 1M context, native vision zai-org/glm-5.2 1M context, long-horizon agentic work deepseek/deepseek-v4-flash-0731 1M context, cheapest of the three Context windows, output limits, input modalities and pricing were taken from the live /openai/v1/models response rather than carried over.
|
jax-novita 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. |
Contributor
|
✅ OpenCodeReview: Review complete: 0 finding(s) across 1 selected item(s). |
wu21-web
approved these changes
Aug 6, 2026
Contributor
|
@jax-novita Maybe you forgot to link this pull request to issue #673 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
novitato the built-in provider registry ininternal/llm/providers.go. Novita's endpoint is OpenAI-compatible, so it registers the same way as the other openai-protocol providers (deepseek, kimi, z-ai, ...) — no new client code needed.https://api.novita.ai/openai(current documented endpoint)NOVITA_API_KEYenv var (Bearer, OpenAI-compatible default)moonshotai/kimi-k3,zai-org/glm-5.2,deepseek/deepseek-v4-flash-0731— current flagships per Novita's live/openai/v1/modelsAlso updates the provider table in the en/ja/zh configuration docs and the provider-order test in
providers_test.go.Verified against the real Novita endpoint via
ocr llm test(the repo's own connectivity-check command), which returned a live response frommoonshotai/kimi-k3through the configured provider.