feat: add OrcaRouter as a named LLM provider - #181
Open
XiaoHuo888-hue wants to merge 1 commit into
Open
XiaoHuo888-hue wants to merge 1 commit into
XiaoHuo888-hue wants to merge 1 commit into
Conversation
Add OrcaRouter to the LLM provider registry, mirroring how existing providers are wired: a preconfigured endpoint (https://api.orcarouter.ai/v1), default model deepseek/deepseek-v4-flash, sk-orca- key prefix, provider logo, form schema keys, and self-hosted settings support. Co-Authored-By: Claude <noreply@anthropic.com>
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
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 OrcaRouter as a named provider. With one API key, users get 150+ models from OpenAI, Anthropic, Google, DeepSeek, Qwen, MiniMax and xAI behind a single endpoint. Because the LLM provider dispatcher is a thin base-URL swap, any TaxHacker pipeline that uses it also inherits OrcaRouter's gateway-level, zero-trust security controls for AI agents, with no application code changes. The gateway screens every prompt and response and governs every tool call on a default-deny basis, across four layers:
I'm an engineer on the OrcaRouter team.
What this changes
OrcaRouter becomes a first-class provider in the LLM settings, mirroring how the existing providers are registered:
lib/llm-providers.ts: neworcarouterentry in thePROVIDERSregistry, preconfigured endpointhttps://api.orcarouter.ai/v1, default modeldeepseek/deepseek-v4-flash,sk-orca-...key prefix, and a link to the OrcaRouter console.ai/providers/llmProvider.ts:"orcarouter"added to theLLMProviderunion;requestLLMUnifiedandtestLLMProviderdispatch it throughChatOpenAIwith the preconfigured base URL (overridable via the settings form).forms/settings.ts/models/settings.ts: the fourorcarouter_*setting keys added to the form schema,SELF_HOSTED_ONLY_SETTINGS, andgetLLMSettings()so the provider is saved, loaded, and picked up by the analysis router (including the default provider order).components/settings/llm-settings-form.tsx: OrcaRouter appears in the default provider order so it shows up in the LLM settings UI out of the box.public/logo/orcarouter.svg: provider logo..env.example: documentsORCAROUTER_MODEL_NAME/ORCAROUTER_API_KEY.How to use it
sk-orca-).deepseek/deepseek-v4-flash; you can override both model and endpoint).Verification
npm run lint→ clean on changed filesnpm run test(vitest) → all passnpx tsc --noEmit→ no errors on changed filesorcarouterprovider path (ChatOpenAI→https://api.orcarouter.ai/v1, modeldeepseek/deepseek-v4-flash) with a realsk-orca-key → returned a valid completion