Skip to main content

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

Buy $1 to $100 at a time from the Billing page. Credit is available within seconds of payment.

Auto-refill

Optionally let Gloo top you up automatically before you run dry, up to $1,000 of automatic charges per rolling 7 days.
Without auto-refill, requests stop when your balance reaches zero and resume after you add credit.

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.
  1. Go to the Studio Billing page
  2. On the Overview tab, click Add credits
  3. Choose $10, $25, $50 or $100, or enter a custom amount between $1 and $100
  4. Complete payment on the checkout page
New organizations choose their first credit amount during onboarding. The card you pay with is saved so it can be used for auto-refill later. You can remove it at any time from the Payment Methods tab. When the credit appears. Fulfilment happens when your payment confirms, not when your browser returns. In practice credit lands within a few seconds and the page updates on its own. If it takes longer than about 90 seconds the page will say so and offer Continue anyway. Your payment went through, and the credit will appear without you doing anything. Gloo does not email a purchase receipt. Every purchase is listed in Billing History in the Studio with the amount and a link to the invoice or receipt.

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:
  1. On the Billing page, find the Auto-refill switch on the Wallet card
  2. Set the amount to add each time ($10 to $100)
  3. Flip the switch on and confirm in the dialog
Nothing is saved until you confirm. Closing the dialog leaves auto-refill off. Turning it off later takes effect immediately. How it decides to charge. Auto-refill is not on a fixed schedule. It charges when your balance runs low, and the charge takes a few seconds to land. The weekly charge cap. Auto-refill will charge at most $1,000 per rolling 7 days. This is a cap on money charged to your card, not on usage. When you reach it:
  • 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
If the amount you configured would not fit in the remaining headroom, Gloo charges the part that fits rather than skipping the top-up entirely.
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.
The monthly API spend limit is not the same as the auto-refill charge cap. One limits how much API usage your organization can run in a month; the other limits how much Gloo will charge your card automatically in 7 days. It is possible to be stopped by one while the other has room.
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.
Update your card on the Payment Methods tab and auto-refill resumes on the next top-up.
Decline emails are limited to one per organization per day, and are sent to the email address on your payment profile.

If you also use Gloo Code

A Gloo Code tier includes its own usage allowance, and that allowance and your credits are separate pools that cannot substitute for each other. Gloo Code work draws on the Gloo Code allowance; direct API calls draw on your credits. See Billing & Plans.

Promotional credits

If your organization has promotional credit, it is shown alongside your paid balance and is always spent first. Only once promotional credit reaches zero does usage begin drawing on credit you paid for.

Who can see and change this

Billing surfaces are restricted to members who can manage billing. Everyone else sees “Billing is managed by your organization admins” in place of the Wallet card, payment methods and plan changes.

Frequently asked questions

Do my credits expire? No expiry is applied to purchased credit today. Credit is consumed by usage and survives product and tier changes. If that changes, it will be announced and reflected in the Terms of Service before it takes effect. Can I get a refund on unused credits? Credit purchases are final. Buy in the amount you expect to use. You can always add more. If something went wrong with a purchase, contact support. Why was my top-up refused? A manual top-up is refused if the amount is outside the $1 to $100 range, or if your organization has reached its monthly API spend limit, since the credit could not be used until the limit resets on the 1st or is raised. Auto-refill is different: it pauses once it reaches its own weekly charge cap, and you can still add credits manually while it is paused. Why did auto-refill not fire before I ran out? Auto-refill charges when your balance runs low, and the charge takes a few seconds to land. A burst of large requests arriving in that window can briefly outrun it. If that happens regularly, raise your auto-refill amount so each top-up lasts longer.

Next Steps

Billing & Plans

Products, tiers, and spend limits.

API Usage

Track requests, tokens, and spend.