Credential Pools
Credential Pools
Start with meaning, then move to detail.
This lesson explains Credential Pools as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect How It Works, Quick Start, Interactive Management, then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand Credential Pools without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Pool multiple API keys or OAuth tokens per provider for automatic rotation and rate limit recovery.
What does the source say, and in what order?
- 01How It Works
Start here to understand the core idea or structure.
- 02Quick Start
Read this after the foundation, then connect it to the previous step.
- 03Interactive Management
Read this after the foundation, then connect it to the previous step.
- 04CLI Commands
Read this after the foundation, then connect it to the previous step.
- 05Rotation Strategies
Read this after the foundation, then connect it to the previous step.
- 06Error Recovery
Read this after the foundation, then connect it to the previous step.
- 07Custom Endpoint Pools
Read this after the foundation, then connect it to the previous step.
- 08Auto-Discovery
Read this after the foundation, then connect it to the previous step.
- 09Delegation & Subagent Sharing
Read this after the foundation, then connect it to the previous step.
- 10Thread Safety
Finish here to verify the result and special cases.
Copy only after you understand the effect.
Your request
→ Pick key from pool (round_robin / least_used / fill_first / random)
→ Send to provider
→ 429 rate limit?
→ Plan/usage limit reached (e.g. ChatGPT/Codex "usage limit reached")?
→ Rotate to next pool key immediately (no retry — the cap won't clear on retry)
→ Generic / transient 429?
→ Retry same key once (transient blip)
→ Second 429 → rotate to next pool key
→ All keys exhausted → fallback_model (different provider)
→ 402 billing error?
→ Immediately rotate to next pool key (1h cooldown)
→ 401 auth expired?
→ # Add a second OpenRouter key
hermes auth add openrouter --api-key sk-or-v1-your-second-key
# Add a second Anthropic key
hermes auth add anthropic --type api-key --api-key sk-ant-api03-your-second-key
# Add an Anthropic OAuth credential (requires Claude Max plan + extra usage credits)
hermes auth add anthropic --type oauth
# Opens browser for OAuth loginhermes auth listRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.