Skip to content

support multiple API keys for rotation and failover#4

Open
swizardlv wants to merge 3 commits intozhangrr:mainfrom
swizardlv:main
Open

support multiple API keys for rotation and failover#4
swizardlv wants to merge 3 commits intozhangrr:mainfrom
swizardlv:main

Conversation

@swizardlv
Copy link
Copy Markdown

to avoid 429 too many request error.

swizardlv and others added 2 commits February 18, 2026 23:14
- Add keyManager with rotation strategies: round_robin, random, least_used
- Support multiple keys via nvidia_keys config or PROVIDER_API_KEYS env
- Auto-retry with next key on HTTP 429 (rate limit) errors
- Update README with configuration examples

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Fix: The proxy uses Go 1.22+ method-aware routing syntax ("POST /v1/messages").
On Go < 1.22, this is treated as a literal path causing all /v1/messages
requests to fall through to the health endpoint.

Changes:
- Add checkGoVersion() function that exits with clear error if Go < 1.22
- Add Requirements section to README documenting Go 1.22+ requirement

Resolves: POST /v1/messages returning health response on Go < 1.22

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant