Skip to content

feat(config): add OrcaRouter gateway template as alternative LLM provider - #473

Open
XiaoHuo888-hue wants to merge 1 commit into
TeamWiseFlow:masterfrom
XiaoHuo888-hue:add-orcarouter-provider
Open

feat(config): add OrcaRouter gateway template as alternative LLM provider#473
XiaoHuo888-hue wants to merge 1 commit into
TeamWiseFlow:masterfrom
XiaoHuo888-hue:add-orcarouter-provider

Conversation

@XiaoHuo888-hue

Copy link
Copy Markdown

Summary

Add OrcaRouter as an alternative LLM gateway provider for xiaobei, mirroring the existing openclaw-awk.json template.

OrcaRouter is an OpenAI-compatible model gateway: one key routes DeepSeek, GLM, Qwen, Claude, Gemini and other mainstream models, with a single OpenAI-compatible endpoint (https://api.orcarouter.ai/v1). 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

  • config-templates/openclaw-orcarouter.json (new): alternative OpenClaw config template with a named orcarouter provider — baseUrl: https://api.orcarouter.ai/v1, api: openai-completions, apiKey: ${ORCAROUTER_API_KEY}, and curated models (orcarouter/auto, orcarouter/fusion, orcarouter/fusion-mini, orcarouter/fusion-flash, orcarouter/free, orcarouter/open-code, orcarouter/code-review). Structured exactly like the existing openclaw-awk.json/openclaw.json templates.
  • docker/docker-entrypoint.sh: made API-key rendering provider-aware. Each configured provider now gets its own key env var (AWK_API_KEYbailian-token-plan/awk, ORCAROUTER_API_KEYorcarouter), and the required-key check validates whichever provider the active openclaw.json actually uses (so the OrcaRouter template no longer requires AWK_API_KEY).
  • docker/docker-compose.yml / docker/.env.example: pass through ORCAROUTER_API_KEY.
  • README.md, config/README.md, config/.env.template: document the OrcaRouter alternative template and key.

Usage

Copy config-templates/openclaw-orcarouter.json to ~/.openclaw/openclaw.json (or swap it into the Docker seed), set ORCAROUTER_API_KEY (starts with sk-orca-) in .env, and start as usual.

Verification

  • JSON valid (all templates parse).
  • Entrypoint syntax validated; provider-aware key check + rendering tested end-to-end with a real openclaw.json from the template.
  • No CRLF; git diff --check clean.
  • Live API check: POST https://api.orcarouter.ai/v1/chat/completions with model: orcarouter/auto using a real key → HTTP 200, OpenAI-compatible response.

Disclosure: I'm an engineer on the OrcaRouter team.

…ider

Add config-templates/openclaw-orcarouter.json mirroring the existing
openclaw-awk.json structure: an OpenAI-compatible provider pointing at
https://api.orcarouter.ai/v1 with models orcarouter/auto, fusion,
fusion-mini, fusion-flash, free, open-code and code-review, using the
openai-completions API adapter and ORCAROUTER_API_KEY env var.

Also:
- docker-entrypoint.sh: make API-key rendering provider-aware so each
  configured provider gets its own key (AWK_API_KEY for
  bailian-token-plan/awk, ORCAROUTER_API_KEY for orcarouter), and
  validate the required key based on which provider the active
  openclaw.json actually uses.
- docker-compose.yml / docker/.env.example: pass through
  ORCAROUTER_API_KEY.
- README / config README / env templates: document the OrcaRouter
  alternative template.

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: XiaoHuo888-hue <jinhao.song@myflashcloud.com>
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


XiaoHuo888-hue seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants