2.1 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| OpenRouter | system | active | 2026-07-22 | 2026-10-20 | 2026-10-20 | medium |
|
|
OpenRouter
Purpose
Fallback model provider.
Location
Remote service; API token store.
Current configuration
Primary key, fallback models, rate limits.
Current state as of 2026-07-22
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_providersin/home/hermes/.hermes/config.yamlis a list of exactly five entries:litellm,guacano,Omniroute:20128,command-code,omni-101. There is noopenrouterentry. 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-fallbackexists, indicating retain intent - Inferred: Multiple backups before model/routing changes imply OpenRouter role changed during prior config iterations
- Unknown: Exact date OpenRouter was replaced or partially deprecated; exact models that were available
Connected systems
Known issues
- Replaced: legacy Hermes autos not persistent, prompting Hermes Agent, which blocks attribution.
Change history
- Pre-2026-07-20: OpenRouter provisioning active in some form
- 2026-07-20: Prior model-fix backup suggests routing changes around this time