Billing & Plans

​

Overview

Gloo AI Studio is priced per product, and the products stack: one account, one payment method, one billing history. Add the ones you need and Gloo combines the monthly ones into a single subscription that renews on one billing date. Prepaid credits work differently: each credit purchase, whether you buy it yourself or auto-refill does, is charged to your card at the moment it happens, not on that date. Current prices are on the pricing page. Once you are signed in, the products page is where you add, change or remove products, and the Billing page is where you manage credits, seats, payment methods and invoices.

​

Prices

Teams plans are bought for 2 to 25 seats; 26 or more seats is an Enterprise conversation. Each tier’s allowance is shown in Studio as a percentage used, never as a dollar figure, and higher tiers include a larger allowance and access to more models. Inference has no monthly fee. You buy credits and each request draws them down at the model’s published rate:

• Direct endpoints, Direct Responses, Direct Completions, and Embeddings, bill the provider’s published per-model rate with nothing added. Embeddings are billed per input token with no output charge. Grounded Responses runs on the same direct path, so retrieval over your own content adds no fee either.
• Guarded endpoints, Responses and Completions, where guardrails, moderation and values alignment run, add a 6.5% platform fee on top of the provider rate. Grounded Completions runs on the guarded pipeline and carries the same fee. See Responses for how the fee is applied.

The live rate for every model is on the Supported Models page 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 deliberate, and it is enforced in both directions:

• An organization with only a Gloo Code plan 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.

​

Choosing a Gloo Code tier

Gloo Code comes in Basic, Pro and Ultra. Each is a single-seat plan, and each has a Teams variant for organizations that need several people on Gloo Code under one subscription. You can only hold one Gloo Code tier at a time. Adding Ultra when you already have Pro replaces it rather than stacking. You get one allowance, not two.

​

Teams and seats

A Teams plan 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. Two different things happen with seats on the Billing page:

• 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 that is drawn only after the monthly allowance is exhausted, and it carries over when the month renews, so unused top-up units are not lost at the boundary. 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. It shows:

• Your organization
• Your Gloo Code plan 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

It does not show dollar amounts. Usage here is always a percentage of your allowance, not a cost. 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 plan

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 have already paid for until then, and you are not refunded the difference.

If a single change does both at once, 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. Your credits are untouched by any of this. They belong to your organization, not to a product, and they survive plan changes.

​

Adding a payment method

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

1. Navigate to the Studio Billing page
2. Go to the Payment Methods tab
3. Click Add payment method
4. Enter your card details
5. Save your changes

Once you have credits, you can start using the API and monitoring your usage in the API Usage dashboard.

​

Spend limits

Inference (prepaid credits). API usage paid from credit has a fixed $100 weekly usage limit. It is not a setting you adjust; it exists to bound how fast a card can be charged. It counts only usage drawn from paid credit, so heavy Gloo Code use never eats into it. The Wallet card on the Billing page shows how much of the week you have used and when the window resets. 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 unlock the full power of Gloo AI, including:

• 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

​

Private Transcription

Audio and video you ingest is transcribed automatically so it becomes searchable. By default that transcription is performed by a third-party speech-to-text provider, which means the audio is sent outside Gloo’s infrastructure to be processed. Private Transcription keeps that processing on Gloo-managed infrastructure instead. It is a paid add-on for Enterprise customers, available on request. It is not enabled by default 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. It is not something you can enable yourself from the Studio. How to contact sales:

• Use Contact us from the pricing page
• Click the Contact sales button on any Enterprise tier in Studio

What to expect: Our sales team will work with you to:

1. Understand your use case and requirements
2. Configure the right plan and features for your needs
3. Set up monthly invoicing and service agreements
4. Migrate your existing organization to Enterprise features

​

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.

​

Legacy plans

Two kinds of organization predate the product model above. Nothing changes for them until they choose to add a product.

​

Pro

Pro is no longer sold to new organizations. If you are on it, it continues to work as it does today: 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: the upgrade checkout moves the organization onto a combined plan and carries your Pro entitlements across, so you keep Data Engine and Content Library access. Details 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 $10, 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 fixed $100 weekly usage limit 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 plan plus a seat for each user, so a team that was set up the old way is re-enabled by an organization admin:

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 $10, with the fixed $100 weekly usage limit 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

​

Frequently asked questions

Can I have two Gloo Code tiers at once? No. One tier per organization. Moving between tiers is a swap, not an addition. Do I need credits if I only use Gloo Code? No. A Gloo Code plan on its own is enough for Gloo Code. Add credits only if you also call the Gloo AI API directly. Does my Gloo Code allowance roll over? The monthly allowance does not. It is for the billing period and renews with your subscription. Top-up units do carry over until they are used. What happens to my credits if I cancel a Gloo Code plan? Nothing. They are separate. Credits stay on your organization. What happens if I exceed my spend limit? For prepaid Inference, API access pauses at the $100 weekly usage limit and resumes when the window resets; the Wallet card shows when. 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. Can I change my plan?

• Add, change or remove a product: self-serve from the products page or the Billing page, with the timing described in Changing your plan
• 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

Can I still get an invoice instead of paying by card? Invoicing is an Enterprise arrangement. See Upgrading to Enterprise. What payment methods are accepted? 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. Can I pay with my bank account (ACH)? 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. How do I stop paying? Remove every product from the products page; each one ends at your next billing date and nothing further is charged. Credits you have already bought stay on your organization and keep working until they are used. Removing your last card from Payment Methods stops auto-refill and any future charges, though Studio asks you to settle any outstanding charges first.