feat: add OrcaRouter as an OpenAI-compatible provider preset - #27
Open
nissrin2020ali-ux wants to merge 1 commit into
Open
feat: add OrcaRouter as an OpenAI-compatible provider preset#27nissrin2020ali-ux wants to merge 1 commit into
nissrin2020ali-ux wants to merge 1 commit into
Conversation
Add OrcaRouter (https://api.orcarouter.ai/v1) to the provider presets in the settings page, mirroring the existing OpenRouter entry. OrcaRouter is an OpenAI-compatible gateway, so it works with the existing OpenAI-compatible interface without any backend changes. 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.
MuseAI's README describes it as "a local AI interaction world that keeps your characters, settings, memories, and relationships in one place," built for people who "prefer keeping stories, settings, and sessions on their own computer while using their own API key." Users already bring their own key and plug into OpenAI-compatible providers — DeepSeek, Kimi, Zhipu, and proxy services — by entering a base URL, key, and model name in Settings.
For a MuseAI user who wants a single provider namespace across many models without juggling several upstream keys, the settings page already ships presets such as OpenRouter. This PR adds OrcaRouter as a first-class preset next to it, so those users can reach the gateway with one click instead of treating it as an anonymous Custom base URL.
OrcaRouter is an OpenAI-compatible AI gateway built for both models and agents. Like OpenRouter, it exposes a provider/model namespace across many models — but it also combines adaptive routing, automatic failover, zero-markup inference, observability, guardrails, and agent-tool governance behind the same endpoint. Adding orcarouter as a first-class provider means this project's users can use that stack directly, without treating OrcaRouter as an anonymous custom base URL.
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.
What changed
MODEL_PROVIDER_PRESETSinsrc/pages/Settings.tsx, mirroring the existing OpenRouter preset:OrcaRouterhttps://api.orcarouter.ai/v1OpenAI-compatibleBecause OrcaRouter speaks the OpenAI-compatible protocol, the preset flows through MuseAI's existing OpenAI-compatible request path (
test_llm_connectionand the chat/agent sessions) — no backend changes are required.Verification
npm run test— 285 tests passnpm run build(tsc + vite build) — succeedshttps://api.orcarouter.ai/v1/chat/completionsusing the same streaming SSE format MuseAI's connection test reads — HTTP 200Discord: discord.gg/YEubt8enRA · X: https://x.com/OrcaRouter
I'm an engineer on the OrcaRouter team.