Key pools

Providers limit how fast one real key can go. A key pool (Team: up to 5 real keys, Business: up to 10) lets one ghost key send each request with the next real key in turn, so the provider's limit counts once per real key. Your app keeps the same ghost key.

• Add real keys under Real key → Key pool, or POST /keys/:id/pool with { real_key, label? }. Use keys from other accounts or projects: two keys of one account usually share one limit, and the same key twice is refused.
• Like a replacement real key, a new one starts being used after the safety hour, or a second admin's approval for production keys, and your team is alerted. Taking one out (DELETE /keys/:id/pool/:pool_id) applies at once.
• When one says “too many requests”, the request goes to the next real key at once, and the busy one rests for as long as the provider asked (30 seconds otherwise). Only when every real key is busy does the 429 reach your app.
• A real key the provider keeps refusing (401 or 403 three times in a row) is taken out of turn, and you get an alert. The others carry on.
• Activity and each request's details say which real key answered; the pool shows each key's requests and 429s today.