What Is a Credit?

A credit is the unit GlideOS uses to measure AI work. When GlideOS does work for you (chatting, making changes to an app, generating something new), that work uses credits. Actions you take yourself, like clicking to create a new project, do not use credits.

Credits are used in two ways:

• Building with GlideOS, such as chatting with the agent, working on an app, or creating a new project or app.
• AI features inside apps you create. For example, if your app uses AI to generate, summarize, classify, or work with text. This is called Runtime AI.

There are two types of credits:

• Monthly credits: These are included in your plan. They reset every billing cycle, and unused credits do not carry forward.
• Extra credits: These are one-time purchases you can use to top up your monthly credit allowance. Extra credits are valid for 12 months from the date you purchase them and roll over month to month regardless of your billing cycle.

Monthly Credits

Every paid plan comes with a monthly credit allowance.

Monthly credits reset at the start of your billing cycle each month. Unused monthly credits do not carry over to the next month.

To check your credit balances, click your organization name at the top of the left sidebar. Click Settings and then select Billing. The Usage section shows your monthly credits for the current billing cycle, plus any extra credits you’ve purchased.

A credit banner in the prompt box shows how many credits you have left. Click it to go straight to the Billing screen. The banner also includes an option to upgrade.

The Free plan comes with a limited number of credits that do not reset or renew.

Extra Credits

If you use all of your monthly credits, GlideOS stops new AI requests until you have more credits available. If you’re on a paid plan, you can wait for your monthly credits to reset or buy extra credits to continue working immediately.

Extra credits can be purchased at any time, even if you have monthly credits remaining. Credits are added to your balance immediately and drawn from only after your monthly credits run out.

Extra credits do not reset at the end of the billing cycle and are valid for 12 months from the date of purchase.

Here’s an example of how it works:

Say you’re on a paid plan and have 100 credits remaining. You buy 100 extra credits. Your balance is now 200 credits: 100 monthly credits plus 100 extra credits.

You continue to build and use up your 100 monthly credits. Your 100 extra credits kick in, and you continue to build without interruption. Your extra credit balance falls to 50 based on usage.

When the billing cycle resets, your account gets its allowance of 100 monthly credits, giving you a total of 150 available credits (100 monthly credits plus 50 extra credits). GlideOS switches back to drawing from your monthly credits. The 50 extra credits you haven’t used stay in your account until GlideOS needs to draw from them again.

Viewing Your Organization’s Usage

The Usage page shows where your organization’s credits go and how people in your organization build and use apps.

To open it, click your organization name at the top of the left sidebar. Click Settings and then select Usage.

A time-range picker at the bottom of the page controls everything you see: the last hour, day, 7 days, 30 days, or 90 days. The default is the last 30 days. You can also type in the search box to filter any breakdown to a specific person, project, model, or app.

Credits tab

The Credits tab shows the credits your organization used in the selected time range: totals for credits, users, and projects, and a chart of credits used over time.

Below the chart, breakdowns show where those credits went. Switch between them to view:

• User: Credits used per member.
• Project: Credits used per project.
• Model: Credits used by each mode (Light, Balanced, and Heavy). Organizations on the Enterprise plan can see a breakdown by individual model instead.
• Apps: Credits split by where the work happened: Build agent (working with GlideOS in a chat) and Runtime AI (AI features inside apps you’ve published).
• Workflows: Steps, step credits, AI and integration usage, and total credits for each workflow.
• Integrations: Calls and credits for each integration.

The Workflows and Integrations breakdowns appear once your organization has used a workflow or an integration.

Activity tab

The Activity tab shows what your organization created and used in the selected time range: totals for apps created, projects created, app opens, and active users, and a chart of active users over time.

Its breakdowns cover activity per member (apps and projects created, apps opened), recently created apps, the most opened apps, and where apps were opened.

The Opened from breakdown splits app opens by where they happened. Live app counts people opening a published app. Build Preview counts opens from previewing an app in the builder.

Your Usage Across Organizations

Your profile shows a personal view of your own credit usage. Click your organization name at the top of the left sidebar, click Settings, and select Profile. The Your usage section shows a daily grid of your credit usage over the past year. Darker squares mark days when you used more credits. Use the toggle to switch between your usage across all organizations and your usage in the current organization.

Choosing a Mode for GlideOS

You can choose whether GlideOS uses a Light, Balanced, or Heavy AI model from the prompt box. You can switch between them at any time during a chat session. The mode you select applies to new messages until you change it again.

• Light uses the fewest credits per message and suits focused, well-defined tasks.
• Balanced is the recommended default, balancing credit consumption and performance.
• Heavy takes on the most complex work, analysis, and testing. It uses more credits than the other modes.

Many factors affect how many credits GlideOS uses for a given request, so credit usage per message is not reliably predictable. As a rough guide to choosing a mode:

Tips for Optimizing Usage

There are several ways you can optimize credit usage when you work with GlideOS.

Be specific

Just as you would be specific with a colleague when handing off a task, be specific when directing GlideOS to work. The more specific you are, the more likely GlideOS is to complete the task to your specifications. If you want to change one part of your app or project, tell GlideOS to work only in that area.

Start a new chat

Each time you message GlideOS, the context of the conversation grows. Conversations with more context use more credits when the agent responds. To reduce the credits spent on a large context window, start a new chat. You can carry over what matters by asking GlideOS to create a handoff message for you, or by directing it yourself to a specific project, app, or task.

Use Select Mode

With Select Mode, you can pinpoint a specific element of an app and ask GlideOS to change that element on its own. This focuses the agent’s work on just that part of your larger project.

Frequently Asked Questions