Problem
Problem
Currently, Raven does not support polling or round-robin switching between multiple API accounts. When users have multiple API Keys (possibly from different providers or multiple quota slots from the same provider), each call can only use a fixed Key. There is no way to automatically distribute requests across multiple Keys to spread request pressure or avoid rate limits of a single Key.
Current Behavior
- Only a single account/Key is supported for API calls
- No automatic request distribution across multiple accounts
- No failover mechanism when one account fails
Impact
- A single Key is prone to rate limiting
- Unable to fully utilize multiple paid API quotas
- Lack of high availability in multi-Key scenarios
Proposal
Proposal
- Support configuring multiple accounts (each with URL + Key)
- Support round-robin request distribution between accounts
- When an account returns an error, automatically failover to the next available account
- Display current account and quota status in the TUI
Alternatives considered
No response
Area
Proactivity / scheduling
Additional context
No response
Problem
Problem
Currently, Raven does not support polling or round-robin switching between multiple API accounts. When users have multiple API Keys (possibly from different providers or multiple quota slots from the same provider), each call can only use a fixed Key. There is no way to automatically distribute requests across multiple Keys to spread request pressure or avoid rate limits of a single Key.
Current Behavior
Impact
Proposal
Proposal
Alternatives considered
No response
Area
Proactivity / scheduling
Additional context
No response