diff --git a/src/content/docs/agent-platform/cloud-agents/overview.mdx b/src/content/docs/agent-platform/cloud-agents/overview.mdx index 9045f47..744c68f 100644 --- a/src/content/docs/agent-platform/cloud-agents/overview.mdx +++ b/src/content/docs/agent-platform/cloud-agents/overview.mdx @@ -128,7 +128,7 @@ Integrations require you to be part of a [Warp team](/knowledge-and-collaboratio * **Plan requirements** * **Supported plans**: Build, Max, Business * Not supported: Pro, Turbo, Lightspeed, legacy Business - * Your plan must support Add-on Credits. + * Your plan must support add-on credits. * **Credit requirements** * Your team must have at least 20 credits available to run cloud agents and integrations. diff --git a/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx b/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx index 8e9328b..4215b5f 100644 --- a/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx +++ b/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx @@ -76,7 +76,7 @@ Integrations and [cloud agents](/agent-platform/cloud-agents/overview/) run insi Your team must meet the following requirements to run integrations: -* You must be on a **Build, Max, or Business** plan with [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) enabled, or on an **Enterprise** plan with a team credit pool per your contract. +* You must be on a **Build, Max, or Business** plan with [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) enabled, or on an **Enterprise** plan with a team credit pool per your contract. * Your team needs at least **20 credits** available to run cloud agents and integrations When a user triggers an agent through an integration (like Slack or Linear), the run draws from credits based on who the run is billed to: @@ -85,7 +85,7 @@ When a user triggers an agent through an integration (like Slack or Linear), the * **Team API key or scheduled cloud agent runs on Build, Max, or Business** - Warp bills the team owner. The waterfall is: the owner's plan-included credits, then the owner's Add-on credits. With auto-reload off, the request is blocked when both pools are depleted. With auto-reload on, usage can trigger a reload on the owner's pool subject to the team-wide monthly spend cap. * **Enterprise plans** - Runs draw from the team-scoped credit pool, per your Enterprise contract terms. -If all applicable credit sources are exhausted and no auto-reload is configured, integrations and cloud agents will not run until credits are added. See [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) for the full self-serve waterfall and [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the third bucket that applies to every cloud agent run. +If all applicable credit sources are exhausted and no auto-reload is configured, integrations and cloud agents will not run until credits are added. See [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) for the full self-serve waterfall and [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the third bucket that applies to every cloud agent run. :::note If you're on an Enterprise plan, please reach out to [warp.dev/contact-sales](https://www.warp.dev/contact-sales) with any billing questions related to integrations. @@ -253,6 +253,6 @@ It's the team's responsibility to manage triggers, confirm they behave as intend ## Related resources -* [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) - How user-scoped Add-on credits, auto-reload, and the team-wide spend cap work on self-serve plans. +* [Add-on credits](/support-and-community/plans-and-billing/add-on-credits/) - How user-scoped add-on credits, auto-reload, and the team-wide spend cap work on self-serve plans. * [Platform credits](/support-and-community/plans-and-billing/platform-credits/) - The third credit bucket that applies to every cloud agent run, alongside AI credits and compute credits. * [Credits overview](/support-and-community/plans-and-billing/credits/) - The full credit model across plans. diff --git a/src/content/docs/agent-platform/getting-started/faqs.mdx b/src/content/docs/agent-platform/getting-started/faqs.mdx index b62d5d7..206f18e 100644 --- a/src/content/docs/agent-platform/getting-started/faqs.mdx +++ b/src/content/docs/agent-platform/getting-started/faqs.mdx @@ -52,7 +52,7 @@ To fix this, try: #### "Monthly request limit exceeded" or "Monthly credit limit exceeded" errors -Once you exceed your monthly credit limit (see [pricing](https://www.warp.dev/pricing) for current limits), premium models will be disabled until your quota resets at the start of your next billing cycle. On paid plans with Add-on Credits, you can continue using AI with usage-based billing. +Once you exceed your monthly credit limit (see [pricing](https://www.warp.dev/pricing) for current limits), premium models will be disabled until your quota resets at the start of your next billing cycle. On paid plans with add-on credits, you can continue using AI with usage-based billing. **Request failed with error: QuotaLimit** diff --git a/src/content/docs/agent-platform/inference/bring-your-own-api-key.mdx b/src/content/docs/agent-platform/inference/bring-your-own-api-key.mdx index f297d05..bcd48a5 100644 --- a/src/content/docs/agent-platform/inference/bring-your-own-api-key.mdx +++ b/src/content/docs/agent-platform/inference/bring-your-own-api-key.mdx @@ -15,7 +15,7 @@ BYOK provides greater flexibility in model access and ensures Warp **never consu BYOK is available on Free and all eligible paid plans for individual users and organizations with 10 or fewer employees, subject to Warp's [Terms of Service](https://www.warp.dev/terms-of-service). Larger organizations need a Business or Enterprise plan. See [warp.dev/pricing](https://www.warp.dev/pricing) for current availability. ::: -## How BYOK differs from Custom inference endpoint and BYOLLM +## How BYOK differs from custom inference endpoints and BYOLLM Warp offers three ways to bring your own AI infrastructure. Use this table to pick the right one, and follow the links for full details. @@ -102,7 +102,8 @@ If your key: * Is invalid: Warp notifies you and halts the request. * Hits usage or rate limits: Warp will not retry using credits. -* You can update or replace your keys anytime by opening **Settings** and searching for `API keys`. + +You can update or replace your keys anytime by opening **Settings** and searching for `API keys`. **Failover and fallback:** diff --git a/src/content/docs/agent-platform/inference/custom-inference-endpoint.mdx b/src/content/docs/agent-platform/inference/custom-inference-endpoint.mdx index 8346479..7248661 100644 --- a/src/content/docs/agent-platform/inference/custom-inference-endpoint.mdx +++ b/src/content/docs/agent-platform/inference/custom-inference-endpoint.mdx @@ -32,7 +32,7 @@ A custom inference endpoint expects your endpoint to implement the **OpenAI Chat When you configure a custom inference endpoint, Warp stores the endpoint URL, model identifiers, and credentials **locally on your device**. They are never synced to Warp's servers. :::caution -Custom inference endpoints don't apply to [Oz Cloud Agents](/agent-platform/cloud-agents/overview/). Because the configuration is stored locally, it isn't available to cloud-hosted agent runs. Cloud agent runs always consume [Warp credits](/support-and-community/plans-and-billing/credits/). +Custom inference endpoints don't apply to [Cloud Agents](/agent-platform/cloud-agents/overview/). Because the configuration is stored locally, it isn't available to cloud-hosted agent runs. Cloud agent runs always consume [Warp credits](/support-and-community/plans-and-billing/credits/). ::: When a model routed through your endpoint is selected: @@ -72,7 +72,7 @@ To use your endpoint, select the specific endpoint-routed model from the model p ### Other AI features in Warp -Some AI-powered features rely on Warp's infrastructure and are unaffected by a custom inference endpoint. These continue to consume credits according to your plan; see [Credits](/support-and-community/plans-and-billing/credits/) for details. +Some AI-powered features (Codebase Context, Active AI recommendations, cloud agent runs) rely on Warp's infrastructure and are unaffected by a custom inference endpoint. See the [feature breakdown on the BYOK page](/agent-platform/inference/bring-your-own-api-key/#byok-usage-and-billing-behavior) for which features still consume Warp credits. ## Zero Data Retention (ZDR) diff --git a/src/content/docs/enterprise/support-and-resources/billing.mdx b/src/content/docs/enterprise/support-and-resources/billing.mdx index 12ebb5a..fe5f2dd 100644 --- a/src/content/docs/enterprise/support-and-resources/billing.mdx +++ b/src/content/docs/enterprise/support-and-resources/billing.mdx @@ -70,7 +70,7 @@ Enterprise administrators can set monthly spending limits across the following f * **Total spending limit** - Cap combined monthly spend across both cloud and local agents. * **Per-user spending limit** - Cap monthly spend for any individual user. Set a default that applies to all users, or configure limits on a per-user basis for predictable individual spend. -Spending is tracked across all payment types (Add-on Credits, pay-as-you-go usage) so limits apply consistently regardless of how usage is funded. +Spending is tracked across all payment types (add-on credits, pay-as-you-go usage) so limits apply consistently regardless of how usage is funded. :::note Team-wide spending limits (cloud, local, and total) are also available on Warp's self-serve paid plans through admin-managed Add-on credit settings. **Per-user spending limits are Enterprise-only.** For deeper visibility into how individual users consume credits, see the [Enterprise Analytics API](/enterprise/enterprise-features/analytics-api/). @@ -87,7 +87,7 @@ For enterprises with credit pools, administrators receive alerts as the team cre ## Related resources * [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 +* [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 * [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 diff --git a/src/content/docs/enterprise/team-management/teams.mdx b/src/content/docs/enterprise/team-management/teams.mdx index ee7aa97..e645e04 100644 --- a/src/content/docs/enterprise/team-management/teams.mdx +++ b/src/content/docs/enterprise/team-management/teams.mdx @@ -21,7 +21,6 @@ Each Warp user can be an admin or member of one team at a time. You can create a new team in two ways: -{/* TODO: Add screenshots for both team creation entry points */} * From the **Warp Drive** side panel, click **+ Create a team**. * In Warp, navigate to **Settings** > **Teams** and follow the prompts. @@ -64,15 +63,15 @@ If you've received an invite link, use it to sign up or log in and join the team If you're a Team Owner and choose to [delete your Warp account](/support-and-community/privacy-and-security/privacy/#delete-your-account-and-data), you'll need to assign a team member as the new owner before your account can be deleted. ::: -### Reload credit consequences when leaving or removing members +### Add-on credit consequences when leaving or removing members -On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) (also known as Add-on Credits) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access: +On Build, Max, and Business plans, [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access: -* **A user leaves a team** - You lose access to any Reload credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin. -* **A user leaves a team** - They lose access to any Reload credits tied to that team. If they rejoin the same team later, they regain access to any unused, non-expired credits. The admin pays a prorated rate for the seat when the user rejoins. -* **An admin deletes the team** - Any remaining Reload credits tied to the team are no longer usable. +* **A user leaves a team** - You lose access to any add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin. +* **An admin removes a member** - That member loses access to any add-on credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. The admin pays a prorated rate for the seat when the user rejoins. +* **An admin deletes the team** - Any remaining add-on credits tied to the team are no longer usable. -Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team. +Add-on credits require an active subscription. Downgrading to the Free plan forfeits access to add-on credits tied to your team. ## Team discoverability @@ -88,7 +87,6 @@ While discoverability is enabled, any new user who joins the team will add a pro Team Owners can transfer ownership to another team member: -{/* TODO: Add screenshot of transfer ownership flow */} 1. Navigate to **Settings** > **Teams** > **Team Members**. 2. Click the three-dot menu icon next to the member you want to transfer ownership to. 3. Click **Transfer ownership**. @@ -113,13 +111,13 @@ We recommend having at least one Team Admin in addition to the Team Owner to pre ### Permissions overview -| | Owner | Admin | Member | +| Action | Owner | Admin | Member | | --- | --- | --- | --- | -|| Create a team | ✓ | ✓ | ✓ | +| Create a team | ✓ | ✓ | ✓ | | Restrict invites by domain | ✓ | ✓ | | | Invite members | ✓ | ✓ | ✓ | | Remove team members | ✓ | ✓ | | -|| Leave a team | | ✓ | ✓ | +| Leave a team | | ✓ | ✓ | | Delete a team | ✓ | | | | Transfer ownership | ✓ | | | | Promote/demote admins | ✓ | ✓ | | @@ -132,7 +130,6 @@ Teams on the **Enterprise** plan can have multiple admins, enabling distributed To promote or demote a team admin: -{/* TODO: Add screenshot of promote/demote admin flow */} 1. Navigate to **Settings** > **Teams** > **Team Members**. 2. Find the user you want to modify and click the three-dot menu icon next to their name. 3. Click **Promote to Admin** or **Demote from Admin**. diff --git a/src/content/docs/knowledge-and-collaboration/teams.mdx b/src/content/docs/knowledge-and-collaboration/teams.mdx index c1ee26f..70b7dc1 100644 --- a/src/content/docs/knowledge-and-collaboration/teams.mdx +++ b/src/content/docs/knowledge-and-collaboration/teams.mdx @@ -24,10 +24,10 @@ You can create a new team in the following ways: * Warp Drive, + Create a team * **Settings** > **Teams** -Before you can invite team members, you will need to give your team a meaningful name. We suggest using a name to represent your organization, company, or project. +Before you can invite team members, you will need to give your team a meaningful name. We suggest using a name to represent your organization, company, or project. :::note -You can rename the team by going to **Settings** > **Teams** and clicking on the team name, entering the new name, and pressing `ENTER` to accept. +You can rename the team by going to **Settings** > **Teams** and clicking on the team name, entering the new name, and pressing `Enter` to accept. ::: ![Teams settings panel with a team name input field and Create button](../../../assets/terminal/team-creation-settings.png) @@ -67,13 +67,13 @@ If you have received an invite link, you can use that link to sign up or log in If you’re a member of a team, you can visit **Settings** > **Teams** to leave a team at any time. Team admins (who created teams) may delete a team only after removing all team members. -On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) (also known as Add-on Credits) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access: +On Build, Max, and Business plans, [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access: -* **A user leaves a team** - You lose access to any Reload credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin. -* **A user leaves a team** - They lose access to any Reload credits tied to that team. If they rejoin the same team later, they regain access to any unused, non-expired credits. The admin pays a prorated rate for the seat when the user rejoins. -* **An admin deletes the team** - Any remaining Reload credits tied to the team are no longer usable. +* **A user leaves a team** - You lose access to any add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin. +* **An admin removes a member** - That member loses access to any add-on credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. The admin pays a prorated rate for the seat when the user rejoins. +* **An admin deletes the team** - Any remaining add-on credits tied to the team are no longer usable. -Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team. +Add-on credits require an active subscription. Downgrading to the Free plan forfeits access to add-on credits tied to your team. ## Team discoverability @@ -93,14 +93,14 @@ Team admins can transfer their role to another team member by going to **Setting If you're a Team admin, and you choose to [delete your Warp](/support-and-community/privacy-and-security/privacy/#manage-your-data) account, the deletion flow will require that you assign a team member as the new admin. ::: -| | Admin | Member | -| ------------------------------------------------------------- | ---------------------------------------------------------------- | -------------------------------------- | -| | This is the Warp user who created a team. There can only be one. | All team members who belong to a team. | -| Create a team | ✓ | | -| Restrict by domain | ✓ | | -| Invite members | ✓ | ✓ | -| Remove team members | ✓ | | -| Leave a team | | ✓ | -| Delete a team | ✓ | | -| Transfer admin | ✓ | | -| [Manage billing](/support-and-community/plans-and-billing/plans-pricing-refunds/) | ✓ | | +| Action | Admin | Member | +| --- | --- | --- | +| Description | The Warp user who created the team. There can only be one. | Team members who belong to the team. | +| Create a team | ✓ | | +| Restrict by domain | ✓ | | +| Invite members | ✓ | ✓ | +| Remove team members | ✓ | | +| Leave a team | | ✓ | +| Delete a team | ✓ | | +| Transfer admin | ✓ | | +| [Manage billing](/support-and-community/plans-and-billing/plans-pricing-refunds/) | ✓ | | diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/index.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/index.mdx index 5a7466c..348dab0 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/index.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/index.mdx @@ -52,7 +52,7 @@ Errors are split into two categories based on what caused the failure: These indicate something the caller needs to fix. When a cloud agent task encounters a user error, the task transitions to the **FAILED** state. -* [`insufficient_credits`](/reference/api-and-sdk/troubleshooting/errors/insufficient-credits/) — Team has no remaining Add-on Credits +* [`insufficient_credits`](/reference/api-and-sdk/troubleshooting/errors/insufficient-credits/) — Team has no remaining add-on credits * [`feature_not_available`](/reference/api-and-sdk/troubleshooting/errors/feature-not-available/) — Feature not included in your current plan * [`external_authentication_required`](/reference/api-and-sdk/troubleshooting/errors/external-authentication-required/) — External service authorization needed * [`not_authorized`](/reference/api-and-sdk/troubleshooting/errors/not-authorized/) — Insufficient permissions for the operation diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/insufficient-credits.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/insufficient-credits.mdx index fab6045..34df8fe 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/insufficient-credits.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/insufficient-credits.mdx @@ -1,11 +1,11 @@ --- title: insufficient_credits description: >- - Your team has exhausted all Add-on Credits for cloud agent usage. Purchase + Your team has exhausted all add-on credits for cloud agent usage. Purchase more credits from your team's billing settings to continue. --- -The `insufficient_credits` error occurs when your team has no remaining Add-on Credits to run cloud agents or integrations. +The `insufficient_credits` error occurs when your team has no remaining add-on credits to run cloud agents or integrations. --- @@ -21,7 +21,7 @@ The `insufficient_credits` error occurs when your team has no remaining Add-on C This error is returned when: -* Your team's Add-on Credits balance has reached zero +* Your team's add-on credits balance has reached zero * A cloud agent task, scheduled run, or integration-triggered run (Slack, Linear) attempts to start but cannot be billed Cloud agent runs consume credits based on usage. When credits are depleted, no new runs can start until credits are replenished. @@ -33,7 +33,7 @@ Cloud agent runs consume credits based on usage. When credits are depleted, no n ```json { "type": "/reference/api-and-sdk/troubleshooting/errors/insufficient-credits/", - "title": "Your team has run out of Add-on Credits. Purchase more credits in your team's billing settings to continue.", + "title": "Your team has run out of add-on credits. Purchase more credits in your team's billing settings to continue.", "status": 403, "instance": "/api/v1/agent/tasks", "title": "Your team has run out of add-on credits. Purchase more credits in your team's billing settings to continue.", @@ -49,7 +49,7 @@ Cloud agent runs consume credits based on usage. When credits are depleted, no n ## How to resolve 1. Go to your team's billing settings in the [Oz web app](https://oz.warp.dev) or Warp desktop app. -2. Purchase additional Add-on Credits. +2. Purchase additional add-on credits. 3. Retry the failed operation. If you are not a team admin, contact your team admin to purchase credits. diff --git a/src/content/docs/reference/cli/api-keys.mdx b/src/content/docs/reference/cli/api-keys.mdx index 9adfe51..3a4eaac 100644 --- a/src/content/docs/reference/cli/api-keys.mdx +++ b/src/content/docs/reference/cli/api-keys.mdx @@ -46,7 +46,7 @@ Warp supports two types of API keys, each with different billing and identity be * **Personal API keys** - Cloud agent runs authenticate as you, just like running an agent from the Warp app or triggering one via Slack or Linear. On Build, Max, and Business plans, runs draw from your plan-included credits, then your Add-on credits — both scoped to your individual user. On Enterprise plans, runs draw from the team-scoped credit pool, per your Enterprise contract terms. * **Team API keys** - Cloud agent runs are not tied to any individual user. On Build, Max, and Business plans, Warp bills the team owner: the owner's plan-included credits, then the owner's Add-on credits. With auto-reload on, usage can trigger a reload on the owner's pool subject to the team-wide monthly spend cap. On Enterprise plans, team API key runs draw from the team-scoped credit pool. When [team GitHub authorization](/agent-platform/cloud-agents/team-access-billing-and-identity/#team-github-authorization) is configured, team key runs can also clone repositories and open pull requests using the Oz by Warp GitHub App. -Team API keys are useful for fully automated workflows, CI/CD pipelines, and scheduled tasks where no specific user context is needed. For the full credit waterfall and how it interacts with Add-on credits, see [Access, billing, and identity permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/) and [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/). +Team API keys are useful for fully automated workflows, CI/CD pipelines, and scheduled tasks where no specific user context is needed. For the full credit waterfall and how it interacts with Add-on credits, see [Access, billing, and identity permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/) and [add-on credits](/support-and-community/plans-and-billing/add-on-credits/). ## Authenticating with API keys 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 cbe47f5..4fa79bd 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 @@ -1,37 +1,33 @@ --- -title: Add-on Credits +title: Add-on credits description: >- - Purchase Add-on Credits to keep using premium AI models after reaching your + Purchase add-on credits to keep using premium AI models after reaching your monthly credit limit. --- Add-on credits let you continue using premium AI models even after you've reached your monthly credit limit — at lower rates and with more control over spending. -:::note -**Add-on Credits** and **Reload credits** are the same thing. Other Warp documentation and in-product copy use both terms interchangeably. -::: +You can manage and purchase add-on credits directly in **Settings** > **Billing and usage**. -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) -![Add-on Credits management surface under Settings > Billing and usage.](../../../../assets/support-and-community/reload-credits.png) +### How do add-on credits work? -### How do Add-on credits work? +Add-on credits extend your AI usage beyond the included monthly quota in your plan. Once your plan’s credits are used up, Warp will automatically begin drawing from your available add-on credits. -Add-on credits extend your AI usage beyond the included monthly quota in your plan. Once your plan’s credits are used up, Warp will automatically begin drawing from your available Add-on credits. +If you’ve enabled **auto-reload**, new credits will be added automatically and billed based on your selected configuration of monthly spending limit and selected purchase amount. -If you’ve enabled **Auto reload**, new credits will be added automatically and billed based on your selected configuration of monthly spending limit and selected purchase amount. - -Add-on credits are available for Build, Max, Business, and Enterprise plans (with custom pricing for Enterprise). On self-serve plans (Build, Max, and Business), Add-on credits are scoped to each individual user; Enterprise uses a team-pooled model. These credits **roll over across billing cycles** and remain valid for **12 months from the purchase date**. +Add-on credits are available for Build, Max, Business, and Enterprise plans (with custom pricing for Enterprise). On self-serve plans (Build, Max, and Business), add-on credits are scoped to each individual user; Enterprise uses a team-pooled model. 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. -### Purchasing Add-on credits +### Purchasing add-on credits You have two options for purchasing more credits: #### 1. Buy on-demand -You can purchase additional Add-on credits at any time directly within the app under **Settings** > **Billing and usage**. Buying more credits upfront provides a larger discount. +You can purchase additional add-on credits at any time directly within the app under **Settings** > **Billing and usage**. Buying more credits upfront provides a larger discount. The table below shows the available credit denominations, their prices, and corresponding discounts: @@ -39,11 +35,11 @@ The table below shows the available credit denominations, their prices, and corr #### 2. Enable auto-reload -Auto reload automatically purchases more credits whenever your balance reaches **100 credits**, ensuring uninterrupted access to premium AI features. +Auto-reload automatically purchases more credits whenever your balance reaches **100 credits**, ensuring uninterrupted access to premium AI features. -By default, **Auto reload is disabled for new subscribers**. When you turn it on, it starts with a **$200 monthly spend limit**, which you can adjust anytime in **Settings** > **Billing and usage**. +By default, **auto-reload is disabled for new subscribers**. When you turn it on, it starts with a **$200 monthly spend limit**, which you can adjust anytime in **Settings** > **Billing and usage**. -Auto reload uses the same denominations and discounts as manual purchases. The denomination you select (e.g., 400, 1,000, 3,000, or 6,500 credits) will repeat each time your balance is depleted, up to your monthly spending limit. Larger denominations offer up to \~40% off per credit. +Auto-reload uses the same denominations and discounts as manual purchases. The denomination you select (e.g., 400, 1,000, 3,000, or 6,500 credits) will repeat each time your balance is depleted, up to your monthly spending limit. Larger denominations offer up to ~40% off per credit. :::note You can opt in and choose your reload amount when subscribing to a paid plan at [app.warp.dev/upgrade](https://app.warp.dev/upgrade), or change your configuration anytime in **Settings** > **Billing and usage**. @@ -51,11 +47,11 @@ You can opt in and choose your reload amount when subscribing to a paid plan at #### **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. 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. * 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. -* Once your limit is reached, no additional Add-on Credit purchases (manual or automatic) will occur until: +* **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. +* Once your limit is reached, no additional add-on credit purchases (manual or automatic) will occur until: * The next calendar month begins, or * You update your limit in settings. @@ -70,43 +66,28 @@ The limit resets automatically at the start of each calendar month, so you can m When your monthly credit balance renews: 1. Warp first consumes your included monthly credits (e.g., Build plan credits). -2. After those are used, Warp continues to draw from any available Add-on Credits. -3. If your Add-on Credits run out and Auto reload is enabled, Warp will automatically purchase more up to your monthly limit. +2. After those are used, Warp continues to draw from any available add-on credits. +3. If your add-on credits run out and auto-reload is enabled, Warp will automatically purchase more up to your monthly limit. You can track your remaining credits and spending in the credits transparency footer and in **Settings** > **Billing and usage**. -#### Teams using Add-on Credits - -On Build, Max, and Business self-serve plans, Add-on credits are scoped to individual users. Each team member's Add-on credits draw down only for their own usage. - -Team admins manage Add-on credit settings for the team in **Settings** > **Billing and usage**: - -* **Team-wide spend cap** — Sets the maximum amount the team can spend on Add-on credits per calendar month, applied across all members. -* **Auto-reload** — When enabled, the admin selects an Add-on credit denomination for the team. Warp automatically purchases that denomination for any user whose Add-on credit balance drops below 100 credits, subject to the team-wide spend cap. While auto-reload is on, individual users cannot purchase Add-on credits manually. -* **Manual purchases** — When auto-reload is off, eligible team members can purchase Add-on credits for themselves, as long as the team stays below the team-wide spend cap. - -**Cloud agent runs on team plans** - -Some cloud agent runs aren't initiated by a specific team member — for example, scheduled runs or runs triggered through a team API key. On self-serve plans (Build, Max, Business), these runs are billed to the **team owner**. +#### Teams using add-on credits -**When auto-reload is off:** +On Build, Max, and Business self-serve plans, add-on credits are scoped to individual users. Each team member's add-on credits draw down only for their own usage. -1. Warp first consumes the team owner's included monthly plan credits. -2. After those are used, Warp draws from the team owner's Add-on credits. -3. If both are exhausted, the request is blocked. +Team admins manage add-on credit settings for the team in **Settings** > **Billing and usage**: -**When auto-reload is on:** +* **Team-wide spend cap** — Sets the maximum amount the team can spend on add-on credits per calendar month, applied across all members. +* **Auto-reload** — When enabled, the admin selects an add-on credit denomination for the team. Warp automatically purchases that denomination for any user whose add-on credit balance drops below 100 credits, subject to the team-wide spend cap. While auto-reload is on, individual users cannot purchase add-on credits manually. +* **Manual purchases** — When auto-reload is off, eligible team members can purchase add-on credits for themselves, as long as the team stays below the team-wide spend cap. -1. Warp first consumes the team owner's included monthly plan credits. -2. After those are used, Warp draws from the team owner's Add-on credits. -3. Cloud agent usage can trigger auto-reload on the team owner's pool — subject to the team-wide monthly spend cap. Once auto-reload tops up the team owner's pool, further cloud agent runs draw from that reloaded balance. -4. If the team-wide spend cap is reached and no credits remain, the request is blocked. +For how cloud agent runs that aren't initiated by a specific team member (scheduled runs, team API key runs) are billed, see [How are cloud agent runs on team plans billed when no individual user triggered them?](/support-and-community/plans-and-billing/pricing-faqs/#how-are-cloud-agent-runs-on-team-plans-billed-when-no-individual-user-triggered-them) in the Pricing FAQs. ### Plan changes and cancellations -Any purchased Add-on Credits remain in your account and can continue to be used for up to 12 months after purchase, as long as you have an active subscription. +Any purchased add-on credits remain in your account and can continue to be used for up to 12 months after purchase, as long as you have an active subscription. -If you move to the Free plan, you'll lose access to any previously purchased Add-on Credits and won't be able to use them. You also can't buy additional Add-on Credits until you're subscribed again. +If you move to the Free plan, you'll lose access to any previously purchased add-on credits and won't be able to use them. You also can't buy additional add-on credits until you're subscribed again. :::caution Add-on credits are tied to your team. Leaving the team, being removed by an admin, or having the team deleted revokes your access to any credits tied to that team. Premium models require an active paid plan. @@ -116,10 +97,10 @@ Add-on credits are tied to your team. Leaving the team, being removed by an admi Add-on credits are tied to the team they were purchased under. The flows below describe what happens in common team-membership scenarios: -* **A user leaves a team** - You lose access to any Add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin. -* **An admin removes a member** - That member loses access to any Add-on credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. -* **An admin deletes the team** - Any remaining Add-on credits tied to the team are no longer usable. +* **A user leaves a team** - You lose access to any add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin. +* **An admin removes a member** - That member loses access to any add-on credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. +* **An admin deletes the team** - Any remaining add-on credits tied to the team are no longer usable. :::note -All unused Add-on credits remain valid for 12 months from purchase, as long as you have an active subscription. +All unused add-on credits remain valid for 12 months from purchase, as long as you have an active subscription. ::: 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 389e374..8fe0030 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 @@ -14,9 +14,9 @@ Warp meters credits across three types of infrastructure — inference, compute, * **AI credits** cover inference: the LLM call itself. Consumed when Warp pays for the model call through Warp-managed providers. * **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; 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 (BYOK or BYOLLM via AWS Bedrock, with Azure Foundry and Google Vertex coming soon). See [platform credits](/support-and-community/plans-and-billing/platform-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 (BYOK, a custom inference endpoint, or BYOLLM). See [platform credits](/support-and-community/plans-and-billing/platform-credits/). -All three buckets draw from the same Warp credit pool and [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/), so you can manage them as a single balance in the Warp app under **Settings** > **Billing and usage**. +All three buckets draw from the same Warp credit pool and [add-on credits](/support-and-community/plans-and-billing/add-on-credits/), so you can manage them as a single balance in the Warp app under **Settings** > **Billing and usage**. Each interaction consumes **at least one credit**, though more complex interactions may use **multiple credits**. Because of factors such as codebase size, model choice, number of tool calls, and the nature of LLMs, credit usage is **non-deterministic** — two similar prompts can still use a different number of credits. @@ -43,7 +43,7 @@ You can view your total credit usage, along with other billing details, in **Set * **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. -* **Hitting the credit limits**: Once you hit your monthly credit limit, your access will depend on your plan. On the Free plan, AI access stops until your next billing cycle. On paid plans, you can continue using AI with usage-based billing via [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/). +* **Hitting the credit limits**: Once you hit your monthly credit limit, your access will depend on your plan. On the Free plan, AI access stops until your next billing cycle. On paid plans, 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** @@ -146,7 +146,7 @@ Platform credits cover Warp's platform infrastructure — run lifecycle, schedul 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. -* **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)](/agent-platform/inference/bring-your-own-api-key/), a [custom inference endpoint](/agent-platform/inference/custom-inference-endpoint/), or BYOLLM via AWS Bedrock (with Azure Foundry and Google Vertex coming soon). +* **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)](/agent-platform/inference/bring-your-own-api-key/), a [custom inference endpoint](/agent-platform/inference/custom-inference-endpoint/), or [BYOLLM](/enterprise/enterprise-features/bring-your-own-llm/). #### Not eligible for platform credits @@ -161,21 +161,6 @@ For a full breakdown of how platform credits work, see [platform credits](/suppo ### 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 a team API key — follow plan-specific billing rules. +Cloud agent runs that aren't initiated by a specific team member — for example, scheduled runs or runs triggered through a team 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 their add-on credits, with optional auto-reload subject to the team-wide spend cap. On Enterprise plans, these runs draw from the team-scoped credit pool per your contract. -#### Self-serve plans - -On Build, Max, and Business plans, these runs are billed to the team owner: - -1. Warp first consumes the team owner's included monthly credits. -2. After those are used, Warp draws from the team owner's Add-on credits. -3. If auto-reload is enabled for the team, cloud agent usage can trigger auto-reload on the team owner's Add-on credit pool, subject to the team-wide spend cap. -4. If the team owner has no available credits and auto-reload is off, the request is blocked. - -[Platform credits](/support-and-community/plans-and-billing/platform-credits/) and compute credits draw from the same Add-on credit pool, so a single balance covers AI credits, platform credits, and compute credits. - -For details on auto-reload, manual purchases, and the team-wide spend cap, see [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/). - -#### Enterprise plans - -On Enterprise plans, these runs draw from the team's Enterprise credit pool. Overage behavior follows your Enterprise contract terms. +For the full waterfall, see [How are cloud agent runs on team plans billed when no individual user triggered them?](/support-and-community/plans-and-billing/pricing-faqs/#how-are-cloud-agent-runs-on-team-plans-billed-when-no-individual-user-triggered-them) in the Pricing FAQs. 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 aaef800..d44581b 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 @@ -7,9 +7,9 @@ description: >- Warp offers flexible plans for individual developers, teams, and enterprises, with credits powering all agent features. Choose from plan-included credits, add-on credit purchases, or automatic reloads. Compare plans, manage billing, and track credit usage from your account settings. -Looking for **Bring Your Own API Key** or **Custom Inference Endpoint**? They've moved to [Inference & providers](/agent-platform/inference/bring-your-own-api-key/) under Warp Agents. +Looking for **Bring Your Own API Key** or **custom inference endpoints**? They've moved to [Inference & providers](/agent-platform/inference/model-choice/) under Warp Agents. * [**Plans & Pricing**](/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 automatic reloads +* [**Add-on credits**](/support-and-community/plans-and-billing/add-on-credits/) - Purchase additional credits or enable automatic reloads * [**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 38403e8..f7df946 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 @@ -19,7 +19,7 @@ Visit [warp.dev/pricing](https://www.warp.dev/pricing) to see the latest plans a **Explore the following sections for more details:** * [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 automatic reloads at discounted rates. +* [Add-on credits](/support-and-community/plans-and-billing/add-on-credits/) — purchase additional credits or enable automatic reloads 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. * [Bring Your Own API Key](/agent-platform/inference/bring-your-own-api-key/) — connect your own model provider API keys for custom usage and billing. * [Custom inference endpoint](/agent-platform/inference/custom-inference-endpoint/) — connect an OpenAI-compatible endpoint such as OpenRouter, LiteLLM, z.ai, or an internal gateway. @@ -47,9 +47,9 @@ If you signed up for an annual Warp subscription by mistake, we can issue a full After 15 days, we will refund you for the remaining full months on your subscription, excluding the first month. -#### Add-on Credits refund policy +#### Add-on credits refund policy -* If you purchased [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) by mistake, you can receive a refund **as long as none of the credits have been used**. Warp cannot refund Add-on Credits if there has been any usage. Add-on Credits remain available for up to **12 months** from the date of purchase, as long as you have an active subscription — if you move to the Free plan, you'll lose access to any remaining Add-on Credits. +* If you purchased [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) by mistake, you can receive a refund **as long as none of the credits have been used**. Warp cannot refund add-on credits if there has been any usage. Add-on credits remain available for up to **12 months** from the date of purchase, as long as you have an active subscription — if you move to the Free plan, you'll lose access to any remaining add-on credits. :::caution Warp does not offer a formal guaranteed uptime Service Level Agreement (SLA). Live incidents can be monitored on our [**Status Page**](https://status.warp.dev/), and open issues are tracked on our [**GitHub Issues**](https://github.com/warpdotdev/Warp/issues). 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 dffb371..5a5b059 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 @@ -5,14 +5,14 @@ description: >- and on local runs with customer-supplied inference. Learn when they apply. --- -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, Amazon Bedrock, or Google Vertex. +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. 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)](/agent-platform/inference/bring-your-own-api-key/) and BYOLLM via Amazon Bedrock or Google Vertex. +Customer-supplied inference covers [Bring Your Own API Key (BYOK)](/agent-platform/inference/bring-your-own-api-key/), [custom inference endpoints](/agent-platform/inference/custom-inference-endpoint/), and [BYOLLM](/enterprise/enterprise-features/bring-your-own-llm/). :::caution -BYOK and customer-supplied inference (BYOLLM via Amazon Bedrock or Google Vertex, plus custom endpoints) are available to individual users and organizations with 10 or fewer employees or users on any plan. Organizations with more than 10 employees or users must be on a Warp Business or Enterprise plan to use BYOK or customer-supplied inference. See Warp's [Terms of Service](https://www.warp.dev/terms-of-service) for details. +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/terms-of-service) for details. ::: ## The three credit buckets @@ -38,7 +38,7 @@ Whether platform credits apply depends on where the agent runs and who's paying ### 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. -* **Local agents on Business or Enterprise with customer-supplied inference** use platform credits when the local agent run uses [BYOK](/agent-platform/inference/bring-your-own-api-key/) or BYOLLM via Amazon Bedrock or Google Vertex. 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. +* **Local agents on Business or Enterprise with customer-supplied inference** use platform credits when the local agent run uses [BYOK](/agent-platform/inference/bring-your-own-api-key/), a [custom inference endpoint](/agent-platform/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. ### Doesn't use platform credits @@ -53,11 +53,12 @@ Platform credits appear in the same billing views as your other 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. +* **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. ## Related pages * [Credits](/support-and-community/plans-and-billing/credits/) - How AI credits are measured and calculated. -* [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) - Purchase additional credits or enable auto reload. +* [Add-on credits](/support-and-community/plans-and-billing/add-on-credits/) - Purchase additional credits or enable auto-reload. * [Bring Your Own API Key](/agent-platform/inference/bring-your-own-api-key/) - Connect your own model provider keys. +* [Custom inference endpoint](/agent-platform/inference/custom-inference-endpoint/) - Route Warp through any OpenAI-compatible endpoint. * [Plans, pricing, and refunds](/support-and-community/plans-and-billing/plans-pricing-refunds/) - Compare plans and refund policies. 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 add574e..b36ecce 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 @@ -24,8 +24,8 @@ After entering your payment details, you’ll receive an invoice and confirmatio 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: -* **Build** — Usage-based plan for individuals or small teams with monthly credits, the ability to [bring your own API key (BYOK)](/agent-platform/inference/bring-your-own-api-key/) or point Warp at a [custom inference endpoint](/agent-platform/inference/custom-inference-endpoint/), and access to [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) (also known as 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 Reload credits on Build. +* **Build** — Usage-based plan for individuals or small teams with monthly credits, the ability to [Bring Your Own API Key (BYOK)](/agent-platform/inference/bring-your-own-api-key/) or point Warp at a [custom inference endpoint](/agent-platform/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. * **Business** — Multi-seat plan for teams. Includes everything in Build, plus admin-configurable data controls, SAML-based SSO, and centralized billing. Available up to the seat limit listed at [warp.dev/pricing](https://www.warp.dev/pricing). * **Enterprise** — Custom plan for organizations that need higher seat counts, [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference, granular admin controls, advanced security and compliance, and dedicated support. @@ -36,7 +36,7 @@ For the most up-to-date feature and usage details — including current per-plan Warp offers two options for larger teams and organizations: * **Business plan**: Self-serve multi-seat plan available for immediate upgrade. Includes admin-configurable data controls and admin-controlled SAML-based SSO. See [warp.dev/pricing](https://www.warp.dev/pricing) for the current seat limit. -* **Enterprise plan**: Custom pricing, credit allowances, and terms — built for larger engineering organizations or teams with advanced security, compliance, or support needs. Enterprise also includes [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference, where Warp routes traffic through AWS Bedrock today — with Azure Foundry and Google Vertex coming soon — with routing, orchestration, governance, and observability provided by Warp. +* **Enterprise plan**: Custom pricing, credit allowances, and terms — built for larger engineering organizations or teams with advanced security, compliance, or support needs. Enterprise also includes [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference, with routing, orchestration, governance, and observability provided by Warp. :::tip If you’d like to explore Enterprise, [contact our sales team](https://www.warp.dev/contact-sales) and someone from Warp will follow up. @@ -124,11 +124,11 @@ Tokens are chunks of text, such as words, parts of code, or characters, that lar Warp now abstracts away token usage, so you don't need to manage or track it directly. You only need to monitor your **credit usage**, which is what’s measured against your plan limits. ::: -If you're curious, you can read the [OpenAI article on tokens](https://help.openai.com/en/articles/4936856-understanding-tokens), or refer to the pricing page for plan-level credit allocations. If you reach your monthly credit limits on the Free plan, premium models pause until your quota resets at the start of your next billing cycle. On paid plans, you can continue using premium models via [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) and auto-reload — see [What if I need more AI usage than my plan includes?](#what-if-i-need-more-ai-usage-than-my-plan-includes) for the full list of options. +If you're curious, you can read the [OpenAI article on tokens](https://help.openai.com/en/articles/4936856-understanding-tokens), or refer to the pricing page for plan-level credit allocations. If you reach your monthly credit limits on the Free plan, premium models pause until your quota resets at the start of your next billing cycle. On paid plans, you can continue using premium models via [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) and auto-reload — see [What if I need more AI usage than my plan includes?](#what-if-i-need-more-ai-usage-than-my-plan-includes) for the full list of options. ### How often do my credits reset? -Allotted credits refill every 30 days from your signup date. When you upgrade to a [paid plan](https://www.warp.dev/pricing), you will be given more credits immediately. You can follow along with your refill period by referencing **Settings** > **Billing and usage**. Alternatively, purchase [Reload credits](/support-and-community/plans-and-billing/add-on-credits/), or enable auto-reload with a monthly spend limit, to continue using premium models beyond your included quota. +Allotted credits refill every 30 days from your signup date. When you upgrade to a [paid plan](https://www.warp.dev/pricing), you will be given more credits immediately. You can follow along with your refill period by referencing **Settings** > **Billing and usage**. Alternatively, purchase [add-on credits](/support-and-community/plans-and-billing/add-on-credits/), or enable auto-reload with a monthly spend limit, to continue using premium models beyond your included quota. :::note Unused credits do not rollover to the next cycle and can't be transferred to other accounts. @@ -139,20 +139,20 @@ Unused credits do not rollover to the next cycle and can't be transferred to oth On the new multi-seat paid plans, credits attribute differently than they did on Warp's older pooled-credit teams: * **Plan-included monthly credits** — Each seat receives its own monthly credit allowance that resets every 30 days based on the team's renewal date. See [warp.dev/pricing](https://www.warp.dev/pricing) for the current per-seat allowance on your plan. -* **Reload credits** — As of May 21, 2026, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to the individual user who purchased or was allocated them, not pooled across the team. A single heavy user can no longer drain the whole team's purchased credits. -* **Grandfathered pooled credits** — Teams that purchased Reload credits before May 21, 2026 keep their existing pooled balance until it's exhausted. Pooled credits are spent down first across the team; all new Reload credit purchases after May 21, 2026 are user-scoped. +* **Add-on credits** — As of May 21, 2026, [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to the individual user who purchased or was allocated them, not pooled across the team. A single heavy user can no longer drain the whole team's purchased credits. +* **Grandfathered pooled credits** — Teams that purchased add-on credits before May 21, 2026 keep their existing pooled balance until it's exhausted. Pooled credits are spent down first across the team; all new add-on credit purchases after May 21, 2026 are user-scoped. * **Team-wide spend cap** — Admins set a single team-wide monthly spend cap that governs auto-reload across the team. See [How does auto-reload work for teams?](#how-does-auto-reload-work-for-teams) below. Enterprise plans support team-scoped credit pools and per-user spend limits separately — see [enterprise billing](/enterprise/support-and-resources/billing/). ### 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 [Reload 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). 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. 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 paid plans (Build, Max, Business), platform-credits billing is in a preview period until July 1, 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, BYOLLM via AWS Bedrock (with Azure Foundry and Google Vertex coming soon), or a custom inference endpoint. 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 until July 1, 2026 on self-serve paid plans. +* **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 until July 1, 2026 on self-serve paid plans. 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. @@ -160,11 +160,11 @@ Local agent runs on Free, Build, or Max — and local runs on Business or Enterp If you regularly run through your plan's monthly credit allowance, you have a few options: -* **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 [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) on Build. See [warp.dev/pricing](https://www.warp.dev/pricing) for current allowances. -* **Purchase Reload credits** — Top up your account on demand. Larger denominations have a better effective rate. Reload credits roll over month-to-month and remain valid for 12 months as long as you have an active subscription — if you move to the Free plan, you'll lose access to any remaining Reload credits. See [Reload 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 Reload 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](/agent-platform/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](/agent-platform/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)). +* **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.dev/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 as long as you have an active subscription — if you move to the Free plan, you'll lose access to any remaining add-on credits. 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](/agent-platform/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](/agent-platform/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)). *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.* @@ -176,14 +176,14 @@ Auto-reload prevents team members from getting blocked by credit exhaustion. It When auto-reload is **on**: -* The admin chooses a Reload credit **denomination**. Larger denominations have a better effective per-credit rate. -* Whenever any individual user's balance (their plan credits plus their user-scoped Reload credits balance) drops below **100 credits**, Warp automatically purchases another bundle of the configured denomination on the team's behalf. +* The admin chooses an add-on credit **denomination**. Larger denominations have a better effective per-credit rate. +* Whenever any individual user's balance (their plan credits plus their user-scoped add-on credits balance) drops below **100 credits**, Warp automatically purchases another bundle of the configured denomination on the team's behalf. * All auto-reload purchases count against a single **team-wide monthly spend cap** that the admin sets. Once the team hits the cap in a given month, auto-reload pauses until the next billing cycle or until the admin raises the cap. -* While auto-reload is on, **individual team members cannot purchase Reload credits manually** — the team-wide auto-reload configuration governs all purchases. +* While auto-reload is on, **individual team members cannot purchase add-on credits manually** — the team-wide auto-reload configuration governs all purchases. -Teams with a pre-May 21, 2026 grandfathered pooled Reload balance: that pooled balance drains first across the team before user-scoped Reload credits and is not counted toward any individual user's 100-credit auto-reload threshold. +Teams with a pre-May 21, 2026 grandfathered pooled add-on credit balance: that pooled balance drains first across the team before user-scoped add-on credits and is not counted toward any individual user's 100-credit auto-reload threshold. -When auto-reload is **off**, eligible team members can purchase Reload credits for themselves, as long as the team stays below the team-wide monthly spend cap. Users keep working as long as they have plan credits, previously purchased Reload credits, or have routed Warp at their own API key or [custom inference endpoint](/agent-platform/inference/custom-inference-endpoint/). Once those run out, premium-model usage is blocked until credits are topped up or the next billing cycle begins. +When auto-reload is **off**, eligible team members can purchase add-on credits for themselves, as long as the team stays below the team-wide monthly spend cap. Users keep working as long as they have plan credits, previously purchased add-on credits, or have routed Warp at their own API key or [custom inference endpoint](/agent-platform/inference/custom-inference-endpoint/). Once those run out, premium-model usage is blocked until credits are topped up or the next billing cycle begins. Auto-reload can be enabled, paused, or reconfigured at any time in **Settings** > **Billing and usage**. @@ -192,13 +192,13 @@ Auto-reload can be enabled, paused, or reconfigured at any time in **Settings** Some cloud agent runs aren't initiated by a specific team member — for example, scheduled runs or runs triggered through a team API key. On self-serve plans (Build, Max, Business), these runs are billed to the **team owner**. :::caution -Team owners: scheduled runs and runs triggered through a team API key draw from your personal credit pool. If auto-reload is enabled on your account, automated jobs can consume your Reload credits and count toward your spend cap. Review your auto-reload settings and team-wide spend cap in **Settings** > **Billing and usage** before relying on scheduled or API-key-triggered cloud agents. +Team owners: scheduled runs and runs triggered through a team API key draw from your personal credit pool. If auto-reload is enabled on your account, automated jobs can consume your add-on credits and count toward your spend cap. Review your auto-reload settings and team-wide spend cap in **Settings** > **Billing and usage** before relying on scheduled or API-key-triggered cloud agents. ::: The waterfall on the owner's account is: 1. First, the owner's plan-included monthly credits are consumed. -2. Once those are exhausted, the owner's Reload credits are consumed. +2. Once those are exhausted, the owner's add-on credits are consumed. When auto-reload is **off**, the request is blocked once both buckets are depleted. When auto-reload is **on**, cloud agent usage can trigger auto-reload on the owner's pool subject to the team-wide spend cap; further cloud agent runs then draw from that reloaded balance until the cap is reached. @@ -267,7 +267,7 @@ On Business and Enterprise, local agent runs that use BYOK still consume platfor 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. -Custom inference endpoints are available on Free, Build, Max, Business, and Enterprise. See [Custom Inference Endpoint](/agent-platform/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. +Custom inference endpoints are available on Free, Build, Max, Business, and Enterprise. See [Custom inference endpoint](/agent-platform/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. @@ -343,7 +343,7 @@ The team at Warp is standing by and ready to help. For subscribers technical iss ### Warp's pricing change FAQs (May 21, 2026) -The following questions cover the May 21, 2026 pricing updates: seat limits per plan, Reload credits attribution, BYOK on Free, the new Custom Inference Endpoint feature, and ZDR / data-controls clarifications. +The following questions cover the May 21, 2026 pricing updates: seat limits per plan, add-on credits attribution, BYOK on Free, the new custom inference endpoint feature, and ZDR / data-controls clarifications. #### Are there new seat limits per plan? @@ -353,21 +353,21 @@ The seat limit governs paid-plan features and credit allocation — it's separat Teams that already exceed the new seat limit on their current plan remain in good standing — you won't be downgraded or charged differently. However, you **cannot add new members above the seat cap**, including backfilling members who leave. To grow past the cap, switch to the next plan up (or to Enterprise) at any time in **Settings** > **Billing and usage**. -#### How are Reload credits being attributed differently? +#### How are add-on credits being attributed differently? -Before May 21, 2026, Reload credits on multi-seat teams were **pooled** — every team member drew from a single shared balance. As of May 21, 2026, **Reload credits are user-scoped**: each user has their own balance, and a single heavy user can no longer drain the whole team's purchased credits. +Before May 21, 2026, add-on credits on multi-seat teams were **pooled** — every team member drew from a single shared balance. As of May 21, 2026, **add-on credits are user-scoped**: each user has their own balance, and a single heavy user can no longer drain the whole team's purchased credits. -**Grandfathering for pre-May 2026 pooled credits**: Existing pooled Reload credit balances are honored. They drain first across the team before any new user-scoped Reload credits are consumed. No new credits will be added to the pooled balance — once it's exhausted, all future Reload credit purchases are user-scoped. +**Grandfathering for pre-May 2026 pooled credits**: Existing pooled add-on credit balances are honored. They drain first across the team before any new user-scoped add-on credits are consumed. No new credits will be added to the pooled balance — once it's exhausted, all future add-on credit purchases are user-scoped. -For details, see [Reload credits](/support-and-community/plans-and-billing/add-on-credits/). +For details, see [add-on credits](/support-and-community/plans-and-billing/add-on-credits/). #### Can I bring my own API key on the Free plan now? -Yes. As of May 21, 2026, **bring your own API key (BYOK)** is available on all plans, including Free. Previously, BYOK required a Build, Business, or Enterprise subscription. You can configure your OpenAI, Anthropic, or Google key in **Settings** > **AI** > **Manage models**. +Yes. As of May 21, 2026, **Bring Your Own API Key (BYOK)** is available on all plans, including Free. Previously, BYOK required a Build, Business, or Enterprise subscription. You can configure your OpenAI, Anthropic, or Google key in **Settings** > **AI** > **Manage models**. See [Bring Your Own API Key](/agent-platform/inference/bring-your-own-api-key/) for the full list of supported providers and setup steps. -#### What is the new Custom Inference Endpoint feature? +#### What is the new custom inference endpoint feature? **Custom inference endpoints** are a new way to route Warp's AI traffic through any OpenAI-compatible inference endpoint — including OpenRouter, LiteLLM, z.ai, and internal gateways your team already runs. Custom inference endpoint support is available on Free, Build, Max, Business, and Enterprise. @@ -377,7 +377,7 @@ Custom inference endpoints differ from BYOK and BYOLLM: * **Custom inference endpoint** sends requests to any OpenAI-compatible URL you control (or that your team runs). * **BYOLLM** is an Enterprise-only managed inference feature where Warp routes traffic through your cloud provider — AWS Bedrock today, with Azure Foundry and Google Vertex coming soon — with full routing, orchestration, governance, and observability provided by Warp. -For setup and details, see [Custom Inference Endpoint](/agent-platform/inference/custom-inference-endpoint/). +For setup and details, see [Custom inference endpoint](/agent-platform/inference/custom-inference-endpoint/). #### How does Zero Data Retention (ZDR) work on the new plans? @@ -392,7 +392,7 @@ If you previously relied on the "automatically enforced team-wide ZDR" language [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 paid plans (Build, Max, Business), platform-credits billing doesn't start until July 1, 2026.** -Between May 21 and June 30, 2026, self-serve paid plans are in a **preview period**: platform-credit consumption is visible in the Warp app's usage breakdown for transparency, but **no platform credits are deducted from your Reload pool or counted against your spend cap**. +Between May 21 and June 30, 2026, self-serve paid plans are in a **preview period**: platform-credit consumption is visible in the Warp app's usage breakdown for transparency, but **no platform credits are deducted from your add-on credit pool or counted against your spend cap**. The preview period applies only to Build, Max, and Business. On **Free**, cloud agent runs draw platform credits from your monthly Warp credit allowance immediately, without a preview period. On **Enterprise**, platform credit usage is governed by your contract — see [enterprise billing](/enterprise/support-and-resources/billing/). diff --git a/src/sidebar.ts b/src/sidebar.ts index e53a198..ed8b12f 100644 --- a/src/sidebar.ts +++ b/src/sidebar.ts @@ -142,11 +142,11 @@ export const sidebarTopics: StarlightSidebarTopicsUserConfig = [ { label: 'Settings file', collapsed: true, - items: [ - { slug: 'terminal/settings', label: 'Overview' }, - { slug: 'terminal/settings/all-settings', label: 'All settings reference' }, - { slug: 'terminal/settings/file-locations', label: 'File locations' }, - ], + items: [ + { slug: 'terminal/settings', label: 'Overview' }, + { slug: 'terminal/settings/all-settings', label: 'All settings reference' }, + { slug: 'terminal/settings/file-locations', label: 'File locations' }, + ], }, { label: 'Warpify overview',