Skip to main content
Gloo AI Studio is priced per product, and the products stack: one account, one payment method, one billing history. Gloo combines the monthly products you add into a single subscription that renews on one billing date. Prepaid credits are different: each purchase, whether manual or by auto-refill, is charged to your card when it happens, not on that date.

Inference

Pay-as-you-go access to the Gloo AI API, funded with prepaid credits. Usage is billed at the published per-model rates.

Gloo Code

A monthly subscription to the Gloo Code coding agent in Basic, Pro and Ultra tiers, each with a Teams variant priced per seat. Every tier includes a monthly usage allowance.

Data Engine

Ingest, ground and search your own content. Data Engine is currently at capacity; request access and the team will follow up.

Enterprise

Custom terms, monthly invoicing, audit trails and dedicated support. Contact us to talk it through.
Current prices are on the pricing page. Once signed in, use the products page to add, change or remove products, and the Billing page to manage credits, seats, payment methods and invoices.
Organizations created before this model, on the older Pro plan or on weekly arrears billing, keep working as they do today. See Legacy plans. Enterprise organizations are invoiced under their agreement and do not buy prepaid credits.

Prices

Teams tiers are bought for 2 to 25 seats; 26 or more seats is an Enterprise conversation. Every tier includes every agent and model; tiers differ only by allowance and support. Each tier’s allowance is shown in Studio as a percentage used, never as a dollar figure. Inference has no monthly fee. You buy credits and each request draws them down at the model’s published rate. Direct endpoints bill the model’s published rate, the same as going straight to the model providers. Guarded endpoints are priced at that rate plus 6.5% for Gloo’s guardrails, moderation and values alignment. The live rate for every model is on the Supported Models page, on the Models page in Studio, and on GET /platform/v2/models.

The one rule that surprises people

A Gloo Code allowance and API credits are two separate pools, and neither can be spent as the other.
  • Your Gloo Code allowance pays for work you do inside Gloo Code. It cannot be spent on direct API calls.
  • Your credits pay for direct API calls. They are not consumed by Gloo Code.
This is enforced in both directions:
  • An organization with only a Gloo Code subscription that calls the API directly is refused. The Gloo Code allowance does not grant API access.
  • An organization with only credits that uses Gloo Code is refused with 402 GC_NOT_SUBSCRIBED. Credits do not grant Gloo Code access.
If you use both Gloo Code and the API directly, add both products. Having one does not grant the other, and running out of one does not fall back to the other.

Choosing a Gloo Code tier

Basic, Pro and Ultra are single-seat tiers, and each has a Teams variant for several people under one subscription. You can only hold one Gloo Code tier at a time. Adding Ultra when you already have Pro replaces it, so you get one allowance, not two.

Teams and seats

A Teams tier is bought in seats, from 2 to 25 per subscription. The fee and the included allowance both scale with the seat count: five seats means five times the per-seat fee and five times the per-seat allowance, pooled across the organization rather than divided per person. The Billing page handles seats in two places:
  • How many seats you pay for is a product change, made from the Gloo Code product’s Manage dialog. Adding seats takes effect immediately, prorated for the rest of the period. Removing seats takes effect at your next billing date, and until then you keep the seats you paid for.
  • Who holds a seat is set from the Manage seats dialog. An organization admin assigns and unassigns seats to members, and only a member holding a seat can sign in to Gloo Code. Unassigning a member frees the seat and signs them out within about a minute.
Only organization Admins can buy or change products, assign seats, and buy credits. Other members see Billing is managed by your organization admins in place of those controls. See Manage Users for roles.

When the allowance runs out

Each pool runs out on its own terms: The full error bodies are in the error reference.

Gloo Code top-ups

If your allowance runs out before the month does, buy a top-up from the Gloo Code card on the Billing page. A top-up costs the same as a month of your tier and adds the same allowance again. It goes into a separate pool, drawn only after the monthly allowance is exhausted, and unused top-up units carry over when the month renews. Top-up units expire 12 months after purchase and can only be spent while the organization holds an active Gloo Code tier. On a Teams plan the top-up is priced and sized for your full seat count. The Usage page shows the monthly allowance and any top-up as two separate percentages.

Tracking your Gloo Code usage

The Usage page in Studio has a Gloo Code view showing:
  • Your organization
  • Your Gloo Code tier
  • How much of this month’s allowance you have used, as a percentage
  • When your allowance resets
  • How much of any top-up you have used
Usage is always a percentage of your allowance, never a dollar amount. Gloo Code sign-ins do not appear on the API Keys page. Organization admins can see each member’s Gloo Code activity on the Usage page, and can revoke a member’s Gloo Code sign-ins from there.

Changing your products or tiers

