Right now my ENTIRE APPLICATION IS OFFLINE and it has been for several minutes because your stupid API doesn’t know I already topped up my credits. This happens very frequently. I’ll run ouf of credits, recharge, but the API responses keep returning the quota reached for UPWARDS OF 30 MINUTES after I recharge.
It takes a while to both shut off and turn back on an organization. And yes, it would be better if it was instantaneous either way - so a compromised account can’t be run negative into the thousands of dollars.
The amount of time that you got in unfunded API use is the equivalent of the delay in turning it on.
If you purchase credits before the balance goes to zero, you should not have any lag in being able to spend them.
I understand. If only we had a way to programatically know our current credit balance, I’d 100% setup an alert for when we’re about to run out of credits. We usually try to keep it in check but sometimes we’ll have a spike in usage and it will run out. I wish the API would expose the credit balance but maybe i’m stupid but it’s almos like they don’t want you to have it.
Understood.
The closest that OpenAI has is a spend alert, based on a monthly usage. Send an email when the usage has increased by an amount, instead of when the balance has instead dropped.
In addition to the alert feature you can also enable auto-recharge in the billing settings.
The account will be topped up when a pre-determined threshold is hit and you can manage risk by setting a maximum amount for recharges.
This should effectively prevent the org from running out of credits and prevent billing related outages.