> 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.

# Purchasing additional usage

Buy Warp usage or enable auto-reload, and manage your team's shared balance and monthly spend limit.

Purchase usage when your available balance won’t cover your work. Buying usage is separate from subscribing to a plan.

## Warp Terminal and local agents

On the Free plan for Warp Terminal and local agents, buy usage without subscribing from the purchase card on the [Warp upgrade page](https://app.warp.dev/upgrade). Purchases do not include a premium.

On eligible paid Warp Terminal and local agent plans, open **Settings** > **Billing and usage** in the Warp app. Runs use the member’s included allowance before drawing from eligible purchased usage.

## Warp Factories

In the [Warp Factories web app](https://platform.warp.dev), open **Settings** > **Billing and usage** to review shared funding and add team usage. Under “Add more usage”, choose an amount, then click **Purchase**. Complete checkout if prompted.

The Start plan for Warp Factories uses purchased usage without a subscription. The Scale plan for Warp Factories uses its shared monthly allowance first, then eligible purchased usage. Factory runs cannot use a member’s included personal allowance. See [funding factory runs](https://docs.warp.dev/support-and-community/plans-and-billing/plans-pricing-refunds/#funding-factory-runs) for spending order and Enterprise contract terms.

## How purchased usage works

Warp uses your included allowance first, then available purchased usage. Purchased usage covers inference, hosted compute, and applicable [platform charges](https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/). It rolls over across billing cycles and expires 12 months after purchase.

On a team, new purchases enter a shared balance. The product-specific sections above explain which included allowance is used first. Enterprise purchases follow your contract.

## Who can purchase usage

On eligible plans, any active team member can make a one-time purchase within the team’s monthly spend limit. Team admins manage auto-reload, the limit, and the saved payment method. If your billing view does not offer a purchase control, ask an admin.

Purchases charge the team’s saved payment method, not a separate card for each member. A card saved during the team’s first purchase can become the payment method used for later purchases and auto-reloads. See [managing the team’s payment method](https://docs.warp.dev/support-and-community/plans-and-billing/pricing-faqs/#how-do-i-change-or-remove-the-card-saved-for-my-team).

## Purchasing usage

### 1\. Buy on-demand

Eligible self-serve plans offer one-time usage purchases. See [Warp pricing](https://www.warp.dev/pricing) for current amounts and prices.

Use the purchase path for [Warp Terminal and local agents](#warp-terminal-and-local-agents) or [Warp Factories](#warp-factories). Choose a one-time amount while auto-reload is off. If your account bills in credits, check the credit quantity and price displayed for your plan instead.

### 2\. Enable auto-reload

Auto-reload buys your selected usage amount when included usage is exhausted and the available purchased balance runs low. Reloaded usage enters the shared team balance and uses the same purchase prices as one-time purchases.

Auto-reload is off by default. The purchase card for the Free plan for Warp Terminal and local agents only supports one-time purchases. A team admin can configure auto-reload when Billing and usage offers the controls:

1.  For Warp Terminal and local agents, open **Settings** > **Billing and usage** in the Warp app. For Warp Factories, open **Settings** > **Billing and usage** in the factory web app, then click **Open billing** to reach the team’s billing controls.
2.  Turn on **Auto-reload** and choose the usage amount to purchase each time.
3.  Review the team’s [monthly spend limit](#configuring-a-monthly-spend-limit) and adjust it for the work you plan to run.

Heavy usage by any member can trigger repeated reloads. Review the selected amount and limit before starting unattended runs.

## Configuring a monthly spend limit

One-time purchases and auto-reloads count toward a single team-wide monthly spend limit. If a purchase is blocked, choose a smaller amount or ask an admin to raise the limit.

In the Warp app, a team admin can adjust this limit in **Settings** > **Billing and usage**, even when auto-reload is off.

-   **Paid Warp Terminal and local agent subscriptions** - The spend limit uses a monthly cycle, including on annual subscriptions. Its reset can differ from the included-usage reset.
-   **Free plan for Warp Terminal and local agents** - The spend limit resets at the start of each calendar month in UTC.

The spend limit is not a guaranteed ceiling on the amount charged. Taxes can increase the payment total. Subscription payments and external provider bills are separate.

## Tracking purchases and team usage

Check your remaining balance and purchase spending in **Settings** > **Billing and usage**. Eligible shared purchased usage is spent before member-specific purchases usable on the same team. Dedicated cloud allowances can have a different spending order.

Scheduled and agent API key runs can also draw from the shared balance and trigger reloads. See [cloud agent billing on team plans](https://docs.warp.dev/platform/team-access-billing-and-identity/).

## Plan changes and cancellations

If purchased usage remains available after a plan change, its original 12-month expiration still applies. New purchases use the price for your current plan.

### When team membership changes

Purchased usage stays tied to the team that bought it:

-   **Leaving or being removed** - You lose access to that team’s balance. Rejoining restores access to any unused, unexpired purchased usage.
-   **Deleting a team** - Contact [support@warp.dev](mailto:support@warp.dev) if the team still has unused purchased usage.

## Related pages

-   [Usage and billing](https://docs.warp.dev/support-and-community/plans-and-billing/credits/) - What consumes usage and how to track it.
-   [Plans, pricing, and refunds](https://docs.warp.dev/support-and-community/plans-and-billing/plans-pricing-refunds/) - Existing balances, allowances, and refund policies.
-   [Pricing FAQs](https://docs.warp.dev/support-and-community/plans-and-billing/pricing-faqs/) - Payment methods and account management.
