Usage and billing

Warp usage pays for model calls, hosted compute, and platform services. In the Warp app, open Settings > Billing and usage to check your included allowance, purchased balance, and reset date.

Dollar usage and credits

Your plan determines the unit Warp uses to charge usage:

• Dollar billing - When Billing and usage shows dollar amounts, usage charges draw from that balance.
• Credit billing - Usage is measured and charged in credits. Enterprise contracts that use credits retain their rates and terms.

Use the unit shown in Billing and usage to identify how your account is billed. If the unit does not match your billing terms, contact billing@warp.dev.

Usage has three charge components:

• Inference - Model calls provided by Warp. If you use your own API key or inference endpoint, your provider bills that inference separately.
• Compute - The sandbox used by an agent on Warp-hosted compute. Local runs and self-hosted compute don’t incur this charge.
• Platform - Agent time billed for cloud runs, plus local runs on Business and Enterprise that use customer-supplied inference. See platform usage for eligibility and rates.

For paid self-serve plans billed in dollars, Warp-provided inference is priced at public API rates. Compute and platform charges are separate. Free-plan usage purchases include a purchase premium.

A credit is a usage unit, not a token or a fixed number of prompts.

Tracking usage

• Account usage - Check your balance and reset date in Settings > Billing and usage.
• Turn usage - Expand the usage amount below an agent response. Where detailed usage is available, expand a model to see input, output, cache-read, and cache-write tokens, plus web searches and their costs.
• Conversation usage - Open the conversation’s usage summary to see its total. View account usage opens Billing and usage.

The CLI has its own usage display.

Charges and estimates

Recorded dollar totals represent Warp usage charges, not the total price of your subscription or usage purchases. Older usage can have estimated costs, credit-only details, or no breakdown. An unavailable amount does not mean the run was free. Bills from your own inference provider are not fully represented in Warp’s totals.

Included and purchased usage

On self-serve paid plans, included usage is allocated per seat and resets monthly, including on annual subscriptions. Unused included usage does not roll over. Check the allowance shown for your account rather than assuming it matches the amount advertised for a new subscription.

After included usage runs out, Warp draws from available purchased usage on eligible plans. Purchased usage rolls over until its expiration and is shared across the team. Dedicated cloud allowances can be used before your general balance. Enterprise pool sizes and allocation rules follow your contract.

Under dollar billing, the Free plan doesn’t include bundled usage for the Warp Agent. Buy additional usage, upgrade, or bring your own inference. Separate platform charges still apply to eligible runs.

Other metered features

Generate and AI Autofill in Workflows also use inference. Regular shell commands and non-AI terminal features do not consume agent usage.

How usage is calculated

Inference cost depends on the model’s rates and the work required to complete your request:

• Model choice - Models have different input, output, and cache prices. A lower-cost model can reduce spending without reducing the number of tokens.
• Input and output - Your prompt, conversation history, attached context, and generated response contribute to token usage.
• Caching - Cached input can cost less than new input. Cache-read and cache-write tokens are reported separately.
• Task complexity - A task can require several model calls, including calls made while using tools or summarizing a long conversation.
• Provider tools - Features such as web search can add charges beyond token costs.

Two similar prompts can use different amounts. Use the reported breakdown to compare tasks rather than treating a prompt as a fixed-price unit. See using tokens efficiently for ways to reduce usage.

Compute usage

Cloud runs on Warp-hosted compute incur compute charges, whether started from the Warp app, an integration, the CLI, or the Warp Platform API. Compute cost depends on the resources and time used.

Local runs, CI jobs on your own runners, and self-hosted workers do not incur Warp-hosted compute charges. Platform charges can still apply.

Platform usage

Cloud runs, including factory runs and third-party harnesses, incur platform usage for billable agent time. Local runs on Business and Enterprise also incur platform charges when they use customer-supplied inference. Enterprise billing follows your contract.

See platform usage for billable time, exceptions, and the distinction between agent hours and run time.

Cloud agent runs on team plans

Agent API key runs follow the team billing rules for cloud runs.

By default, user-created schedules use the creator’s eligible included and purchased usage. A schedule configured to run as a cloud agent uses shared team usage instead. Enterprise pools and charges follow your contract.

If no usable balance remains, a run can fail with an insufficient credits error.

Related pages

• Plans, pricing, and refunds - Allowances, existing balances, and refund policies.
• Purchasing additional usage - One-time purchases, auto-reload, and team limits.
• Platform usage - Agent-hour billing and eligibility.