diff --git a/src/content/docs/enterprise/support-and-resources/billing.mdx b/src/content/docs/enterprise/support-and-resources/billing.mdx index ffdcc7a7..a02f777d 100644 --- a/src/content/docs/enterprise/support-and-resources/billing.mdx +++ b/src/content/docs/enterprise/support-and-resources/billing.mdx @@ -3,11 +3,11 @@ title: Enterprise billing sidebar: label: "Billing" description: >- - Learn about billing for Warp Enterprise, including credits, cloud agent - costs, and billing management. + Billing for Warp Enterprise: credits, cloud agent costs, spending controls, + and BYOLLM billing under your contract. --- -This page covers general information about credits, cloud agent costs, and BYOLLM billing for enterprise teams. If you have specific questions about custom pricing, credit allocation, or contract terms, contact your Warp account manager. +Warp Enterprise uses the same credit-based billing as other plans, with pool sizes, rates, and terms set by your contract. For questions about custom pricing, credit allocation, or contract terms, contact your Warp account manager. ## Credits @@ -31,7 +31,7 @@ Credit allocations vary by contract. Contact your account manager for details on ## Cloud agent billing -Cloud agents consume AI credits for inference, compute credits for the sandbox they run in, and platform credits for the orchestration layer. See [Credits](/support-and-community/plans-and-billing/credits/) for the full breakdown of how each credit type is metered. +Cloud agents consume AI credits for inference, compute credits for the sandbox they run in, and [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the platform layer, billed by the agent hour (the time an agent spends working on a task). Cloud agent runs on self-hosted workers don't consume compute credits but still consume platform credits. See [Credits](/support-and-community/plans-and-billing/credits/) for the full breakdown of how each credit type is metered. ### How credits are consumed @@ -88,7 +88,7 @@ For enterprises with credit pools, administrators receive alerts as the team cre * [Credits](/support-and-community/plans-and-billing/credits/) - How credits are calculated and consumed * [Add-on credits](/support-and-community/plans-and-billing/add-on-credits/) - Purchase additional credits and configure auto-reload -* [Platform credits](/support-and-community/plans-and-billing/platform-credits/) - The third credit bucket alongside AI credits and compute credits, covering Warp's platform infrastructure +* [Platform credits](/support-and-community/plans-and-billing/platform-credits/) - Billed by the agent hour; cover Warp's platform layer on cloud agent runs and local runs with customer-supplied inference * [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/) - Common billing questions * [Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/) - BYOLLM billing and configuration * [Team-managed API keys and endpoints](/enterprise/enterprise-features/team-managed-keys-and-endpoints/) - Share provider keys and custom endpoints across the team; inference routes through your accounts diff --git a/src/content/docs/support-and-community/plans-and-billing/add-on-credits.mdx b/src/content/docs/support-and-community/plans-and-billing/add-on-credits.mdx index b29e7ea4..84c46a59 100644 --- a/src/content/docs/support-and-community/plans-and-billing/add-on-credits.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/add-on-credits.mdx @@ -9,7 +9,10 @@ Add-on credits let you continue using premium AI models even after you've reache In the Warp app, you can manage and purchase add-on credits directly in **Settings** > **Billing and usage**. -![Add-on credits management surface under **Settings** > **Billing and usage**.](../../../../assets/support-and-community/reload-credits.png) +
+![The Add-on credits card in Billing and usage settings, showing the monthly spend limit, the auto reload toggle, and one-time purchase denominations.](../../../../assets/support-and-community/reload-credits.png) +
Add-on credit settings under Billing and usage.
+
### How do add-on credits work? @@ -19,7 +22,7 @@ If you’ve enabled **auto-reload**, new credits will be added automatically and Add-on credits are available on every self-serve plan — Free, Build, Max, and Business — plus Enterprise. The Free plan buys the same packs at a higher rate than paid plans; see [Warp pricing](https://www.warp.dev/pricing) for current rates. On both self-serve and Enterprise plans, add-on credits are shared across your team: every purchase goes into a single team-wide pool that all members draw from. These credits **roll over across billing cycles** and remain valid for **12 months from the purchase date**. -Add-on credits draw from the same pool as [platform credits](/support-and-community/plans-and-billing/platform-credits/) and compute credits, so a single balance covers all three credit types. +Add-on credits can be spent on any credit type, so a single balance covers AI credits, compute credits, and [platform credits](/support-and-community/plans-and-billing/platform-credits/). ### Who can purchase add-on credits @@ -55,9 +58,9 @@ Auto-reload uses the same denominations and discounts as manual purchases. The d You can opt in and choose your reload amount when subscribing to a paid plan on the [Warp upgrade page](https://app.warp.dev/upgrade), or change your configuration anytime in **Settings** > **Billing and usage**. ::: -#### **Configuring a monthly spend limit** +#### Configuring a monthly spend limit -Your monthly spend limit sets the maximum amount you can spend on add-on credits in a single calendar month. This ensures you have full control over your AI usage costs while still allowing flexibility for automatic top-ups when needed, keeping your workflow uninterrupted. +Your monthly spend limit sets the maximum amount you can spend on add-on credits in a single calendar month. * The default limit is $200, but you can increase or decrease it anytime in **Settings** > **Billing and usage**. * **If a credit purchase would exceed your limit, it won’t process** — you’ll need to either raise your limit or choose a smaller add-on credit amount. @@ -66,9 +69,7 @@ Your monthly spend limit sets the maximum amount you can spend on add-on credits * You update your limit in settings. :::caution -Your monthly spend limit is separate from your billing cycle (which determines when your subscription renews).\ -\ -The limit resets automatically at the start of each calendar month, so you can manage recurring AI usage with predictable spending and clear visibility into your costs. +Your monthly spend limit is separate from your billing cycle (which determines when your subscription renews). The limit resets at the start of each calendar month. ::: ### Billing and credit usage diff --git a/src/content/docs/support-and-community/plans-and-billing/credits.mdx b/src/content/docs/support-and-community/plans-and-billing/credits.mdx index 9a73161d..47af6ebe 100644 --- a/src/content/docs/support-and-community/plans-and-billing/credits.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/credits.mdx @@ -3,13 +3,14 @@ title: Warp credits and billing sidebar: label: "Credits" description: >- - Details on Warp credits and how they are calculated. + How Warp credits work: the AI, compute, and platform credit buckets, what + drives credit usage, and how limits and billing apply. --- import { VARS } from '@data/vars'; -### What are Warp credits? +## What are Warp credits? -Any interaction with Warp's Agent consumes credits. Credits are primarily based on AI usage — the number of credits a task consumes varies based on the size and complexity of your codebase, the size of the task, the model you're using, the amount of context the agent needs to gather, and more. +Any interaction with the Warp Agent consumes credits. Credits are primarily based on AI usage — the number of credits a task consumes varies based on the size and complexity of your codebase, the size of the task, the model you're using, the amount of context the agent needs to gather, and more. Warp meters credits across three types of infrastructure — inference, compute, and platform — each with its own bucket. Credit types and where an agent runs (local or cloud) are independent: each agent run consumes from whichever credit types apply to it. @@ -27,11 +28,11 @@ For a general breakdown of what factors contribute to how many credits are consu Since there's no exact formula for predicting usage, we recommend building an intuitive understanding by experimenting with different prompts, models, and tracking how many credits they consume. -**Tracking your credit usage** +### Tracking your credit usage -In an Agent conversation, a **turn** represents a single exchange (a response from the LLM). To see how many credits a turn consumed, hover over the **credit count chip** at the bottom of the Agent's response: +In an agent conversation, a **turn** represents a single exchange (a response from the LLM). To see how many credits a turn consumed, hover over the **credit count chip** at the bottom of the agent's response: -
+
![The conversation usage footer shows how many credits a conversation has consumed, and breaks down the usage by credits, tool calls, context window, files changed, diffs applied, and more.](../../../../assets/support-and-community/inline-credit-usage-footer.png)
Conversation usage footer.
@@ -40,15 +41,15 @@ In an Agent conversation, a **turn** represents a single exchange (a response fr You can view your total credit usage, along with other billing details, in **Settings** > **Billing and usage**. ::: -#### Credit **limits and billing** +### Credit limits and billing * **Seat-level allocation**: On team plans, credit limits apply per seat — each team member has their own allowance. Individual users (not on a team) also have their own credit allocation. * **Cloud agents and integrations**: Individual users can run cloud agents via the CLI and API, drawing from their Warp credits. Slack and Linear integrations require team membership. * **Credit limits by plan**: The Free plan doesn't include bundled AI usage for the Warp Agent. To use the Warp Agent, [upgrade to a paid plan](https://www.warp.dev/pricing), buy [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) without subscribing, or bring your own inference with [Bring Your Own API Key (BYOK)](/agents/inference/bring-your-own-api-key/), a [custom inference endpoint](/agents/inference/custom-inference-endpoint/), or a [SuperGrok or X Premium subscription](/agents/inference/grok-subscription/). On paid plans, once you reach your monthly credit limit you can continue using AI with usage-based billing via [add-on credits](/support-and-community/plans-and-billing/add-on-credits/). -#### **Other features that use credits** +### Other features that use credits -In addition to direct Agent conversations, the following features also consume credits: +In addition to direct agent conversations, the following features also consume credits: * [Generate](/agents/local-agents/generate/) helps you look up commands and suggestions as you type. As you refine your input, multiple credits may be used before you select a final suggestion. * [AI Autofill in Workflows](/knowledge-and-collaboration/warp-drive/workflows/#ai-autofill) counts as a credit each time it is run. @@ -57,27 +58,25 @@ In addition to direct Agent conversations, the following features also consume c Regular shell commands in Warp do not consume or count towards credits. ::: -### How are Warp credits calculated? +## How are Warp credits calculated? -A **credit** in Warp is a unit of work representing the total processing required to complete an interaction with an Agent. It is **not** the same as "one user message" — instead, it scales with the number of tokens processed during the interaction. +A **credit** in Warp is a unit of work representing the total processing required to complete an interaction with an agent. It is **not** the same as "one user message" — instead, it scales with the number of tokens processed during the interaction. In short: **the more tokens used, the more credits consumed**. Several factors influence how many credits are counted for a single interaction: -#### **1. The LLM model used** +### 1. The LLM model used -Generally, smaller, faster models typically consume fewer credits than larger, reasoning-based models. - -For example, **Claude Opus 4.7** tends to consume the most tokens and credits in Warp, followed by **Claude Sonnet 4.6, GPT-5.5, Gemini 3.1 Pro**, and others in roughly that order. This generally correlates with model pricing as well. +Smaller, faster models consume fewer credits than larger reasoning models. The largest frontier reasoning models (the latest Claude Opus models, for example) consume the most tokens and credits per interaction. Credit usage generally tracks the model's API pricing. :::note **Tip**: If your task doesn't require deep reasoning, planning, or multi-step problem solving, choose a more lightweight model to reduce credit usage. ::: -#### 2. Tool calls triggered by the Agent +### 2. Tool calls triggered by the agent -Warp's Agents make a variety of tool calls, including: +Agents in Warp make a variety of tool calls, including: * Searching for files (grep) * Retrieving and reading files @@ -85,17 +84,17 @@ Warp's Agents make a variety of tool calls, including: * Gathering web or documentation context * Running other utilities -Some prompts require only a couple of tool calls, while others may trigger many — especially if the Agent needs to explore your development environment, navigate a large codebase, or apply complex changes. **More tool calls = more credits**. +Some prompts require only a couple of tool calls, while others may trigger many — especially if the agent needs to explore your development environment, navigate a large codebase, or apply complex changes. **More tool calls = more credits**. -#### 3. Task complexity and number of steps +### 3. Task complexity and number of steps Some tasks are straightforward and may require only a single quick response, without much thinking or reasoning. Others can involve multiple stages—such as planning, generating intermediate outputs, verifying results, applying changes, and self-correcting—each of which can add to the credits count. :::note -**Tip**: Keep tasks that you give to the Agent well-scoped, work incrementally, and break large changes into smaller, contained steps. +**Tip**: Keep tasks that you give to the agent well-scoped, work incrementally, and break large changes into smaller, contained steps. ::: -#### 4. Amount of context passed to the model +### 4. Amount of context passed to the model Prompts that include large amounts of context (such as [attached blocks](/agents/local-agents/agent-context/blocks-as-context/), long user query messages, etc.) or file attachments like [images](/agents/local-agents/agent-context/images-as-context/) may also increase the number of credits used due to increased token consumption. @@ -103,7 +102,7 @@ Prompts that include large amounts of context (such as [attached blocks](/agents **Tip**: When sharing logs, code, or other large pieces of content, attach only the most relevant portions instead of full outputs. ::: -#### 5. Prompt caching (hits and misses) +### 5. Prompt caching (hits and misses) Many model prompts include repeated content, like system instructions: @@ -118,49 +117,50 @@ Because cache results depend on model provider behavior and timing, two similar These are the most common factors affecting credit usage, though there are others. Understanding them can help you manage your credits more efficiently and get the most from your plan. -### Compute credits +## Compute credits -Compute credits cover Warp-hosted compute consumed by an agent run. In practice, cloud agent runs consume them because they run on Warp's compute; local agent runs typically don't, since they run on your own machine. +Compute credits cover Warp-hosted compute consumed by an agent run. Cloud agent runs on Warp-hosted workers consume them; local agent runs don't, since they run on your own machine. -Compute credits are sometimes referred to as **cloud agent credits** when the conversation is framed around cloud agents vs local agents — they're the same bucket described from a different angle. +Compute credits are sometimes called **cloud agent credits** when the conversation is framed around cloud agents versus local agents. They're the same bucket described from a different angle. -#### Eligible for compute credits +### Eligible for compute credits The following scenarios use compute credits: -* **First-party integrations** - Running agents through Slack or Linear integrations +* **First-party integrations** - Running agents through Warp's integrations (Slack, Linear, GitHub, and others) * **Cloud agent runs** - Using `oz agent run-cloud` via the CLI * **{VARS.API_SDK_NAME}** - Running agents through Warp's API * **Cloud Mode** - Running an agent from Cloud Mode in the Warp app -#### Not eligible for compute credits +### Not eligible for compute credits -* **Local agent runs** — Using `oz agent run` on your local machine -* **Self-hosted compute** — Using `oz agent run` on GitHub Actions, CI/CD pipelines, or other self-hosted infrastructure +* **Local agent runs** - Using `oz agent run` on your local machine +* **Self-hosted compute** - Using `oz agent run` on GitHub Actions, CI/CD pipelines, or other self-hosted infrastructure +* **Self-hosted workers** - Cloud agent runs on your own infrastructure through Enterprise self-hosted workers. These runs still use platform credits. -### Platform credits +## Platform credits -Platform credits cover Warp's platform infrastructure — run lifecycle, scheduling, integrations, dashboard, APIs, and observability — for every cloud agent run, plus local agent runs on Business and Enterprise plans that use customer-supplied inference. +Platform credits are calculated from agent hours, the time an agent spends working on a task. They cover Warp's platform layer (run lifecycle, integrations, dashboard, APIs, and observability) and apply to every cloud agent run, plus local agent runs on Business and Enterprise plans that use customer-supplied inference. -#### Eligible for platform credits +### Eligible for platform credits Platform credits are used in the following scenarios: -* **Cloud agents on any plan** use platform credits for every cloud agent run, regardless of which agent runs the task or which inference source it uses. +* **Cloud agents on any plan** use platform credits for every cloud agent run, whichever harness, inference source, or compute source it uses. * **Local agents on Business or Enterprise with customer-supplied inference** use platform credits when the local agent run uses [Bring Your Own API Key (BYOK)](/agents/inference/bring-your-own-api-key/), a [custom inference endpoint](/agents/inference/custom-inference-endpoint/), or [BYOLLM](/enterprise/enterprise-features/bring-your-own-llm/). -#### Not eligible for platform credits +### Not eligible for platform credits The following scenarios do **not** use platform credits: -* **Local agents on Free, Build, or Max plans** don't use platform credits, regardless of inference source. +* **Local agents on Free, Build, or Max plans** don't use platform credits, whichever inference source they use. * **Local agents on Business or Enterprise using Warp-managed inference** don't use platform credits because Warp is already paying for the model call through AI credits. * **Regular terminal usage** doesn't use platform credits. Shell commands and non-AI Warp features don't consume credits. * **Third-party agent CLIs run directly** don't use platform credits when you run `claude`, `codex`, or another agent CLI outside of Warp. For a full breakdown of how platform credits work, see [platform credits](/support-and-community/plans-and-billing/platform-credits/). -### Cloud agent runs on team plans +## Cloud agent runs on team plans Cloud agent runs that aren't initiated by a specific team member — for example, scheduled runs or runs triggered through an agent API key — follow plan-specific billing rules. On self-serve plans (Build, Max, Business), these runs are billed to the team owner: the owner's plan-included credits first, then the team's shared add-on credit pool. With auto-reload off, the request is blocked when both are depleted (insufficient credits error). With auto-reload on, usage can trigger a reload into the team's shared pool subject to the team-wide spend cap. On Enterprise plans, these runs draw from the team-scoped credit pool per your contract. diff --git a/src/content/docs/support-and-community/plans-and-billing/index.mdx b/src/content/docs/support-and-community/plans-and-billing/index.mdx index 402319fe..489a56d9 100644 --- a/src/content/docs/support-and-community/plans-and-billing/index.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/index.mdx @@ -12,5 +12,5 @@ Looking for **Bring Your Own API Key** or **custom inference endpoints**? They'v * [**Plans, pricing, and refunds**](/support-and-community/plans-and-billing/plans-pricing-refunds/) - Compare plans, pricing tiers, and refund policies. * [**Credits**](/support-and-community/plans-and-billing/credits/) - How credits are used and calculated across AI features. * [**Add-on credits**](/support-and-community/plans-and-billing/add-on-credits/) - Purchase additional credits or enable auto-reload. -* [**Platform credits**](/support-and-community/plans-and-billing/platform-credits/) - The third credit bucket alongside AI credits and compute credits, covering Warp's platform layer. +* [**Platform credits**](/support-and-community/plans-and-billing/platform-credits/) - Billed by the agent hour; cover Warp's platform layer on cloud agent runs and local runs with customer-supplied inference. * [**Pricing FAQs**](/support-and-community/plans-and-billing/pricing-faqs/) - Answers to common questions about plans and billing. diff --git a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx index 91ccbae2..a28b4a43 100644 --- a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx @@ -1,7 +1,8 @@ --- title: Plans, pricing, and refunds description: >- - Learn about Warp's plans and pricing tiers. Get started for free. + Warp's Free, Build, Max, Business, and Enterprise plans, what each includes, + and the refund policies for subscriptions and add-on credits. sidebar: label: "Plans, pricing, and refunds" --- @@ -20,7 +21,7 @@ See [Warp pricing](https://www.warp.dev/pricing) for the latest plans and what * [Credits](/support-and-community/plans-and-billing/credits/) — learn how credits are used and calculated across AI features. * [Add-on credits](/support-and-community/plans-and-billing/add-on-credits/) — purchase additional credits or enable auto-reload at discounted rates. -* [Platform credits](/support-and-community/plans-and-billing/platform-credits/) — learn how platform credits cover Warp's platform infrastructure for cloud agent runs and local runs with customer-supplied inference. +* [Platform credits](/support-and-community/plans-and-billing/platform-credits/) — billed by the agent hour, covering Warp's platform layer on cloud agent runs and local runs with customer-supplied inference. * [Bring Your Own API Key](/agents/inference/bring-your-own-api-key/) — connect your own model provider API keys for custom usage and billing. * [Custom inference endpoint](/agents/inference/custom-inference-endpoint/) — connect an OpenAI-compatible endpoint such as OpenRouter, LiteLLM, z.ai, or an internal gateway. * [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/) — answers to common questions about plans, billing, and usage. Don’t have Warp yet? [Download Warp](https://www.warp.dev/download) and get started for free today. diff --git a/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx b/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx index 0708f703..8f1e4d18 100644 --- a/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx @@ -1,60 +1,57 @@ --- title: Platform credits description: >- - Platform credits cover Warp's platform layer on every cloud agent run - and on local runs with customer-supplied inference. Learn when they apply. + Platform credits are calculated from agent hours and cover Warp's platform + layer on cloud agent runs and local runs with customer-supplied inference. --- -import { VARS } from '@data/vars'; -Platform credits cover Warp's platform infrastructure for coordinating, observing, and integrating agent runs. They apply to every cloud agent run, plus local agent runs on Business and Enterprise plans that use customer-supplied inference such as BYOK, a custom inference endpoint, or BYOLLM. +Platform credits cover Warp's platform layer: run lifecycle, integrations, dashboard, APIs, and observability. They're calculated from agent hours, the time an agent spends working on a task. Platform credits apply to every cloud agent run, including [Warp Factories](/factories/) runs, plus local agent runs on Business and Enterprise plans that use customer-supplied inference. -Warp meters credits across three types of infrastructure: **inference** (the model call), **compute** (the sandbox an agent runs in), and **platform** (everything that runs around the agent — run lifecycle, integrations, dashboard, APIs, and observability). Each type maps to one credit bucket: [AI credits](/support-and-community/plans-and-billing/credits/), [compute credits](/support-and-community/plans-and-billing/credits/#compute-credits), and platform credits. Credit types and where an agent runs (local or cloud) are independent. - -Customer-supplied inference covers [Bring Your Own API Key (BYOK)](/agents/inference/bring-your-own-api-key/), [custom inference endpoints](/agents/inference/custom-inference-endpoint/), [BYOLLM](/enterprise/enterprise-features/bring-your-own-llm/), and Enterprise [team-managed API keys and endpoints](/enterprise/enterprise-features/team-managed-keys-and-endpoints/). +Customer-supplied inference is any setup where Warp isn't paying for the model call: [Bring Your Own API Key (BYOK)](/agents/inference/bring-your-own-api-key/), [custom inference endpoints](/agents/inference/custom-inference-endpoint/), [BYOLLM](/enterprise/enterprise-features/bring-your-own-llm/), or Enterprise [team-managed API keys and endpoints](/enterprise/enterprise-features/team-managed-keys-and-endpoints/). :::caution -BYOK and customer-supplied inference (custom inference endpoints, plus BYOLLM) are available to individual users and organizations with 10 or fewer employees on any plan. Organizations with more than 10 employees need a Warp Business or Enterprise plan to use BYOK or customer-supplied inference. See Warp's [Terms of Service](https://www.warp.dev/legal/terms-of-service) for details. +BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp's [Terms of Service](https://www.warp.dev/legal/terms-of-service). Companies or organizations with more than 10 employees need a Warp Business or Enterprise plan to use these features. ::: -## The three credit buckets +## How platform credits are measured -Each credit bucket covers a different layer of the infrastructure Warp provides. Credit types and where an agent runs (local or cloud) are independent — each agent run consumes from whichever credit types apply to it. +Platform credits are calculated from **agent hours**. An agent hour is an hour an agent spends working on a task. The clock starts when the agent starts up in its environment, including any environment setup the run performs, and stops when the run finishes, fails, is cancelled, or pauses for your input. Time spent queued before the agent starts, time waiting on your input, and idle time between turns don't count. -* **AI credits** cover inference: the LLM call itself. Consumed when Warp pays for the model call through Warp-managed providers. Used by agent conversations, [Generate](/agents/local-agents/generate/), [AI Autofill](/knowledge-and-collaboration/warp-drive/workflows/#ai-autofill), and other AI features. See [credits](/support-and-community/plans-and-billing/credits/) for how AI credits are calculated. -* **Compute credits** cover compute: the sandbox an agent runs in. Consumed when an agent run uses Warp-hosted compute. In practice this is cloud agent runs (Slack and Linear integrations, `oz agent run-cloud`, the {VARS.API_SDK_NAME}, and Cloud Mode in the Warp app); local agent runs use your own machine and don't consume compute credits. See [compute credits](/support-and-community/plans-and-billing/credits/#compute-credits). -* **Platform credits** cover Warp's platform layer: run lifecycle, integrations, dashboard, APIs, and observability. Apply to every cloud agent run, plus local agent runs on Business and Enterprise plans that use customer-supplied inference. +Usage is billed on exact time rather than rounded up to whole hours, so a run that works for 15 minutes bills a quarter of an agent hour. See [Warp pricing](https://www.warp.dev/pricing) for current rates. -The three buckets are independent and a single run can consume from more than one. A Warp-managed cloud agent run, for example, consumes AI credits for the model call, compute credits for the hosted compute, and platform credits for the platform infrastructure that runs the agent. +## The three credit buckets -## How platform credits are measured +Warp meters three types of infrastructure, each with its own credit bucket. Credit types and where an agent runs (local or cloud) are independent: each run consumes from whichever buckets apply to it. -Platform credits accrue while an agent is actively working on a task — from when the task starts running to when it finishes, fails, or is cancelled. Idle time, time spent waiting on user input, and time before the task starts don't accrue platform credits. +* **AI credits** - Cover inference, the model call itself. Consumed when Warp pays for the model call through Warp-managed providers. See [credits](/support-and-community/plans-and-billing/credits/) for how AI credits are calculated. +* **Compute credits** - Cover the sandbox an agent runs in. Consumed when a run uses Warp-hosted compute, which in practice means cloud agent runs; local agent runs use your own machine. See [compute credits](/support-and-community/plans-and-billing/credits/#compute-credits). +* **Platform credits** - Cover the platform layer that runs around the agent, billed by the agent hour. -See [Warp pricing](https://www.warp.dev/pricing) for current rates. +A single run can consume from more than one bucket. A Warp-managed cloud agent run consumes AI credits for the model call, compute credits for the hosted sandbox, and platform credits for the platform layer. ## When platform credits apply -Whether platform credits apply depends on where the agent runs and who's paying for inference. +Whether a run uses platform credits depends on where it runs and who pays for inference. ### Uses platform credits -* **Cloud agents on any plan** use platform credits for every cloud agent run, regardless of which agent runs the task (Warp Agent, Claude Code, or Codex), inference source (Warp-managed, BYOK, or BYOLLM), or compute source (Warp-hosted or self-hosted workers). Warp's platform infrastructure coordinates every cloud agent run. [Warp Factories](/factories/) runs are cloud agent runs, so a factory's agents draw platform credits the same way. -* **Local agents on Business or Enterprise with customer-supplied inference** use platform credits when the local agent run uses [BYOK](/agents/inference/bring-your-own-api-key/), a [custom inference endpoint](/agents/inference/custom-inference-endpoint/), or BYOLLM. Warp isn't paying for the model call, but Warp's platform infrastructure is still running the local agent. BYOK and customer-supplied inference are subject to plan-size eligibility — see the callout above. +* **Cloud agent runs on any plan** - Every cloud agent run uses platform credits, whichever harness (Warp Agent, Claude Code, or Codex), inference source (Warp-managed, BYOK, or BYOLLM), or compute source (Warp-hosted or self-hosted workers) it uses. [Warp Factories](/factories/) runs are cloud agent runs, so a factory's agents draw platform credits the same way. +* **Local agent runs on Business or Enterprise with customer-supplied inference** - When a local run uses [BYOK](/agents/inference/bring-your-own-api-key/), a [custom inference endpoint](/agents/inference/custom-inference-endpoint/), or BYOLLM, Warp isn't paying for the model call but still runs the platform layer around the agent. ### Doesn't use platform credits -* **Local agents on Free, Build, or Max plans** don't use platform credits, regardless of whether you use Warp-managed inference or BYOK. -* **Local agents on Business or Enterprise using Warp-managed inference** don't use platform credits because Warp is already paying for the model call through AI credits. -* **Regular terminal usage** doesn't use platform credits. Shell commands and non-AI Warp features don't consume credits. -* **Third-party agent CLIs run directly** don't use platform credits when you run `claude`, `codex`, or another agent CLI without going through Warp. +* **Local agent runs on Free, Build, or Max plans** - Don't use platform credits, whether the run uses Warp-managed or customer-supplied inference. +* **Local agent runs on Business or Enterprise with Warp-managed inference** - Don't use platform credits because Warp already charges AI credits for the model call. +* **Regular terminal usage** - Shell commands and non-AI Warp features don't consume credits. +* **Third-party agent CLIs run directly** - Running `claude`, `codex`, or another agent CLI outside Warp doesn't consume platform credits. ## Where platform credits appear -Platform credits appear in the same billing views as your other credit usage. +Platform credits appear in the same billing views as the rest of your credit usage. -* **Per-user credit totals** - In the Warp app, **Settings** > **Billing and usage** includes platform credits alongside AI credits and compute credits. -* **Admin usage breakdown** - For team admins, the Admin Panel billing view shows a per-bucket breakdown for each member and for the team as a whole. Platform credits appear as their own segment in the stacked usage bar, distinct from the AI credits and compute credits segments. -* **Add-on credits and limits** - Platform credits draw from the same pools as your other usage — your monthly Warp credits first, then [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) once those are exhausted. +* **Per-user credit totals** - In the Warp app, **Settings** > **Billing and usage** shows platform credits alongside AI credits and compute credits. +* **Admin usage breakdown** - For team admins, the Admin Panel billing view shows a per-bucket breakdown for each member and for the team as a whole. Platform credits appear as their own segment in the stacked usage bar. +* **Add-on credits and limits** - Platform credits draw from the same pool as the rest of your usage: monthly Warp credits first, then [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) once those run out. ## Related pages diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index e36276e7..cd148666 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -23,7 +23,7 @@ After entering your payment details, you’ll receive an invoice and confirmatio ### How can I get the most out of my Warp plan? -Warp's plans are designed for developers who rely on AI to code, debug, and move faster with their team. Pick the plan that matches the scale of your usage and the controls your team needs: +Warp's plans are for developers who rely on AI to code, debug, and move faster with their team. Pick the plan that matches the scale of your usage and the controls your team needs: * **Build** — Usage-based plan for individuals or small teams with monthly credits, the ability to [Bring Your Own API Key (BYOK)](/agents/inference/bring-your-own-api-key/) or point Warp at a [custom inference endpoint](/agents/inference/custom-inference-endpoint/), and access to [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) with volume-based discounts. * **Max** — Plan for individuals or small teams with heavier AI usage. Includes a larger monthly credit allowance than Build, plus a better effective rate for credits than buying add-on credits on Build. @@ -47,7 +47,7 @@ For Warp-managed model traffic (requests Warp routes to OpenAI, Anthropic, or Go ### What counts as a team member and how does billing work for members? -In Warp, a _team member_ is any seat with access to your Team — including the shared Warp Drive, Notebooks, Workflows, and other team resources. All plans allow you to invite unlimited Warp Drive collaborators, but paid-plan features and credit allocation are governed by your plan's seat limit (see [Are there new seat limits per plan?](#are-there-new-seat-limits-per-plan) below). Upgrading applies to your entire team, including your own account and all active members. +In Warp, a _team member_ is any seat with access to your Team — including the shared Warp Drive, Notebooks, Workflows, and other team resources. Every plan lets you invite unlimited Warp Drive collaborators, but paid-plan features and credit allocation are governed by your plan's seat limit (see [Are there new seat limits per plan?](#are-there-new-seat-limits-per-plan) below). Upgrading applies to your entire team, including your own account and all active members. On the Free plan, you can share a limited number of Notebooks and Workflows with other Free users. If your team exceeds that limit, you’ll be prompted to [upgrade to a plan](https://app.warp.dev/upgrade).\ \ @@ -70,7 +70,7 @@ All members of the team will have the same subscription plan, you can't mix and Team members have access to your shared [Warp Drive](/knowledge-and-collaboration/warp-drive/) objects and limited access to Warp's collaboration features, including Session Sharing and Warp Drive storage. -**Upgrading the team to a plan unlocks powerful collaboration and knowledge-sharing tools to help your team move faster, together:** +**Upgrading the team to a paid plan adds collaboration and knowledge-sharing tools:** * Create unlimited [Notebooks](/knowledge-and-collaboration/warp-drive/notebooks/) and [Workflows](/knowledge-and-collaboration/warp-drive/workflows/) in Warp Drive to organize and share knowledge across your team. * Use Unlimited [Session Sharing](/knowledge-and-collaboration/session-sharing/) to collaborate in real time through live, shared terminal sessions. @@ -85,7 +85,7 @@ When you’re ready to use Warp more collaboratively, we suggest you nominate an When you use the account to sign into Warp on different devices, for example Linux on one computer and Windows on another, your usage of metered features like credits is tracked at the account level, not the device level. -You can use your Warp account on multiple personal computers. Warp is designed to provide a consistent experience across devices. When you log in with the same account on different computers, your settings and preferences can be synced through the [Settings Sync](/terminal/more-features/settings-sync/) feature. +You can use your Warp account on multiple personal computers. When you log in with the same account on different computers, your settings and preferences can be synced through the [Settings Sync](/terminal/more-features/settings-sync/) feature. ### How do I manage my billing? @@ -161,12 +161,12 @@ Enterprise plans support team-scoped credit pools and per-user spend limits sepa ### How do platform credits factor in? -Warp meters credits across three buckets: **AI credits** (the model call), **compute credits** (the sandbox a cloud agent runs in), and **platform credits** (run lifecycle, integrations, dashboard, APIs, and observability). All three draw from the same pool — your monthly Warp credits first, then [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) once those are exhausted. +Warp meters credits across three buckets: **AI credits** (the model call), **compute credits** (the sandbox a cloud agent runs in), and **platform credits** (run lifecycle, integrations, dashboard, APIs, and observability). Platform credits are calculated from agent hours, the time an agent spends working on a task. All three buckets draw from the same pool: your monthly Warp credits first, then [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) once those are exhausted. Platform credits apply in two situations: -* **Every cloud agent run, on every plan.** Warp's platform infrastructure coordinates every cloud run regardless of which agent or inference source it uses. On self-serve plans (Free, Build, Max, Business), platform-credits billing is in a preview period through June 30, 2026 — see [When do platform credits start being charged on self-serve plans?](#when-do-platform-credits-start-being-charged-on-self-serve-plans) for details. -* **Local agent runs on Business and Enterprise that use customer-supplied inference** — BYOK, a custom inference endpoint, or BYOLLM. Warp isn't paying for the model call, but Warp's platform infrastructure is still running the agent. Billing for these runs is also in preview through June 30, 2026 on self-serve plans; metering begins July 1, 2026. +* **Every cloud agent run, on every plan.** Warp's platform layer coordinates every cloud run, whichever harness or inference source it uses. +* **Local agent runs on Business and Enterprise that use customer-supplied inference** (BYOK, a custom inference endpoint, or BYOLLM). Warp isn't paying for the model call, but it still runs the platform layer around the agent. Local agent runs on Free, Build, or Max — and local runs on Business or Enterprise that use Warp-managed inference — do not consume platform credits. See [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the full breakdown. @@ -177,8 +177,8 @@ If you regularly run through your plan's monthly credit allowance, you have a fe * **Upgrade to Max** — Designed for developers with heavier AI usage. Max includes a higher monthly credit allowance than Build, plus a better effective rate for credits than buying [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) on Build. See [Warp pricing](https://www.warp.dev/pricing) for current allowances. * **Purchase add-on credits** — Top up your account on demand. Larger denominations have a better effective rate. Add-on credits roll over month-to-month and remain valid for 12 months from purchase, and they stay usable if you later move to the Free plan. See [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) for current denominations. * **Enable auto-reload** — Pick a denomination and a monthly spend cap, and Warp will automatically purchase add-on credits when your balance drops below 100 credits, up to your cap. -* **Bring Your Own API Key (BYOK)** — Point Warp at your own OpenAI, Anthropic, or Google API key. Requests routed through BYOK don't consume Warp credits — you're billed directly by the model provider. See [Bring Your Own API Key](/agents/inference/bring-your-own-api-key/). On Business and Enterprise, platform credits may apply for local agent runs (billing starts July 1, 2026 on self-serve plans — see [When do platform credits start being charged on self-serve plans?](#when-do-platform-credits-start-being-charged-on-self-serve-plans)). -* **Use a custom inference endpoint** — Route requests through any OpenAI-compatible endpoint (OpenRouter, LiteLLM, z.ai, an internal gateway, etc.) without spending Warp credits. See [Custom inference endpoint](/agents/inference/custom-inference-endpoint/). On Business and Enterprise, platform credits may apply for local agent runs (billing starts July 1, 2026 on self-serve plans — see [When do platform credits start being charged on self-serve plans?](#when-do-platform-credits-start-being-charged-on-self-serve-plans)). +* **Bring Your Own API Key (BYOK)** — Point Warp at your own OpenAI, Anthropic, or Google API key. Requests routed through BYOK don't consume AI credits — you're billed directly by the model provider. See [Bring Your Own API Key](/agents/inference/bring-your-own-api-key/). On Business and Enterprise, local agent runs that use BYOK consume [platform credits](/support-and-community/plans-and-billing/platform-credits/). +* **Use a custom inference endpoint** — Route requests through any OpenAI-compatible endpoint (OpenRouter, LiteLLM, z.ai, an internal gateway, etc.) without spending AI credits. See [Custom inference endpoint](/agents/inference/custom-inference-endpoint/). On Business and Enterprise, local agent runs that use a custom inference endpoint consume [platform credits](/support-and-community/plans-and-billing/platform-credits/). *BYOK and custom inference endpoint availability is subject to organization size — see [Can I bring my own API key?](#can-i-bring-my-own-api-key) for details.* @@ -317,23 +317,23 @@ Regardless of plan, Warp never allows OpenAI, Anthropic, Google, or other model ### Can I bring my own API key? -Yes. On Free, Build, Max, Business, and Enterprise plans, you can configure your own OpenAI, Anthropic, or Google API key in **Settings** > **Agents** > **Warp Agent** > **Manage models**. Requests routed through your own key don't consume Warp credits — you're billed directly by the model provider. +Yes. On Free, Build, Max, Business, and Enterprise plans, you can configure your own OpenAI, Anthropic, or Google API key in **Settings** > **Agents** > **Warp Agent** > **Manage models**. Requests routed through your own key don't consume AI credits — you're billed directly by the model provider. See [Bring Your Own API Key](/agents/inference/bring-your-own-api-key/) for setup steps, the list of supported providers and models, and the differences between BYOK, custom inference endpoints, and BYOLLM. BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp's Terms of Service. Companies or organizations with more than 10 employees need a Warp Business or Enterprise plan to use these features. -On Business and Enterprise, local agent runs that use BYOK still consume platform credits for Warp's platform infrastructure. See [platform credits](/support-and-community/plans-and-billing/platform-credits/). +On Business and Enterprise, local agent runs that use BYOK still consume platform credits, billed by the agent hour. See [platform credits](/support-and-community/plans-and-billing/platform-credits/). ### Does Warp support custom inference endpoints? -Yes. In addition to BYOK, Warp can route requests to any OpenAI-compatible inference endpoint — including OpenRouter, LiteLLM, z.ai, and internal gateways your team already runs. Custom inference endpoint requests also don't consume Warp credits. +Yes. In addition to BYOK, Warp can route requests to any OpenAI-compatible inference endpoint — including OpenRouter, LiteLLM, z.ai, and internal gateways your team already runs. Custom inference endpoint requests also don't consume AI credits. Custom inference endpoints are available on Free, Build, Max, Business, and Enterprise. See [Custom inference endpoint](/agents/inference/custom-inference-endpoint/) for configuration steps, billing behavior, and how custom inference endpoints differ from BYOK and from Enterprise's [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference. BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp's Terms of Service. Companies or organizations with more than 10 employees need a Warp Business or Enterprise plan to use these features. -On Business and Enterprise, local agent runs that use a custom inference endpoint still consume platform credits for Warp's platform infrastructure. See [platform credits](/support-and-community/plans-and-billing/platform-credits/). +On Business and Enterprise, local agent runs that use a custom inference endpoint still consume platform credits, billed by the agent hour. See [platform credits](/support-and-community/plans-and-billing/platform-credits/). ### Does Warp support other model routers or "Bring Your Own LLM"? @@ -399,7 +399,7 @@ The team at Warp is standing by and ready to help. For subscribers technical iss ### May 2026 pricing changes -The May 21, 2026 update introduces new seat limits, changes how add-on credits are attributed, opens BYOK to every plan, adds custom inference endpoints, and starts metering platform credits for cloud agent runs. The questions below cover what's changing and what to do if any of it affects you. +The May 21, 2026 update introduced new seat limits, changed how add-on credits are attributed, opened BYOK to every plan, added custom inference endpoints, and began metering platform credits for cloud agent runs. The questions below cover what changed and what to do if any of it affects you. #### Are there new seat limits per plan? @@ -453,19 +453,6 @@ Here's how custom inference endpoints differ from BYOK and BYOLLM: For setup and details, see [Custom inference endpoint](/agents/inference/custom-inference-endpoint/). -#### When do platform credits start being charged on self-serve plans? - -[Platform credits](/support-and-community/plans-and-billing/platform-credits/) apply to every cloud agent run, plus local agent runs on Business that use BYOK or a custom inference endpoint. **For self-serve plans (Free, Build, Max, Business), platform-credits billing doesn't start until July 1, 2026.** - -Between May 21 and June 30, 2026, all self-serve plans are in a **preview period**. Platform credits are not consumed during this window, so they won't draw from your monthly Warp credits, your add-on credit balance, or your spend cap. - -On **Enterprise**, platform credit usage is governed by your contract. See [enterprise billing](/enterprise/support-and-resources/billing/) for details. - -On **July 1, 2026**, Warp begins consuming platform credits for: - -* Every cloud agent run on Free, Build, Max, or Business. -* Local agent runs on Business that use BYOK or a custom inference endpoint. - #### I'm a team admin. What do I need to do? A short checklist to triage the May 2026 changes for your team: @@ -474,4 +461,4 @@ A short checklist to triage the May 2026 changes for your team: * **Set your team's add-on credit spend cap.** Under **Settings** > **Billing and usage**, configure the monthly cap that applies to add-on credit purchases across your team. Team members can buy add-on credits for the team, but every purchase counts against this cap. * **Let your team know add-on credits are shared team-wide.** Purchases from any member land in the team's shared pool, and the whole team's usage draws it down. * **Confirm which card your team has on file.** Every add-on credit purchase charges the team's saved payment method, including purchases made by members who aren't admins. Review it in the billing portal. See [Which card is charged when a team member buys add-on credits?](#which-card-is-charged-when-a-team-member-buys-add-on-credits). -* **Plan for platform credits on July 1, 2026.** If your team is on Business and uses BYOK or a custom inference endpoint locally, those local runs will start consuming platform credits when the preview period ends. See [When do platform credits start being charged on self-serve plans?](#when-do-platform-credits-start-being-charged-on-self-serve-plans). +* **Account for platform credits.** If your team is on Business and uses BYOK or a custom inference endpoint locally, those local runs consume platform credits. See [platform credits](/support-and-community/plans-and-billing/platform-credits/).