--- title: Keep OpenRouter as fallback type: decision status: active created: 2026-07-22 updated: 2026-11-11 review_after: 2026-10-20 # was 0001-01-01 (bug), fixed during 2026-07-22 audit; real trigger is conditional, see Revisit when verified_on: 2026-11-11 confidence: high tags: [routing, provider, decision] sources: [] --- # Keep OpenRouter as fallback ## Decision OpenRouter must remain available as a fallback provider, even if a self-hosted router becomes primary. ## Reasons - Free models are important. - Broad model coverage. - Previous migrations disrupted provider availability. - A fallback reduces the chance of Hermes becoming unusable. ## Alternatives considered - Direct providers only - OmniRoute exclusively - Local models exclusively ## Revisit when A self-hosted router has operated reliably for at least 30 days. > **Revisit trigger MET (verified 2026-10-20).** OmniRoute has been the primary router for well over > 30 days — `custom:omni-101` is the pin on effectively every model-calling cron job, and > `Omniroute:20128` is a second live OmniRoute endpoint. The estate has **no standalone OpenRouter > provider**: `custom_providers` in `~/.hermes/config.yaml` holds only `litellm`, `guacano`, > `Omniroute:20128`, `command-code` and `omni-101` (see [[systems/openrouter]]). > > **But the fallback is now provided *through* OmniRoute rather than alongside it** — OpenRouter-style > slugs (`openrouter/auto`, `freeapi/openrouterfree`, `or-openrouter-fusion`, …) are present in the > OmniRoute catalog, so OpenRouter capacity remains reachable without a separate Hermes provider. > > **Status: decision still `active`, but the mechanism it protects has changed.** The intent > (OpenRouter capacity must remain reachable as a fallback) is satisfied via the OmniRoute catalog. > The literal reading — a standalone OpenRouter provider in `custom_providers` — is **not** satisfied > and has not been since at least 2026-07-22. This needs a re-affirmation or a rewrite of the > decision text; it should not simply be left to drift on a 30-day timer. > > Related context: OmniRoute has also been the source of repeated fleet-wide failures — > the 2026-10-14 connection-refused storm, the 2026-10-16/17 and 2026-10-19 resource-pressure 503 > bursts, and the 2026-10-18 degenerate-stream delivery. A single-node fallback posture carries > that concentration risk with it. > **Re-verified 2026-11-11 — the decision still needs the re-affirmation it was flagged for on > 2026-10-20, and the position is unchanged.** `custom_providers` still holds exactly > `litellm`, `guacano`, `Omniroute:20128`, `command-code`, `omni-101` — **no standalone > OpenRouter provider**. OmniRoute remains the primary path (`smart-route` on > `custom:omni-101`), so the "revisit trigger" (a self-hosted router running reliably >30 days) is > still met and the literal reading of the decision is still unsatisfied. Nothing new to decide > here — the page still says what needs a human call. ## Related - [[model-routing]] - [[systems/omniroute]] - [[systems/openrouter]]