How-To Series · Episode 54 / 59 · Module 8: Provider Plumbing

Hermes · Credential Pools

Multiple keys for one provider. When one hits a rate limit, Hermes rotates to a healthy key, no switch.

After this videoYou can now pool keys per provider and auto-rotate to dodge rate limits.

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.

About these resources. Every command comes from the Credential Pools doc.

New words here · Plain English

one sentence each · full glossary
Credential poolA set of API keys for the same service. When one hits its limit, Hermes automatically switches to the next.
Rate limitA cap on how many requests you can send per minute or day. Pools rotate keys to avoid hitting this.

Sources · What this video distills

1 docs page · every command below traces to one of them
Primary · pool model, hermes auth, auto-discovery, rotation strategies, error recovery, subagent sharing
Credential Pools
Read ↗

Commands shown · Copy and paste

each shows the source doc it came from
hermes auth add openrouter --api-key sk-or-v1-...
Inspect the poolfrom source ↗
hermes auth list
Strategy (config.yaml)from source ↗
credential_pool_strategies: { openrouter: round_robin }

Going deeper · Related Hermes docs

further reading · not sources of facts shown above

Next in the series · Episodes that build on this

E55
Configuring Models
E53
Fallback Providers
E52
Provider Routing