Hermes Agent's key pool is suitable for solving problems such as accidental 429, quota exhaustion, and OAuth expiration on the same provider. Instead of letting you bypass platform rules, it puts multiple legal credentials into a pool and lets Hermes automatically switch health credentials if it fails.
How to add
_CODE_BLOCK_0___If there is already a key in.env, Hermes will automatically recognize it as a 1-key pool. You only need to replenish the second and third credentials.How to choose a rotation strategy
_CODE_INLINE_2__: The default policy, use the first health key first.round_robin: Multiple keys rotate evenly.- least_used : Priority is given to keys with fewer requests.
- _CODE_INLINE_5__: Select health credentials randomly. In a word: - When using Hermes Agent at high frequencies, the key pool is more stable than changing keys manually, so it is best to equip it with fallback_model. When should I have fallback
key pool only rotates credentials within the same provider. If the entire provider is not available, or if all keys are exhausted,fallback_modelwill need to take over. Common combinations are OpenRouter or Nous for the main model and another provider for the alternate model. In this way, 429, 402, and 401 each have processing paths, so that the entire round of tasks will not be directly cut off after a failure.Official open source address:
https://github.com/NousResearch/hermes-agent; Official document entry:https://hermes-agent.nousresearch.com/_.
