openclaw - 💡(How to fix) Fix Support OpenRouter provider routing / extra_body in model config [1 comments, 2 participants]

TL;DR

To restrict OpenRouter providers for specific models in OpenClaw, consider adding an options or extra_body sub-key to model entries in openclaw.json to pass provider preferences.

Guidance

• Evaluate Option A by adding an openrouter object with a provider sub-key to model entries, specifying order, ignore, and allow_fallbacks preferences.
• Assess Option B by adding an extra_headers object to model entries, setting the X-Title-Preset header to support Presets.
• Verify the effectiveness of these options by testing model requests with restricted providers.
• If the proposed solutions are not feasible, use the account-wide Default Provider Preferences in the OpenRouter dashboard as a temporary workaround, although it lacks model-level granularity.

Example

"models": {
  "openrouter/deepseek/deepseek-v4-pro": {
    "openrouter": {
      "provider": {
        "order": ["GMICloud", "AtlasCloud", "Parasail"],
        "ignore": ["SiliconFlow", "NovitaAI"],
        "allow_fallbacks": false
      }
    }
  }
}

Notes

The proposed solutions require updates to the openclaw.json configuration file and may need adjustments based on the specific OpenClaw and OpenRouter versions being used.

Recommendation

Apply workaround: Use Option A or Option B to add provider preferences to model entries, as it provides a more granular control over OpenRouter providers compared to the account-wide default preferences.