openclaw - 💡(How to fix) Fix [Feature]: Bundle OrcaRouter as a provider extension

Summary

Add OrcaRouter as a bundled provider extension at extensions/orcarouter/, mirroring the existing OpenRouter / Kilocode / LiteLLM / Vercel AI Gateway / Cloudflare AI Gateway extensions.

Problem to solve

OpenClaw users who want adaptive cross-vendor LLM routing currently have several bundled options (OpenRouter, Kilocode, LiteLLM, Vercel AI Gateway, Cloudflare AI Gateway). OrcaRouter is functionally in the same category but requires a separate openclaw plugins install clawhub:... step. Users browsing the bundled providers list won't see it next to peer meta-routers, and the install gap means lower discovery for an option that fits the same use case.

Proposed solution

Mirror the extensions/openrouter/ shape, scoped to chat completion for v1:

• extensions/orcarouter/{index,onboard,provider-catalog}.ts + openclaw.plugin.json + package.json
• Manifest with modelIdNormalization.prefixWhenBare: "orcarouter", setup.providers[{authMethods:["api-key"], envVars:["ORCAROUTER_API_KEY"]}], providerAuthChoices wizard config
• HTTP-Referer + X-Title attribution headers on verified api.orcarouter.ai routes
• Dynamic + static catalog (orcarouter/auto + flagship models, free-form orcarouter/<vendor>/<model> via resolveDynamicModel)

The same code is already shipped as a 3rd-party plugin and verified end-to-end:

• Source: https://github.com/Continuum-AI-Corp/openclaw-orcarouter-plugin
• ClawHub: https://clawhub.ai/plugins/@continuum-ai-corp/openclaw-orcarouter
• Install today: openclaw plugins install clawhub:@continuum-ai-corp/openclaw-orcarouter

Alternatives considered

Keep it on ClawHub only — current state, works fine. Tradeoff is discovery: users browsing the bundled provider list won't see OrcaRouter next to peer meta-routers, and an extra install step is required.

Impact

• Affected: OpenClaw users who want adaptive cross-vendor routing and are evaluating between OpenRouter / Kilocode / LiteLLM / etc.
• Severity: Low-medium — extra install step is one command, not a blocker
• Frequency: Per-user one-time during onboarding
• Consequence: Lower discoverability vs. peer meta-routers that ship bundled

Evidence/examples

7 meta-routers are already bundled in extensions/:

Our v0.1.0 ClawHub plugin is chat-only and small (~600 LOC) — image/video/music/STT can follow incrementally if there's interest. End-to-end install + agent call against [email protected] verified locally (unit tests + live test + real-user e2e through openclaw plugins install ... && openclaw onboard ... && openclaw agent ...).

Additional information

I'm an engineer on the OrcaRouter team. Happy to draft a PR with the source files if there's interest, or keep the ClawHub-only path if maintainers prefer all newer meta-routers stay in the community channel. Aware of CONTRIBUTING.md L95 — opening this issue first per the documented "GitHub Issue or Discord" path.