Adding, removing or swapping a product takes effect without interrupting service. When it takes effect depends on which direction the money moves:
  • Anything that increases your fee, adding a product, moving up a Gloo Code tier or adding seats, applies immediately, prorated for the rest of the current period. You get the new access straight away and pay the difference for the remaining days.
  • Anything that decreases your fee, removing a product, moving down a tier or removing seats, applies at the start of your next billing period. You keep what you paid for until then, with no refund of the difference.
If a single change does both, say adding credits while dropping to a lower Gloo Code tier, the increase applies immediately and the decrease is scheduled for the next period. You are never charged twice, and you never lose access you have paid for. The dialog states the timing and today’s charge before you confirm. Credits belong to your organization, not to a product, so product and tier changes never touch them.
The Studio UI refreshes automatically after a product or tier change; no reload needed.

Adding a payment method

Your card is saved the first time you pay: buying credits, or starting a Gloo Code subscription, during onboarding or from the Billing page. After that you can add, replace or remove cards from the Payment Methods tab.
1

Open the Billing page

Navigate to the Studio Billing page.
2

Open Payment Methods

Go to the Payment Methods tab.
3

Add the card

Click Add payment method and enter your card details.
4

Save

Save your changes.
A card on its own does not activate anything. API access starts when you buy your first credits; see Prepaid Credits. Gloo Code access starts with a Gloo Code subscription.
Once you have credits, you can use the API and monitor usage in the API Usage dashboard.

Spend limits

Inference (prepaid credits)

API usage paid from credit has a monthly API spend limit for your organization, $4,000 per calendar month (UTC) unless Gloo has set a different one. You can’t adjust it in the Studio. It counts only usage drawn from paid credit, so Gloo Code use never eats into it. 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 this month against the limit, for example $1,250 / $4,000.
When you reach the monthly limit, API requests return 429 MONTHLY_SPEND_LIMIT_REACHED until the month resets on the 1st (UTC) or the limit is raised. Adding credits does not restore access, and manual purchases are refused while you are at the limit, unless the purchase is clearing a negative balance. See Prepaid Credits for the two limits and the two errors they produce.
Need a different monthly limit? Contact support, who can raise or lower it for your organization, or remove it. A change takes effect within a minute and persists across plan changes, because the limit lives on the organization. Organizations on legacy plans still set their own limit from the Spend Limit card.

Gloo Code

There is no spend limit to set. Your tier’s monthly allowance is the ceiling, and a top-up is the only way to add to it.

Enterprise

Spend limits are managed through your service agreement, not the Studio UI. Contact your account manager to adjust them.

Upgrading to Enterprise

Enterprise plans include:
  • Data Engine: Ingest and manage your organization’s content
  • Search: Implement intelligent search across your data
  • Item Recommendations API: Build personalized recommendation systems
  • Extended Analytics: Track ingestion metrics
  • Private Transcription: Paid add-on, available on request (see below)
  • Monthly Invoicing: Simplified billing with monthly invoices
  • Dedicated Support: Priority support from our team

How to contact sales

What to expect

Sales will work with you to:
1

Understand your needs

Understand your use case and requirements.
2

Configure your plan

Configure the right plan and features for your needs.
3

Set up invoicing

Set up monthly invoicing and service agreements.
4

Migrate your organization

Migrate your existing organization to Enterprise features.

Private Transcription

Audio and video you ingest is transcribed automatically so it becomes searchable. By default a third-party speech-to-text provider does this, so the audio is processed outside Gloo’s infrastructure. Private Transcription keeps that processing on Gloo-managed infrastructure instead. It is a paid add-on for Enterprise customers, available on request, and is not included automatically with an Enterprise agreement. If your organization has data-residency, regulatory, or contractual requirements that prevent audio being processed by a third party, raise it with your account manager or contact sales; you can’t enable it yourself in the Studio.

Managing invoices (Enterprise)

Enterprise accounts receive monthly invoices based on their service agreement. Invoices include:
  • API usage (requests and tokens)
  • Feature access (Data Engine, Search, Item APIs)
  • Any custom services or add-ons
Invoices are sent to your designated billing contact at the end of each billing period. For questions about your invoice, contact your account manager.
Enterprise invoices include detailed usage breakdowns. You can also monitor real-time usage in the API Usage dashboard.

Frequently asked questions

No. One tier per organization; moving between tiers is a swap.
No. Add credits only if you also call the Gloo AI API directly.
The monthly allowance does not; it renews with your subscription. Top-up units carry over until used.
Nothing. Credits are separate and stay on your organization.
For prepaid Inference, API requests return 429 MONTHLY_SPEND_LIMIT_REACHED at the monthly API spend limit and resume when the month resets on the 1st (UTC). For legacy Pro, access pauses at the monthly cap and resumes at the start of the next billing period. In both cases support can raise the ceiling.
  • Add, change or remove a product: self-serve from the products page or the Billing page, with the timing described in Changing your products or tiers
  • From legacy Pro or weekly pay-as-you-go to the product model: self-serve from the upgrade card on the Billing page; see Legacy plans
  • To Enterprise: contact us
  • Downgrade from a legacy plan: contact support to discuss your options
