docs: add OrcaRouter as an OpenAI-compatible provider example - #1643
Open
bangla24bdrang-lab wants to merge 1 commit into
Open
bangla24bdrang-lab wants to merge 1 commit into
bangla24bdrang-lab wants to merge 1 commit into
Conversation
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.
Summary
Adds OrcaRouter as a documented example of an OpenAI-compatible AI gateway, alongside LocalAI and OpenRouter in
docs/other-models.md.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 it as a documented provider means LLM 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
This updates
docs/other-models.mdwith a new OrcaRouter section showing how to configure OrcaRouter models throughextra-openai-models.yaml, mirroring the existing OpenRouter / AGIone examples.The examples use full OrcaRouter model identifiers:
orcarouter/auto— the adaptive router endpointopenai/gpt-5.5— a vendor-prefixed model identifierWhy
OrcaRouter provides a single OpenAI-compatible endpoint for routing to frontier models through standard Bearer-token authentication, using the same provider/model namespace style as OpenRouter.
This fits the existing "OpenAI-compatible models" documentation pattern used for providers like LocalAI and OpenRouter.
Verification
orcarouter/autoandopenai/gpt-5.5) againsthttps://api.orcarouter.ai/v1with a real API key — both return 200 with a normal chat completion.llm keys set orcarouter, configuredextra-openai-models.yaml,llm modelsshows both models, andllm -m orcarouter-auto '...'/llm -m orcarouter-gpt-5 '...'both returned a completion.1105 passed.black --check,ruff check .,mypy llm, andcog --checkall pass.Disclosure
I'm an engineer on the OrcaRouter team.
Discord: discord.gg/YEubt8enRA · X: https://x.com/OrcaRouter