wiki: publish pending edits (2026-10-20)

This commit is contained in:
Tony0410
2026-10-20 18:38:11 +08:00
parent 667ab7f41d
commit fbd4f297eb
46 changed files with 1012 additions and 197 deletions
+10 -2
View File
@@ -3,8 +3,8 @@ title: OpenRouter
type: system
status: active
created: 2026-07-22
updated: 2026-07-22
verified_on: 2026-07-22
updated: 2026-10-20
verified_on: 2026-10-20
confidence: medium
tags: [system, openrouter, provider]
sources: [raw/configs/hermes-config-sanitized.txt]
@@ -21,6 +21,14 @@ Primary key, fallback models, rate limits.
OpenRouter is not configured as a standalone provider in `~/.hermes/config.yaml` `custom_providers`.
OmniRoute’s catalog includes provider names and model IDs consistent with OpenRouter-style slugs, but live routing via OpenRouter directly is not present in current Hermes config.
> **Re-verified 2026-10-20 — the claim above still holds.** `custom_providers` in
> `/home/hermes/.hermes/config.yaml` is a list of exactly five entries:
> `litellm`, `guacano`, `Omniroute:20128`, `command-code`, `omni-101`. There is **no `openrouter`
> entry**. OpenRouter-style slugs (`openrouter/auto`, `freeapi/openrouterfree`,
> `kilo-openrouter-auto`, `or-openrouter-fusion`, and many more) exist only inside the **OmniRoute
> model catalog**, not as directly-routable Hermes providers. Routing to OpenRouter therefore still
> goes through OmniRoute, exactly as recorded here.
## History
- **User-provided:** Previously used; now largely replaced by LiteLLM and OmniRoute paths
- **Verified:** Decision page `keep-openrouter-as-fallback` exists, indicating retain intent