> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt). > Markdown versions of each page are available by appending .md to any URL. # Usage and billing Track Warp usage, understand inference, compute, and platform costs, and distinguish accounts billed in dollars from Enterprise contracts using credits. 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** - Your usage balance is an amount in US dollars. 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. Changing the display unit doesn’t change your billing terms or charges. If you’re unsure which unit your account bills in, check your billing terms or contact [billing@warp.dev](mailto:billing@warp.dev). Usage has three charge components: - **Inference** - Model calls provided by Warp. If you use your own [API key](https://docs.warp.dev/agents/inference/bring-your-own-api-key/) or [inference endpoint](https://docs.warp.dev/agents/inference/custom-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](https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/) 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](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/) 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](https://docs.warp.dev/agents/cli/models-and-usage/#usage-and-cost). ### 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](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/) 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. The Free plan uses pay-as-you-go for Warp-provided inference. [Buy additional usage](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/) without subscribing, [upgrade](https://www.warp.dev/pricing), or [bring your own inference](https://docs.warp.dev/agents/inference/bring-your-own-api-key/). Separate [platform charges](https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/) still apply to eligible runs. ## Other metered features [Generate](https://docs.warp.dev/agents/local-agents/generate/) and [AI Autofill in Workflows](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/workflows/#ai-autofill) 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](https://docs.warp.dev/guides/configuration/how-to-use-tokens-efficiently-with-ai-coding-agents/) 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](https://docs.warp.dev/factories/self-hosting/) 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](https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/) 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](https://docs.warp.dev/platform/team-access-billing-and-identity/#billing-for-cloud-agent-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](https://docs.warp.dev/factories/api-and-sdk/troubleshooting/errors/insufficient-credits/) error. ## Related pages - [Plans, pricing, and refunds](https://docs.warp.dev/support-and-community/plans-and-billing/plans-pricing-refunds/) - Allowances, existing balances, and refund policies. - [Purchasing additional usage](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/) - One-time purchases, auto-reload, and team limits. - [Platform usage](https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/) - Agent-hour billing and eligibility.