What problem does it solve? Hermes Agent model configuration spans primary providers, named custom providers, and fallback chains across multiple profiles and cron jobs, and misconfigurations like silent fallback traps, truncated API keys, and stale credential pool entries cause hidden billing spikes and HTTP 401/404 failures that are hard to diagnose from config files alone. ## Core Features & Use Cases - Three-Tier Provider Configuration: Set up primary models, named custom_providers (OpenAI or Anthropic wire protocol), and fallback_providers chains in config.yaml with correct YAML structure. - Silent Fallback Detection: Audit agent.log to count real provider failures versus successes, revealing when a broken primary routes 100% of traffic to an expensive fallback like OpenRouter. - Credential & Auxiliary Fixes: Detect truncated API keys containing literal '...', clean stale credential_pool entries in auth.json, and fix HTTP 401 errors on auxiliary features like title generation and compression. - Use Case: A user notices high OpenRouter billing after switching to DashScope. The audit procedure reveals 145 DashScope 404 failures and 3,834 OpenRouter successes in agent.log, pinpointing an endpoint/model-name mismatch as the root cause. ## Quick Start Ask the agent to audit which model provider is actually serving traffic across all Hermes profiles and explain any unexpected fallback usage.
