Hermes · Credential Pools
Multiple keys for one provider. When one hits a rate limit, Hermes rotates to a healthy key, no switch.
A credential pool is several keys (or OAuth tokens) for the same provider. When one hits a rate limit or billing quota, Hermes rotates to the next healthy key without switching providers, your session never notices. Pools are tried first; only when every key is exhausted does Hermes fall through to a different provider. Add keys with hermes auth add (env vars and OAuth logins are auto-discovered too); inspect with hermes auth list. Pick a rotation strategy: fill_first (default), round_robin, least_used, or random. Error recovery is automatic, a rate limit retries then rotates (1h cooldown), a billing error rotates now (24h), an expired token refreshes first. Subagents inherit the pool.
Sources · What this video distills
1 docs page · every command below traces to one of themCommands shown · Copy and paste
each shows the source doc it came fromhermes auth add openrouter --api-key sk-or-v1-...hermes auth listcredential_pool_strategies: { openrouter: round_robin }