docs(ops): document OrcaRouter as a LiteLLM model provider - #2354
Open
Marc-oss-hub wants to merge 1 commit into
Open
docs(ops): document OrcaRouter as a LiteLLM model provider#2354Marc-oss-hub wants to merge 1 commit into
Marc-oss-hub wants to merge 1 commit into
Conversation
Add an OrcaRouter subsection to the LiteLLM embeddings provider list and a row to the entity-resolution model strings table. OrcaRouter is an OpenAI-compatible routing gateway; the docs show the namespaced model-id form (openai/openai/...) with api_base set to https://api.orcarouter.ai/v1. 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.
Summary
Adds OrcaRouter to the LiteLLM provider docs. OrcaRouter is an OpenAI-compatible model routing gateway that exposes models from OpenAI, Anthropic, Google, DeepSeek, Qwen and others behind a single endpoint and API key. 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.
I'm an engineer on the OrcaRouter team.
What this changes
docs/src/content/docs/ops/litellm.mdx: adds an### OrcaRoutersubsection under "Supported providers", alongside the existing OpenAI / Azure / Gemini entries, showing theLiteLLMEmbedderwiring withapi_baseandapi_key.docs/src/content/docs/ops/entity_resolution.mdx: adds an OrcaRouter row to theLlmPairResolvermodel strings table, with a one-line note on the namespaced model-id form.How to use it
The outer
openai/prefix selects the OpenAI-compatible protocol; the inneropenai/…is the router's namespaced model id (passed through verbatim). The same shape works forLlmPairResolver(model="openai/openai/gpt-5.5", ...)in entity resolution.Verification
npm run buildindocs/passes (98 pages; the 5 pre-existingmissing .md twinnotices forindex.mdxpages are unchanged by this PR).https://api.orcarouter.ai/v1with ansk-orca-key:litellm.aembedding("openai/openai/text-embedding-3-small", api_base=..., api_key=...)→ 200, 1536-dim vector.litellm.acompletion("openai/openai/gpt-5.5", ...)→ 200.text-embedding-3-small(noopenai/prefix) → 503No available channel, which is why the docs show the namespaced form.