Fallback AI API key when the default fails
under review
Tommaso Ercole
Right now the system allows record more than one API key but keep using the default one to categorize emails and perform all the other operations. I tried to understand if there is a valid reason to have more than one API key registered, but I could not find something. Maybe it is because I am still new to the product.
But my idea would be to declare one or more keys as fallbacks, for when the primary begin to fails.
In case of home or unprofessional usage, this can help using free tiers around the various AI providers.
In case of enterprise or professional usage, where people are paying their subscription, maybe it can help as a backup system in case the primary one fails.
I do know that theoretically this should not be a necessity and system should not fail, but should not be a difficult feature to implement and can help in some occasions.
Duda Bardavid
under review