Hi all, sorry if this has already been covered but I was looking for some reassurance regarding Pay As You Go. Can I confirm that once you reach 0 credits the api requests stop working and you won’t be charged further.
I think I saw a previous post where balances had gone into the negative, obviously if I am using PAYG I want the requests to stop once the ballance hits 0. Also i thought there was a hard limit option that you could set? It turns out its a monthly limit/budget and even that states that it can go over the threshold set by the user.
Just looking to work to a budget and dont want any unexpected overspend.
Running out of credits and not having recharge on is the only way that your organization can be limited. There is no hard limit setting or budget limit that does anything other than send you an email based on monthly usage. It seems this being a usage cutoff was purposefully removed, and no complaints have reversed the decision.
It also can take a while for an organization to be shut off, historically many hours or a large part of a day. Your organization account will indeed go negative and this will create a monthly bill that you must separately pay if it is large, or your purchase of more credits may be increased to directly fund this deficit and more in order to get the organization reactivated.
The API system is more “pay before you go”, considering that you must prepurchase credits to fund future calls (unless you have a big enterprise account with undisclosed terms). So you will want to use best practices - know your accumulating costs by token usage in responses made only through your own backend, and by use of the org admin endpoints for monitoring the API platform; know your API key usage sites and keep them as secure as a banking password.