Invoicing is an Enterprise arrangement. See Upgrading to Enterprise.
We accept all major credit cards (Visa, MasterCard, American Express, Discover), Apple Pay, and U.S. bank accounts (ACH) for self-serve organizations. Enterprise accounts are invoiced monthly and can arrange payment terms with our billing team.
Yes. When you add a U.S. bank account, you can either connect it instantly by signing in to your bank, or verify it manually with two small deposits. Instant connections are ready to use right away. Manual (micro-deposit) verification takes 1-2 business days, and until you confirm the deposit amounts the payment stays pending.
Remove every product from the products page; each one ends at your next billing date. Credits you have already bought stay on your organization and keep working until they are used. If auto-refill is on, it can still buy credit, so also turn it off or remove your last card from Payment Methods; removing the card stops auto-refill and any future charges, though Studio asks you to settle any outstanding charges first.

Legacy plans

Two kinds of organization predate the product model above, and nothing changes for them until they add a product.

Pro

Pro is no longer sold to new organizations. If you are on it, it works as before: everything in pay-as-you-go, plus Data Engine, Content Library and Search access, billed monthly to your card.
  • Spend limit: $800/month by default. Adjust it from the Spend Limit card on the Billing page, up to your organization’s ceiling ($800 unless it has been raised on request). When you reach it, API access pauses until the next billing period or until support raises your ceiling.
  • Adding Gloo Code: see below.

Adding Gloo Code to a Pro organization

Admins on a Pro plan see an Add Gloo Code to your Pro plan card on the Billing page, and the same option on the products page. The upgrade checkout moves the organization onto a combined plan:
  • You keep Data Engine, Content Library and Search. Pro appears under Your products as Pro · $25/mo, includes Data Engine ingestion, billed together with everything else.
  • Your $25 Pro fee continues. It is not charged again at upgrade. The next Pro charge moves to your new monthly billing date.
  • API usage moves to prepaid credits. The checkout includes an opening credit purchase of at least $1, and from then on API calls draw down your balance instead of being billed in arrears. See Prepaid Credits.
  • The editable spend limit goes away. Prepaid API usage has the monthly API spend limit ($4,000 per month unless Gloo has set a different one) instead. A higher ceiling that support raised for your Pro plan does not carry over; contact support if you still need it.
  • Gloo Code is billed from today. The first month of your tier is charged at checkout, then it renews on the same date each month with the rest of your plan.
Members, publishers, content and existing API keys are unaffected.

If your team used Gloo Code before with a Client ID and Secret

Earlier builds of Gloo Code authenticated with API client credentials and billed their usage to the organization’s plan. Gloo Code now signs in through the browser and needs a Gloo Code subscription plus a seat for each user, so an organization admin re-enables a team set up the old way:
1

Add Gloo Code

On the Billing page, click Add to Pro on the Add Gloo Code to your Pro plan card. Pick a tier, choose My team, set the seat count to the number of people who will use Gloo Code (2 to 25), and complete checkout with your opening credits. Those credits fund the organization’s direct API usage only; Gloo Code work is covered by the tier’s monthly allowance and never draws on them. For a single user, pick the single-seat tier instead.
2

Assign seats

Back on the Billing page, open Manage seats on the Gloo Code product and assign a seat to each member. Anyone not yet in the organization must be invited first. On a single-seat tier, assign the seat to yourself.
3

Each member signs in again

In the terminal, run gloocode and then /login; in Gloo Code Desktop, use the sign-in dialog. Choose this organization when the browser asks and approve access. Gloo Code no longer uses the Client ID and Secret. Leave those credentials in place if other applications still use them, or revoke them from the API Keys page.
A member who sees Your account has no organizations eligible for Gloo Code does not have a seat yet. See Troubleshooting.

Weekly arrears pay-as-you-go

Organizations created before prepaid credits are billed weekly for what they used. They set their own weekly limit from the Spend Limit card, up to their organization’s ceiling, and they keep doing so. New organizations are prepaid instead; see Prepaid Credits. Admins on weekly billing see an Upgrade to Gloo Code and prepaid credits card on the Billing page. Upgrading:
  • charges usage since your last weekly bill to your card now
  • ends weekly billing and sets your new monthly billing date to today
  • moves API usage to prepaid credits, funded by an opening purchase of at least $1, with the monthly API spend limit ($4,000 per month unless Gloo has set a different one) in place of the limit you set yourself. A ceiling support raised for you does not carry over.
There is no self-serve path back to weekly billing afterwards.

How the plans compare

Next steps

To lower what each API request costs and plan around the monthly spend limit, see Controlling Cost.

Prepaid Credits

Add credits and set up auto-refill.

API Usage

Track requests, tokens, and spend.

Manage Users

Control who can see and change billing.