Overview
API access is funded with prepaid credits. You buy credit before you use it, and every request draws down the balance at the model’s published rate. Direct endpoints add no platform fee; guarded endpoints add 6.5% on top of that rate. Credits pay for API usage only. Gloo Code is billed separately, through its own monthly allowance and top-ups, and does not draw from these credits. Credits belong to your organization, not to a product, so adding or removing Gloo Code or changing tiers leaves your balance untouched. Enterprise organizations are invoiced under their agreement and do not use prepaid credits.Add credits
Auto-refill
Adding credits
You need to fund your credits at least once before you can create an API key. Until then, the API Keys page sends you here to add credits first. Only organization Admins can add credits. Signing in to Gloo Code from the terminal is separate: it needs a Gloo Code plan, not credits.- Go to the Studio Billing page
- On the Overview tab, click Add credits
- Choose $10, $25, $50 or $100, or enter a custom amount between $1 and $100
- Complete payment on the checkout page
Auto-refill
When it is on, auto-refill charges your saved card when your balance runs low, up to the weekly cap below. The charge is your chosen amount, applied to the card on file. Studio says the charge happens before your balance runs out, and that during heavy use it can happen more than once. Turning it on:- On the Billing page, find the Auto-refill switch on the Wallet card
- Set the amount to add each time ($10 to $100)
- Flip the switch on and confirm in the dialog
- Auto-refill pauses and the Wallet card shows Paused, weekly cap reached
- You get one email telling you auto-refill is paused
- Manual top-ups still work. The cap applies only to automatic charges
- Headroom returns gradually as older charges age past 7 days
This charge cap is separate from the monthly API spend limit covered below, which pauses your API access rather than your card. Once you reach the monthly limit, adding credits manually is not allowed either, because the credit could not be used until the limit resets or is raised.
When you run out
There are two different limits, they produce two different errors, and the fix for one does nothing for the other.
What the monthly limit is. Each organization has a monthly API spend limit, $4,000 per calendar month unless Gloo has set a different one for you. The month runs on UTC, so usage drops to zero all at once at midnight UTC on the 1st and access returns in one step. Requests over the limit return
429 with the code MONTHLY_SPEND_LIMIT_REACHED and the message “Your organization has reached its monthly API spend limit.”
The Monthly API spend limit meter on the Inference row of the Billing page, and the matching card on the Usage page, show your spend so far against the limit, for example $1,250 / $4,000.
Only usage paid from credit counts toward the monthly limit. Promotional credit and work done inside Gloo Code do not count. You cannot change the limit yourself in the Studio. Contact support to have it raised, lowered, or removed. The limit belongs to your organization, so changing plans does not reset it.
If your card is declined
If an automatic top-up is declined:- No credit is added, and your existing balance is untouched. Nothing is lost.
- You get one email, “Your card was declined”, with a link to update your payment method.
- Gloo waits before retrying rather than re-attempting immediately, so a declined card does not generate repeated charges.
- Your existing credit keeps working until it runs out, at which point requests return
402.
Decline emails are limited to one per organization per day, and are sent to the email address on your payment profile.

