Skip to content

Add Novita as a fourth LLM fallback provider - #475

Open
jax-novita wants to merge 3 commits into
NateBJones-Projects:mainfrom
jax-novita:add-novita-provider
Open

Add Novita as a fourth LLM fallback provider#475
jax-novita wants to merge 3 commits into
NateBJones-Projects:mainfrom
jax-novita:add-novita-provider

Conversation

@jax-novita

Copy link
Copy Markdown

Contribution Type

  • Integration (/integrations)

What does this do?

Adds Novita as a fourth LLM fallback provider (alongside OpenRouter, OpenAI, Anthropic) in integrations/smart-ingest and integrations/entity-extraction-worker. Novita exposes an OpenAI-compatible chat completions endpoint, so the new callNovita() follows the same structure as the existing callOpenAI().

Requirements

  • Novita API key (NOVITA_API_KEY), optional — only needed if you want Novita as one of your configured LLM providers.

Checklist

  • I've read CONTRIBUTING.md
  • My contribution has a README.md with prerequisites, step-by-step instructions, and expected outcome (updated existing READMEs to mention Novita)
  • My metadata.json has all required fields (unchanged; this PR extends an existing integration rather than adding a new one)
  • If my contribution depends on a skill or primitive, I declared it in metadata.json and linked it in the README (n/a)
  • I tested this on my own Open Brain instance (live smoke test against the Novita chat completions endpoint; deno check and deno lint pass with no new errors/warnings in both integrations)
  • No credentials, API keys, or secrets are included

Both smart-ingest and entity-extraction-worker already fall back
through OpenRouter -> OpenAI -> Anthropic. Add Novita as a fourth
option using its OpenAI-compatible chat completions endpoint, so
users who prefer or already hold a Novita key can configure it
without needing OpenRouter/OpenAI/Anthropic as well.
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.
deepseek/deepseek-v4-flash-0731 is no longer the live catalog's
current DeepSeek general flagship; deepseek/deepseek-v4-pro is.
@github-actions github-actions Bot added the integration Contribution: MCP extension or capture source label Aug 10, 2026
@github-actions

Copy link
Copy Markdown

Hey @jax-novita — welcome to Open Brain Source! 👋

Thanks for submitting your first PR. The automated review will run shortly and check things like metadata, folder structure, and README completeness. If anything needs fixing, the review comment will tell you exactly what.

Once the automated checks pass, a human admin will review for quality and clarity. Expect a response within a few days.

If you have questions, check out CONTRIBUTING.md or open an issue.

@jax-novita

Copy link
Copy Markdown
Author

Hi, I checked the failed OB1 PR Gate run.

The failure appears to come from the repository workflow rather than from this PR's code. The workflow is triggered by pull_request_target and attempts to check out the fork head branch, which GitHub refuses for security reasons:

Refusing to check out fork pull request code from a pull_request_target workflow.

There are also warnings about the Node.js 20 runtime used by actions/checkout@v4 / actions/upload-artifact@v4, and the artifact upload step reports that gate-artifact/ does not exist after the failed review step.

Could you please take a look at the workflow configuration? I believe the PR should be re-run after the workflow is adjusted. I have not changed the application code since the failure is occurring before the review checks can run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integration Contribution: MCP extension or capture source

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant