feat: add OrcaRouter as a built-in OpenAI-compatible provider - #941
Open
Marc-oss-hub wants to merge 1 commit into
Open
feat: add OrcaRouter as a built-in OpenAI-compatible provider#941Marc-oss-hub wants to merge 1 commit into
Marc-oss-hub wants to merge 1 commit into
Conversation
Add a data-driven ProviderSpec entry for OrcaRouter, mirroring the OpenRouter entry: ORCAROUTER_API_KEY / ORCAROUTER_BASE_URL env chain, default base https://api.orcarouter.ai/v1, OpenAI-compatible transport. Covers the registry-catalog unit test, a live provider test (skips without a key), and the WebUI built-in catalog + provider-id docs.
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
1 participant
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 built-in OpenAI-compatible provider, mirroring how OpenRouter is wired into the data-driven provider layer.
OrcaRouter is an OpenAI-compatible gateway that reaches 100+ model providers through a single endpoint. It also runs gateway-level, zero-trust security for AI agents on the same endpoint — screening every prompt/response and governing every tool call on a default-deny basis, with no application code changes.
Changes
ms_agent/llm/spec.py: neworcarouterProviderSpec(openai_compattransport,ORCAROUTER_API_KEY/ORCAROUTER_BASE_URLenv chain, default basehttps://api.orcarouter.ai/v1), mirroring theopenrouterentry — one data-driven spec, no new classtests/llm/test_provider_layer.py:orcarouteradded toEXPECTED_PROVIDERS+ spec-shape testtest_orcarouter_uses_orca_envtests/llm/test_provider_router_live.py:orcarouterinPROVIDERS(orcarouter/auto) +test_orcarouterlive test (skips withoutORCAROUTER_API_KEY, same pattern as OpenRouter)webui/backend/tests/test_providers.py:orcarouteradded to_EXPECTED_BUILTINS(WebUI "fill an API key" catalog)webui/backend/.env.example:orcarouterlisted among known registry idsVerification
orcarouterresolves with the expected transport / env chain / default base URL;list_providers()includes it; case-insensitive lookup workshttps://api.orcarouter.ai/v1withorcarouter/auto: non-stream completion and a tool call (mkdir→{"dir_name":"demo"}) both returned (auto-routed todeepseek-v4-pro/MiniMax-M2.7across probes)py_compile+flake8clean on changed files; formatting matches the adjacentopenrouterentryI'm an engineer on the OrcaRouter team.