From 51edabcb03962bd0a098216cca72efde7a2f36c7 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Tue, 19 May 2026 16:55:45 -0700 Subject: [PATCH 01/14] docs(pricing-may-2026): credits, billing, and service-account model MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Part of the May 14, 2026 pricing-and-packaging docs launch. - Reload credits on self-serve plans are now user-scoped (Build/Max/Business); pre-launch pooled balances are grandfathered and drain first. - Team-wide auto-reload uses a single admin-managed monthly spend cap and triggers when any user drops below 100 credits. - Service-account / team-API-key billing waterfall on self-serve bills the team owner: owner's plan-included credits → owner's Reload credits. Attribution stays on the service account; billing rolls up to the owner. Auto-reload OFF and ON outcomes documented explicitly. - Enterprise service-account traffic draws from the team-scoped pool and falls to pay-as-you-go (PAYG) when depleted. - Membership-change consequences for Reload credits: user leaves, admin removes member, admin deletes team, user downgrades to Free. Rejoining restores non-expired credits. - Active-subscription requirement called out explicitly. - Platform credits draw from the same Reload pool as AI and compute credits. - Cross-page billing copy cleanup in team-access-billing-and-identity.mdx and api-keys.mdx aligns with the new model. - New 'Billing for agent identity runs' subsection on agents.mdx. Co-Authored-By: Oz --- .../agent-platform/cloud-agents/agents.mdx | 9 +++ .../team-access-billing-and-identity.mdx | 38 ++++++++---- .../support-and-resources/billing.mdx | 6 ++ src/content/docs/reference/cli/api-keys.mdx | 6 +- .../plans-and-billing/add-on-credits.mdx | 58 ++++++++++++++----- .../plans-and-billing/credits.mdx | 29 ++++++++-- 6 files changed, 112 insertions(+), 34 deletions(-) diff --git a/src/content/docs/agent-platform/cloud-agents/agents.mdx b/src/content/docs/agent-platform/cloud-agents/agents.mdx index 902e84c1..e3d0148b 100644 --- a/src/content/docs/agent-platform/cloud-agents/agents.mdx +++ b/src/content/docs/agent-platform/cloud-agents/agents.mdx @@ -41,6 +41,15 @@ You don't need to distinguish the two terms in day-to-day use — pick the agent Most teams start with the default agent identity and add more as their automation matures. Creating additional agent identities is worth it when distinct workflows have meaningfully different scopes — for example, a `ci-runner` identity that only needs read-only repo access, an `on-call` identity that holds production deploy credentials and is restricted to incident playbooks, and a `nightly-jobs` identity used by scheduled cleanups. Scoping each identity to a single workflow gives every run the minimum credentials it needs, keeps audit trails attributable to the right bot, and lets you revoke or rotate one workflow's access without touching the rest. +## Billing for agent identity runs + +Agent identity runs are not tied to an individual user, so they have no individual *task billing principal*. Warp resolves the billing principal based on your plan: + +* **Self-serve plans (Build, Max, Business)** - Warp bills the **team owner**. The waterfall on the owner's account is: plan-included monthly credits, then the owner's Reload credits. Attribution stays on the agent identity that initiated the run, but billing rolls up to the owner. With auto-reload off, the request is blocked when both pools are depleted. With auto-reload on, agent identity usage can trigger a reload on the owner's pool subject to the team-wide monthly spend cap. +* **Enterprise plans** - Agent identity runs draw from the team-scoped credit pool. When the pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract. + +See [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) for the full self-serve billing model and [Access, billing, and identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for the cross-plan credit precedence. + ## Plan limits Every team starts with a default agent identity. Additional identities are subject to plan-based limits — see [warp.dev/pricing](https://warp.dev/pricing) for current limits per plan. 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 2c9c768d..e0cfede9 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 @@ -81,7 +81,13 @@ Your team must meet the following requirements to run integrations: * Not supported: Pro, Turbo, Lightspeed, legacy Business. * 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 in a specific order. It starts with any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) the user has, then moves to the user's base credits, followed by the team's Add-on Credits, and finally the user's own Add-on Credits. Enterprises may have different payment options and credit plans that affect this flow. If all applicable credit sources are exhausted, integrations and cloud agents will not work until credits are added. +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: + +* **User-triggered runs on Build, Max, or Business** - Warp draws from any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) the user has, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user and are not shared across the team. +* **Team API key, scheduled, or agent identity runs on Build, Max, or Business** - Warp bills the team owner. The waterfall is: the owner's plan-included credits, then the owner's Reload credits. Attribution stays on the service account or agent identity that initiated the run, but billing rolls up to the owner. 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. When the pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract. + +If all applicable credit sources are exhausted and no auto-reload or PAYG path is available, integrations and cloud agents will not run until credits are added. See [Reload 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. @@ -211,14 +217,16 @@ How credits are consumed depends on how the agent run is triggered and authentic **User-triggered runs** (CLI with personal API key, Slack, Linear, or the Warp app): -* Runs are tied to the triggering user's identity -* Credits are consumed starting with any credit grants specifically allocated for cloud agent usage, then the user's base credits, followed by the team's Add-on Credits, and finally the user's own Add-on Credits +* Runs are tied to the triggering user's identity. +* On Build, Max, and Business plans, credits are consumed starting with any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) allocated to the user, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user. +* On Enterprise plans, runs draw from the team-scoped credit pool, falling back to pay-as-you-go (PAYG) when the pool is depleted, if enabled in the contract. -**Team API key runs** (fully automated or headless workflows): +**Team API key, scheduled, and agent identity runs** (fully automated or headless workflows): -* Runs are not tied to any individual user -* Only the team's Add-on Credit pool is used—no individual base credits are available -* Ideal for CI/CD pipelines, scheduled tasks, and other automated workflows +* Runs are not tied to any individual user. Attribution stays on the service account or agent identity that initiated the run. +* On Build, Max, and Business plans, Warp bills the team owner: the owner's plan-included credits, then the owner's Reload 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 Reload pool subject to the team-wide monthly spend cap. +* On Enterprise plans, these runs draw from the team-scoped credit pool, falling back to pay-as-you-go (PAYG) when the pool is depleted, if enabled in the contract. +* Ideal for CI/CD pipelines, scheduled tasks, and other automated workflows. * For workflows that require code changes (opening pull requests, pushing branches, or writing to a repository), configure [team GitHub authorization](#team-github-authorization) so the agent can authenticate with the Oz by Warp GitHub App. Alternatively, use a [personal API key](/reference/cli/api-keys/) to authenticate as an individual user. For more details on creating and using API keys, see [API Keys](/reference/cli/api-keys/). @@ -236,7 +244,17 @@ All triggers and instructions used by cloud agents are defined and controlled by #### Staying aware of usage -Because triggers and instructions are configured by your team, any credits used when an agent runs are billed to your team's Add-on Credit balance. +Because triggers and instructions are configured by your team, the credits consumed when an agent runs are billed according to the model above: + +* **Build, Max, Business** - User-triggered runs draw from the triggering user's pools (plan-included credits, then their Reload credits). Team API key, scheduled, and agent identity runs are billed to the team owner (the owner's plan-included credits, then the owner's Reload credits, subject to the team-wide spend cap when auto-reload is on). +* **Enterprise** - All runs draw from the team-scoped credit pool, with PAYG as a fallback if enabled in the contract. + +It's the team's responsibility to manage triggers, confirm they behave as intended, and monitor usage. Reviewing triggers, prompts, and agent behavior periodically helps ensure that credit usage aligns with expectations. + +--- + +## Related resources -* It’s the team’s responsibility to manage triggers, confirm they behave as intended, and monitor usage. -* Reviewing triggers, prompts, and agent behavior periodically helps ensure that credit usage aligns with expectations. +* [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) - How user-scoped Reload 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/enterprise/support-and-resources/billing.mdx b/src/content/docs/enterprise/support-and-resources/billing.mdx index b9f91462..525e22df 100644 --- a/src/content/docs/enterprise/support-and-resources/billing.mdx +++ b/src/content/docs/enterprise/support-and-resources/billing.mdx @@ -72,6 +72,10 @@ Enterprise administrators can set monthly spending limits across the following f 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 Reload 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/). +::: + #### Monthly spend alerts Warp sends alerts to administrators as team usage approaches each configured spending limit, so you can adjust caps, purchase more credits, or communicate with your team before agent usage is blocked at the cap. @@ -84,6 +88,8 @@ 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 * [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 +* [Enterprise Analytics API](/enterprise/enterprise-features/analytics-api/) - Programmatic access to team usage and spend data * [Admin Panel](/enterprise/team-management/admin-panel/) - Configure spending limits and billing settings diff --git a/src/content/docs/reference/cli/api-keys.mdx b/src/content/docs/reference/cli/api-keys.mdx index 0d2fb031..969c8ff5 100644 --- a/src/content/docs/reference/cli/api-keys.mdx +++ b/src/content/docs/reference/cli/api-keys.mdx @@ -43,10 +43,10 @@ Team keys without GitHub App authorization are the right fit for automated workf Warp supports two types of API keys, each with different billing and identity behavior: -* **Personal API keys** - Cloud agent runs authenticate as you. These runs can use your personal base credits before drawing from team Add-on Credits, just like running an agent from the Warp app or triggering one via Slack or Linear. -* **Team API keys** - Cloud agent runs are not tied to any individual user. These runs can only draw from your team's pool of Add-on Credits. They cannot use any individual's base credits. 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. +* **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 Reload credits — both scoped to your individual user. On Enterprise plans, runs draw from the team-scoped credit pool (with pay-as-you-go fallback if enabled in the contract). +* **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 Reload 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 billing details, see [Access, Billing, and Identity Permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/). +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 Reload credits, see [Access, billing, and identity permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/) and [Reload 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 193616e4..61b5350e 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 @@ -17,7 +17,9 @@ Add-on credits extend your AI usage beyond the included monthly quota in your pl 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, Business, and Enterprise plans (with custom pricing for Enterprise). 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), Reload 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**. + +Reload 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. :::caution **Legacy plans (Pro, Turbo, Lightspeed) do not support Add-on Credits.** If you're on a legacy plan, you cannot purchase or auto-reload Add-on Credits. To access Add-on Credits, upgrade to the [Build plan](https://app.warp.dev/upgrade). For additional usage on legacy plans, see [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/). @@ -47,10 +49,6 @@ 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 at [app.warp.dev/upgrade](https://app.warp.dev/upgrade), or change your configuration anytime in **Settings** > **Billing and usage**. ::: -:::caution -Add-on credit auto reload will be enabled by default for some legacy plan users when they transition to the Build plan. Please see more in our [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/#what-happens-to-my-current-plan-pro-turbo-lightspeed). -::: - #### **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. @@ -79,21 +77,36 @@ You can track your remaining credits and spending in the credits transparency fo #### Teams using Add-on Credits -For teams on Build or Business plans, **Add-on Credits are shared across all members.** All team credit settings can be managed in `Settings → Billing and usage` by the admin of the team. +On Build, Max, and Business self-serve plans, Reload credits are tied to individual users — they are no longer pooled across the team. Each team member's Reload credits draw down only for their own usage. + +Team admins manage Reload credit settings for the team in **Settings** > **Billing and usage**: -Team admins can manage: +* **Team-wide spend cap** — Sets the maximum amount the team can spend on Reload credits per calendar month, applied across all members. +* **Auto-reload** — When enabled, the admin selects a Reload denomination for the team. Warp automatically purchases that denomination for any user whose Reload balance drops below 100 credits, subject to the team-wide spend cap. While auto-reload is on, individual users cannot purchase Reload credits manually. +* **Manual purchases** — When auto-reload is off, eligible team members can purchase Reload credits for themselves, as long as the team stays below the team-wide spend cap. -* Enabling or disabling Auto reload -* Adjusting monthly spend limits -* Choosing Add-on credit increments -* Viewing usage and spending breakdowns +**Service account and team-scoped API key requests** -Each user on the team has their own monthly credit limit, **but any usage beyond that personal quota draws from the shared team credits**. These shared credits are tracked and billed collectively at the team level. +Some AI requests on Warp can't be tied to an individual user — for example, those made through team-scoped API keys, scheduled agents, agent identities, or other service accounts. For these requests, Warp needs a **task billing principal** to charge usage to. On self-serve plans (Build, Max, and Business), that principal is the **team owner**. Usage attribution stays on the service account, but billing rolls up to the team owner. -For example, if your plan includes 1,500 credits per team member: +**When auto-reload is off:** -* If **User A** reaches their 1,500 limit, any further usage will draw from shared Add-on Credits. -* If **User B** has only used 200 credits, their remaining quota is unaffected, but User A will consume the team's shared credits. +1. Warp first consumes the team owner's included monthly plan credits. +2. After those are used, Warp draws from the team owner's Reload credits. +3. If both are exhausted, the request is blocked. + +**When auto-reload is on:** + +1. Warp first consumes the team owner's included monthly plan credits. +2. After those are used, Warp draws from the team owner's Reload credits. +3. Service-account 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 service-account requests deplete that reloaded balance. +4. If the team-wide spend cap is reached and no credits remain, the request is blocked. + +:::caution +**Grandfathering for pre-May 2026 pooled credits** + +Pooled Add-on credits purchased before May 14, 2026 remain available to the team and are consumed first when team members exceed their included monthly credits. No new pooled credits will be added — Reload credit purchases on or after May 14, 2026 are attributed to individual users. +::: ### Plan changes and cancellations @@ -101,6 +114,19 @@ Any purchased Add-on Credits remain in your account and can continue to be used 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 +Reload credits require an active subscription. If your subscription lapses, ends, or you're no longer a member of a paying team, you lose access to your Reload credits until you reactivate or rejoin. +::: + +#### When membership or subscription changes + +Your access to Reload credits depends on your subscription status and team membership. The flows below describe what happens in common scenarios: + +* **A user leaves a paid team** - When you leave a team, you lose access to any remaining Reload credits tied to it. If you rejoin the same team later, you regain access to any unused, non-expired Reload credits. The admin pays a prorated rate for your seat on rejoin. +* **An admin removes a member** - When an admin removes a member from the team, the member loses access to any remaining Reload credits tied to that team. If they rejoin later, they regain access to any unused, non-expired Reload credits. +* **An admin deletes the team** - Deleting a team removes access to any remaining Reload credits tied to it. Team members can no longer use those credits. +* **A user downgrades to Free** - Downgrading to Free forfeits access to Reload credits tied to your previous team. Reload credits require an active subscription. + :::note -All unused Add-on Credits remain valid for 12 months from purchase, as long as you have an active subscription. +All unused Reload 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 17f7a569..4ce53f7d 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 @@ -134,10 +134,8 @@ The following scenarios use compute credits: #### Not eligible for compute credits -The following scenarios don't use compute credits because they don't run on Warp-hosted compute: - -* **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 ### Platform credits @@ -148,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)](/support-and-community/plans-and-billing/bring-your-own-api-key/) or BYOLLM via Amazon Bedrock or Google Vertex. +* **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)](/support-and-community/plans-and-billing/bring-your-own-api-key/), a [custom inference endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/), or BYOLLM via Amazon Bedrock or Google Vertex. #### Not eligible for platform credits @@ -160,3 +158,24 @@ The following scenarios do **not** use platform credits: * **Third-party agent CLIs run directly** don't use platform credits when you run `claude`, `codex`, or another agent CLI outside of Oz. For a full breakdown of how platform credits work, see [platform credits](/support-and-community/plans-and-billing/platform-credits/). + +### Service account and team-scoped API key billing + +When a request can't be attributed to an individual user — i.e. it has no individual task billing principal — Warp needs another principal to charge the usage to. This applies to team-scoped API keys, scheduled agents, agent identities, and other service accounts. + +#### Self-serve plans + +On Build, Max, and Business plans, the team owner is the task billing principal for these requests. Attribution stays on the service account, but billing rolls up 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 Reload credits. +3. If auto-reload is enabled for the team, service-account usage can trigger auto-reload for the team owner's Reload 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 charges also drain through the same Reload credits pool when the team owner is the billing principal — 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, service-account and team-scoped API key usage draws from the team's Enterprise credit pool. When the pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract; otherwise the request is blocked. Overage behavior follows your Enterprise contract terms. From 761e6ab3e23ae351f22fb07099a22495712fd3fb Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Tue, 19 May 2026 17:07:36 -0700 Subject: [PATCH 02/14] docs(pricing-may-2026): add July 1 platform-credits preview note + trim legacy plan caution - credits.mdx: add a :::note in the Platform credits section explaining the self-serve preview period (May 14 \u2013 June 30, 2026). On self-serve plans, platform credits are visible in the usage breakdown for transparency but not billed; charging starts July 1, 2026. Enterprise unaffected and billed per contract from May 14. - add-on-credits.mdx: trim the legacy plan caution to a brief pointer at Overages (Legacy) rather than calling out Pro/Turbo/Lightspeed by name with extra context that's no longer current. Co-Authored-By: Oz --- .../plans-and-billing/add-on-credits.mdx | 2 +- .../support-and-community/plans-and-billing/credits.mdx | 6 ++++++ 2 files changed, 7 insertions(+), 1 deletion(-) 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 61b5350e..72cfdeb4 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 @@ -22,7 +22,7 @@ Add-on credits are available for Build, Max, Business, and Enterprise plans (wit Reload 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. :::caution -**Legacy plans (Pro, Turbo, Lightspeed) do not support Add-on Credits.** If you're on a legacy plan, you cannot purchase or auto-reload Add-on Credits. To access Add-on Credits, upgrade to the [Build plan](https://app.warp.dev/upgrade). For additional usage on legacy plans, see [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/). +If you're on a legacy plan (Pro, Turbo, or Lightspeed) that hasn't yet transitioned, see [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) for the credit model that applies to your account. Upgrade to a current plan at [app.warp.dev/upgrade](https://app.warp.dev/upgrade) to access Reload credits. ::: ### Purchasing Add-on credits 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 4ce53f7d..1cc6010e 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 @@ -157,6 +157,12 @@ The following scenarios do **not** use platform 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 Oz. +:::note +**Self-serve preview period (May 14 – June 30, 2026)** + +Platform credits apply to self-serve cloud agent runs and to Business BYOK / custom inference endpoint usage where applicable, but **self-serve billing for platform credits doesn't start until July 1, 2026**. During the preview period (May 14 – June 30, 2026), platform-credit consumption is visible in the Warp app's usage breakdown for transparency on Build, Max, and Business, but no platform credits are deducted from your Reload pool or counted against your spend cap. Enterprise plans are billed for platform credits per your contract from May 14 and aren't affected by this preview period. +::: + For a full breakdown of how platform credits work, see [platform credits](/support-and-community/plans-and-billing/platform-credits/). ### Service account and team-scoped API key billing From 002e45200f6062e5ae01441f5981d35381455f94 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 10:59:57 -0700 Subject: [PATCH 03/14] docs(pricing-may-2026): correct launch date May 14 \u2192 May 21, 2026 Co-Authored-By: Oz --- .../plans-and-billing/add-on-credits.mdx | 2 +- .../docs/support-and-community/plans-and-billing/credits.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) 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 72cfdeb4..8ab5e254 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 @@ -105,7 +105,7 @@ Some AI requests on Warp can't be tied to an individual user — for example, th :::caution **Grandfathering for pre-May 2026 pooled credits** -Pooled Add-on credits purchased before May 14, 2026 remain available to the team and are consumed first when team members exceed their included monthly credits. No new pooled credits will be added — Reload credit purchases on or after May 14, 2026 are attributed to individual users. +Pooled Add-on credits purchased before May 21, 2026 remain available to the team and are consumed first when team members exceed their included monthly credits. No new pooled credits will be added — Reload credit purchases on or after May 21, 2026 are attributed to individual users. ::: ### Plan changes and cancellations 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 1cc6010e..adfda1e8 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 @@ -158,9 +158,9 @@ The following scenarios do **not** use platform credits: * **Third-party agent CLIs run directly** don't use platform credits when you run `claude`, `codex`, or another agent CLI outside of Oz. :::note -**Self-serve preview period (May 14 – June 30, 2026)** +**Self-serve preview period (May 21 – June 30, 2026)** -Platform credits apply to self-serve cloud agent runs and to Business BYOK / custom inference endpoint usage where applicable, but **self-serve billing for platform credits doesn't start until July 1, 2026**. During the preview period (May 14 – June 30, 2026), platform-credit consumption is visible in the Warp app's usage breakdown for transparency on Build, Max, and Business, but no platform credits are deducted from your Reload pool or counted against your spend cap. Enterprise plans are billed for platform credits per your contract from May 14 and aren't affected by this preview period. +Platform credits apply to self-serve cloud agent runs and to Business BYOK / custom inference endpoint usage where applicable, but **self-serve billing for platform credits doesn't start until July 1, 2026**. During the preview period (May 21 – June 30, 2026), platform-credit consumption is visible in the Warp app's usage breakdown for transparency on Build, Max, and Business, but no platform credits are deducted from your Reload pool or counted against your spend cap. Enterprise plans are billed for platform credits per your contract from May 21 and aren't affected by this preview period. ::: For a full breakdown of how platform credits work, see [platform credits](/support-and-community/plans-and-billing/platform-credits/). From 958a34af5112c33f33d15c3e04b5638cd6ed05da Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 17:15:51 -0700 Subject: [PATCH 04/14] docs(pricing-may-2026): drop self-serve preview-period note from credits.mdx The July 1, 2026 cutover detail is launch-period guidance that lives only in pricing-faqs.mdx going forward \u2014 canonical feature pages describe the durable platform-credits model without the temporary preview window. Pricing FAQs still cover when self-serve billing starts. Co-Authored-By: Oz --- .../support-and-community/plans-and-billing/credits.mdx | 6 ------ 1 file changed, 6 deletions(-) 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 adfda1e8..4ce53f7d 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 @@ -157,12 +157,6 @@ The following scenarios do **not** use platform 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 Oz. -:::note -**Self-serve preview period (May 21 – June 30, 2026)** - -Platform credits apply to self-serve cloud agent runs and to Business BYOK / custom inference endpoint usage where applicable, but **self-serve billing for platform credits doesn't start until July 1, 2026**. During the preview period (May 21 – June 30, 2026), platform-credit consumption is visible in the Warp app's usage breakdown for transparency on Build, Max, and Business, but no platform credits are deducted from your Reload pool or counted against your spend cap. Enterprise plans are billed for platform credits per your contract from May 21 and aren't affected by this preview period. -::: - For a full breakdown of how platform credits work, see [platform credits](/support-and-community/plans-and-billing/platform-credits/). ### Service account and team-scoped API key billing From c13b40d371eaf9050930b0caba4d71e0c4f15f81 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 17:40:21 -0700 Subject: [PATCH 05/14] docs(pricing-may-2026): drop service-account / agent-identity / task-billing-principal terminology, use 'cloud agent runs' framing Per follow-up review, this terminology added noise without clarifying billing for readers. Simplify to talk about cloud agent runs directly: - add-on-credits.mdx: rename the 'Service account and team-scoped API key requests' subsection to 'Cloud agent runs on team plans'. Drop the 'task billing principal' framing and the 'attribution stays on the service account, billing rolls up' explanation. State the rule plainly: cloud agent runs not initiated by a specific team member are billed to the team owner on self-serve plans. - credits.mdx: same treatment on the 'Service account and team-scoped API key billing' section \u2014 now 'Cloud agent runs on team plans'. Drop the task-billing-principal explanation; keep the self-serve waterfall and the Enterprise team-pool + PAYG fallback. - agents.mdx: remove the 'Billing for agent identity runs' subsection entirely. It duplicated the billing model already covered on the cloud-agents billing page and used the disliked agent-identity framing. The Agent identities page is for the feature concept; the billing model is plan-level and lives elsewhere. - team-access-billing-and-identity.mdx: rename 'Team API key, scheduled, or agent identity runs' to 'Team API key or scheduled cloud agent runs' in the integration credit-precedence bullet, the Additional notes section, and the Staying aware of usage summary. Drop the 'attribution stays on the service account or agent identity' explanation. Co-Authored-By: Oz --- .../docs/agent-platform/cloud-agents/agents.mdx | 9 --------- .../team-access-billing-and-identity.mdx | 8 ++++---- .../plans-and-billing/add-on-credits.mdx | 6 +++--- .../plans-and-billing/credits.mdx | 12 ++++++------ 4 files changed, 13 insertions(+), 22 deletions(-) diff --git a/src/content/docs/agent-platform/cloud-agents/agents.mdx b/src/content/docs/agent-platform/cloud-agents/agents.mdx index e3d0148b..902e84c1 100644 --- a/src/content/docs/agent-platform/cloud-agents/agents.mdx +++ b/src/content/docs/agent-platform/cloud-agents/agents.mdx @@ -41,15 +41,6 @@ You don't need to distinguish the two terms in day-to-day use — pick the agent Most teams start with the default agent identity and add more as their automation matures. Creating additional agent identities is worth it when distinct workflows have meaningfully different scopes — for example, a `ci-runner` identity that only needs read-only repo access, an `on-call` identity that holds production deploy credentials and is restricted to incident playbooks, and a `nightly-jobs` identity used by scheduled cleanups. Scoping each identity to a single workflow gives every run the minimum credentials it needs, keeps audit trails attributable to the right bot, and lets you revoke or rotate one workflow's access without touching the rest. -## Billing for agent identity runs - -Agent identity runs are not tied to an individual user, so they have no individual *task billing principal*. Warp resolves the billing principal based on your plan: - -* **Self-serve plans (Build, Max, Business)** - Warp bills the **team owner**. The waterfall on the owner's account is: plan-included monthly credits, then the owner's Reload credits. Attribution stays on the agent identity that initiated the run, but billing rolls up to the owner. With auto-reload off, the request is blocked when both pools are depleted. With auto-reload on, agent identity usage can trigger a reload on the owner's pool subject to the team-wide monthly spend cap. -* **Enterprise plans** - Agent identity runs draw from the team-scoped credit pool. When the pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract. - -See [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) for the full self-serve billing model and [Access, billing, and identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for the cross-plan credit precedence. - ## Plan limits Every team starts with a default agent identity. Additional identities are subject to plan-based limits — see [warp.dev/pricing](https://warp.dev/pricing) for current limits per plan. 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 e0cfede9..d1980857 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 @@ -84,7 +84,7 @@ Your team must meet the following requirements to run 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: * **User-triggered runs on Build, Max, or Business** - Warp draws from any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) the user has, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user and are not shared across the team. -* **Team API key, scheduled, or agent identity runs on Build, Max, or Business** - Warp bills the team owner. The waterfall is: the owner's plan-included credits, then the owner's Reload credits. Attribution stays on the service account or agent identity that initiated the run, but billing rolls up to the owner. 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. +* **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 Reload 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. When the pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract. If all applicable credit sources are exhausted and no auto-reload or PAYG path is available, integrations and cloud agents will not run until credits are added. See [Reload 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. @@ -221,9 +221,9 @@ How credits are consumed depends on how the agent run is triggered and authentic * On Build, Max, and Business plans, credits are consumed starting with any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) allocated to the user, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user. * On Enterprise plans, runs draw from the team-scoped credit pool, falling back to pay-as-you-go (PAYG) when the pool is depleted, if enabled in the contract. -**Team API key, scheduled, and agent identity runs** (fully automated or headless workflows): +**Team API key and scheduled cloud agent runs** (fully automated or headless workflows): -* Runs are not tied to any individual user. Attribution stays on the service account or agent identity that initiated the run. +* 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 Reload 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 Reload pool subject to the team-wide monthly spend cap. * On Enterprise plans, these runs draw from the team-scoped credit pool, falling back to pay-as-you-go (PAYG) when the pool is depleted, if enabled in the contract. * Ideal for CI/CD pipelines, scheduled tasks, and other automated workflows. @@ -246,7 +246,7 @@ All triggers and instructions used by cloud agents are defined and controlled by Because triggers and instructions are configured by your team, the credits consumed when an agent runs are billed according to the model above: -* **Build, Max, Business** - User-triggered runs draw from the triggering user's pools (plan-included credits, then their Reload credits). Team API key, scheduled, and agent identity runs are billed to the team owner (the owner's plan-included credits, then the owner's Reload credits, subject to the team-wide spend cap when auto-reload is on). +* **Build, Max, Business** - User-triggered runs draw from the triggering user's pools (plan-included credits, then their Reload credits). Team API key and scheduled cloud agent runs are billed to the team owner (the owner's plan-included credits, then the owner's Reload credits, subject to the team-wide spend cap when auto-reload is on). * **Enterprise** - All runs draw from the team-scoped credit pool, with PAYG as a fallback if enabled in the contract. It's the team's responsibility to manage triggers, confirm they behave as intended, and monitor usage. Reviewing triggers, prompts, and agent behavior periodically helps ensure that credit usage aligns with expectations. 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 8ab5e254..5f80df59 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 @@ -85,9 +85,9 @@ Team admins manage Reload credit settings for the team in **Settings** > **Billi * **Auto-reload** — When enabled, the admin selects a Reload denomination for the team. Warp automatically purchases that denomination for any user whose Reload balance drops below 100 credits, subject to the team-wide spend cap. While auto-reload is on, individual users cannot purchase Reload credits manually. * **Manual purchases** — When auto-reload is off, eligible team members can purchase Reload credits for themselves, as long as the team stays below the team-wide spend cap. -**Service account and team-scoped API key requests** +**Cloud agent runs on team plans** -Some AI requests on Warp can't be tied to an individual user — for example, those made through team-scoped API keys, scheduled agents, agent identities, or other service accounts. For these requests, Warp needs a **task billing principal** to charge usage to. On self-serve plans (Build, Max, and Business), that principal is the **team owner**. Usage attribution stays on the service account, but billing rolls up to the team owner. +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**. **When auto-reload is off:** @@ -99,7 +99,7 @@ Some AI requests on Warp can't be tied to an individual user — for example, th 1. Warp first consumes the team owner's included monthly plan credits. 2. After those are used, Warp draws from the team owner's Reload credits. -3. Service-account 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 service-account requests deplete that reloaded balance. +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. :::caution 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 4ce53f7d..53b71406 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 @@ -159,23 +159,23 @@ The following scenarios do **not** use platform credits: For a full breakdown of how platform credits work, see [platform credits](/support-and-community/plans-and-billing/platform-credits/). -### Service account and team-scoped API key billing +### Cloud agent runs on team plans -When a request can't be attributed to an individual user — i.e. it has no individual task billing principal — Warp needs another principal to charge the usage to. This applies to team-scoped API keys, scheduled agents, agent identities, and other service accounts. +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. #### Self-serve plans -On Build, Max, and Business plans, the team owner is the task billing principal for these requests. Attribution stays on the service account, but billing rolls up to the team owner: +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 Reload credits. -3. If auto-reload is enabled for the team, service-account usage can trigger auto-reload for the team owner's Reload pool, subject to the team-wide spend cap. +3. If auto-reload is enabled for the team, cloud agent usage can trigger auto-reload on the team owner's Reload 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 charges also drain through the same Reload credits pool when the team owner is the billing principal — a single balance covers AI credits, platform credits, and compute credits. +[Platform credits](/support-and-community/plans-and-billing/platform-credits/) and compute credits draw from the same Reload credits 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, service-account and team-scoped API key usage draws from the team's Enterprise credit pool. When the pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract; otherwise the request is blocked. Overage behavior follows your Enterprise contract terms. +On Enterprise plans, these runs draw from the team's Enterprise credit pool. When the pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract; otherwise the request is blocked. Overage behavior follows your Enterprise contract terms. From 8c6b4c3f57ceb3e5d30b689a82ddaec83b3949c0 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 17:45:44 -0700 Subject: [PATCH 06/14] Remove PAYG mentions from Enterprise plan billing copy MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Drop the pay-as-you-go (PAYG) fallback language from the Enterprise bullets in cloud-agent team billing and credits — PAYG is an internal contract detail. The Enterprise sections now describe runs as drawing from the team-scoped credit pool, with overage behavior governed by the Enterprise contract terms. Co-Authored-By: Oz --- .../cloud-agents/team-access-billing-and-identity.mdx | 10 +++++----- .../plans-and-billing/credits.mdx | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) 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 d1980857..896ef8dc 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 @@ -85,9 +85,9 @@ When a user triggers an agent through an integration (like Slack or Linear), the * **User-triggered runs on Build, Max, or Business** - Warp draws from any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) the user has, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user and are not shared across the team. * **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 Reload 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. When the pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract. +* **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 or PAYG path is available, integrations and cloud agents will not run until credits are added. See [Reload 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 [Reload 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. @@ -219,13 +219,13 @@ How credits are consumed depends on how the agent run is triggered and authentic * Runs are tied to the triggering user's identity. * On Build, Max, and Business plans, credits are consumed starting with any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) allocated to the user, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user. -* On Enterprise plans, runs draw from the team-scoped credit pool, falling back to pay-as-you-go (PAYG) when the pool is depleted, if enabled in the contract. +* On Enterprise plans, runs draw from the team-scoped credit pool, per your Enterprise contract terms. **Team API key and scheduled cloud agent runs** (fully automated or headless workflows): * 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 Reload 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 Reload pool subject to the team-wide monthly spend cap. -* On Enterprise plans, these runs draw from the team-scoped credit pool, falling back to pay-as-you-go (PAYG) when the pool is depleted, if enabled in the contract. +* On Enterprise plans, these runs draw from the team-scoped credit pool, per your Enterprise contract terms. * Ideal for CI/CD pipelines, scheduled tasks, and other automated workflows. * For workflows that require code changes (opening pull requests, pushing branches, or writing to a repository), configure [team GitHub authorization](#team-github-authorization) so the agent can authenticate with the Oz by Warp GitHub App. Alternatively, use a [personal API key](/reference/cli/api-keys/) to authenticate as an individual user. @@ -247,7 +247,7 @@ All triggers and instructions used by cloud agents are defined and controlled by Because triggers and instructions are configured by your team, the credits consumed when an agent runs are billed according to the model above: * **Build, Max, Business** - User-triggered runs draw from the triggering user's pools (plan-included credits, then their Reload credits). Team API key and scheduled cloud agent runs are billed to the team owner (the owner's plan-included credits, then the owner's Reload credits, subject to the team-wide spend cap when auto-reload is on). -* **Enterprise** - All runs draw from the team-scoped credit pool, with PAYG as a fallback if enabled in the contract. +* **Enterprise** - All runs draw from the team-scoped credit pool, per your Enterprise contract terms. It's the team's responsibility to manage triggers, confirm they behave as intended, and monitor usage. Reviewing triggers, prompts, and agent behavior periodically helps ensure that credit usage aligns with expectations. 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 53b71406..66aaa834 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 @@ -178,4 +178,4 @@ For details on auto-reload, manual purchases, and the team-wide spend cap, see [ #### Enterprise plans -On Enterprise plans, these runs draw from the team's Enterprise credit pool. When the pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract; otherwise the request is blocked. Overage behavior follows your Enterprise contract terms. +On Enterprise plans, these runs draw from the team's Enterprise credit pool. Overage behavior follows your Enterprise contract terms. From 67fe4d2a2a04f79636f276544266bd600a976721 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 18:06:54 -0700 Subject: [PATCH 07/14] Remove legacy plan / Overages mentions from launch-touched docs - add-on-credits.mdx: drop the 'replaces Warp's old pay-as-you-go Overages' intro sentence and the Pro/Turbo/Lightspeed legacy caution. - team-access-billing-and-identity.mdx: collapse the supported / not-supported plan sub-bullets into a single Build/Max/Business (or Enterprise) line; the Pro/Turbo/Lightspeed not-supported note is no longer relevant. Co-Authored-By: Oz --- .../cloud-agents/team-access-billing-and-identity.mdx | 4 +--- .../plans-and-billing/add-on-credits.mdx | 6 +----- 2 files changed, 2 insertions(+), 8 deletions(-) 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 896ef8dc..80999138 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,9 +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 plan that supports **[Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/)**. - * Supported: **Build, Max, Business** - * Not supported: Pro, Turbo, Lightspeed, legacy Business. +* You must be on a **Build, Max, or Business** plan (or an Enterprise plan) that supports [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/). * 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: 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 5f80df59..17d474d9 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 @@ -5,7 +5,7 @@ description: >- monthly credit limit. --- -Add-on credits replace Warp's old [pay-as-you-go Overages](/support-and-community/plans-and-billing/overages-legacy/). They 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. +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. You can manage and purchase Add-on credits directly in **Settings** > **Billing and usage**. @@ -21,10 +21,6 @@ Add-on credits are available for Build, Max, Business, and Enterprise plans (wit Reload 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. -:::caution -If you're on a legacy plan (Pro, Turbo, or Lightspeed) that hasn't yet transitioned, see [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) for the credit model that applies to your account. Upgrade to a current plan at [app.warp.dev/upgrade](https://app.warp.dev/upgrade) to access Reload credits. -::: - ### Purchasing Add-on credits You have two options for purchasing more credits: From bff9c1a7bf937625b27b1d29772c50b8475296bc Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 18:46:15 -0700 Subject: [PATCH 08/14] Cleanup pass: PAYG, BYOLLM scope, model versions - reference/cli/api-keys.mdx: drop the lingering '(with pay-as-you-go fallback if enabled in the contract)' parenthetical from the Personal API keys Enterprise bullet, matching the phrasing used elsewhere on this PR. - credits.mdx: tighten BYOLLM scope to reflect actual launch state (AWS Bedrock today; Azure Foundry and Google Vertex coming soon) in both the AI/compute/platform overview and the platform-credits eligibility bullets. Also normalizes 'Amazon Bedrock' to 'AWS Bedrock' to match the canonical BYOLLM page. - credits.mdx: refresh the example model list from Claude Opus 4.6 / 4.5 / GPT-5.4 / GPT-5.3 Codex / Gemini 3 Pro to the current set (Claude Opus 4.7, Claude Sonnet 4.6, GPT-5.5, Gemini 3.1 Pro) so PR #114 and PR #115's BYOK page cite the same models. Co-Authored-By: Oz --- src/content/docs/reference/cli/api-keys.mdx | 2 +- .../support-and-community/plans-and-billing/credits.mdx | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/docs/reference/cli/api-keys.mdx b/src/content/docs/reference/cli/api-keys.mdx index 969c8ff5..b60eb1e8 100644 --- a/src/content/docs/reference/cli/api-keys.mdx +++ b/src/content/docs/reference/cli/api-keys.mdx @@ -43,7 +43,7 @@ Team keys without GitHub App authorization are the right fit for automated workf Warp supports two types of API keys, each with different billing and identity behavior: -* **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 Reload credits — both scoped to your individual user. On Enterprise plans, runs draw from the team-scoped credit pool (with pay-as-you-go fallback if enabled in the contract). +* **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 Reload 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 Reload 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 Reload credits, see [Access, billing, and identity permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/) and [Reload credits](/support-and-community/plans-and-billing/add-on-credits/). 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 66aaa834..d78e4bf6 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,7 +14,7 @@ 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 Amazon Bedrock or Google Vertex). 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 or BYOLLM via AWS Bedrock, with Azure Foundry and Google Vertex coming soon). 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**. @@ -68,7 +68,7 @@ Several factors influence how many credits are counted for a single interaction: Generally, smaller, faster models typically consume fewer credits than larger, reasoning-based models. -For example, **Claude Opus 4.6** and **Claude Opus 4.5** tend to consume the most tokens and credits in Warp, followed by **Claude Sonnet 4.6, GPT-5.4, GPT-5.3 Codex, Gemini 3 Pro**, and others in roughly that order. This generally correlates with model pricing as well. +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. :::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. @@ -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)](/support-and-community/plans-and-billing/bring-your-own-api-key/), a [custom inference endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/), or BYOLLM via Amazon Bedrock or Google Vertex. +* **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)](/support-and-community/plans-and-billing/bring-your-own-api-key/), a [custom inference endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/), or BYOLLM via AWS Bedrock (with Azure Foundry and Google Vertex coming soon). #### Not eligible for platform credits From ec6098fca78756ca936eda4f63b64e770a53fd1c Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 21:05:27 -0700 Subject: [PATCH 09/14] PR #114 review: address Isaiah's comments - team-access-billing-and-identity.mdx integrations requirement bullet: separate Enterprise from the Add-on Credits framing. Enterprise has its own team credit pool per contract, so grouping it under 'plan that supports Add-on Credits' is incorrect. The new bullet covers Build/Max/Business with Add-on Credits and Enterprise with the team credit pool separately. - add-on-credits.mdx: normalize 'Reload credits' references in the body to 'Add-on credits' so the page is internally consistent with its title and the first half of the page. The switch in the second half was a leftover from an earlier rename attempt. - add-on-credits.mdx 'When membership or subscription changes' section: rewrite to clarify that individual Add-on credits stay with the user across plan changes (Isaiah pointed out the old 'downgrade to Free forfeits Reload credits' claim is no longer accurate). The remaining bullets now scope explicitly to team-pooled grandfathered credits, and the surrounding 'requires an active subscription' caution is removed since individual credits persist regardless. Co-Authored-By: Oz --- .../team-access-billing-and-identity.mdx | 2 +- .../plans-and-billing/add-on-credits.mdx | 35 ++++++++----------- 2 files changed, 16 insertions(+), 21 deletions(-) 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 80999138..e6bad043 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 (or an Enterprise plan) that supports [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/). +* 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: 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 17d474d9..ee3beef2 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 @@ -17,9 +17,9 @@ Add-on credits extend your AI usage beyond the included monthly quota in your pl 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), Reload 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**. -Reload 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 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 @@ -73,13 +73,13 @@ You can track your remaining credits and spending in the credits transparency fo #### Teams using Add-on Credits -On Build, Max, and Business self-serve plans, Reload credits are tied to individual users — they are no longer pooled across the team. Each team member's Reload credits draw down only for their own usage. +On Build, Max, and Business self-serve plans, Add-on credits are tied to individual users — they are no longer pooled across the team. Each team member's Add-on credits draw down only for their own usage. -Team admins manage Reload credit settings for the team in **Settings** > **Billing and 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 Reload credits per calendar month, applied across all members. -* **Auto-reload** — When enabled, the admin selects a Reload denomination for the team. Warp automatically purchases that denomination for any user whose Reload balance drops below 100 credits, subject to the team-wide spend cap. While auto-reload is on, individual users cannot purchase Reload credits manually. -* **Manual purchases** — When auto-reload is off, eligible team members can purchase Reload credits for themselves, as long as the team stays below the team-wide spend cap. +* **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** @@ -88,20 +88,20 @@ Some cloud agent runs aren't initiated by a specific team member — for example **When auto-reload is off:** 1. Warp first consumes the team owner's included monthly plan credits. -2. After those are used, Warp draws from the team owner's Reload 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. **When auto-reload is on:** 1. Warp first consumes the team owner's included monthly plan credits. -2. After those are used, Warp draws from the team owner's Reload 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. :::caution **Grandfathering for pre-May 2026 pooled credits** -Pooled Add-on credits purchased before May 21, 2026 remain available to the team and are consumed first when team members exceed their included monthly credits. No new pooled credits will be added — Reload credit purchases on or after May 21, 2026 are attributed to individual users. +Pooled Add-on credits purchased before May 21, 2026 remain available to the team and are consumed first when team members exceed their included monthly credits. No new pooled credits will be added — Add-on credit purchases on or after May 21, 2026 are attributed to individual users. ::: ### Plan changes and cancellations @@ -110,19 +110,14 @@ Any purchased Add-on Credits remain in your account and can continue to be used 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 -Reload credits require an active subscription. If your subscription lapses, ends, or you're no longer a member of a paying team, you lose access to your Reload credits until you reactivate or rejoin. -::: - #### When membership or subscription changes -Your access to Reload credits depends on your subscription status and team membership. The flows below describe what happens in common scenarios: +Individual Add-on credits stay with the user who purchased or was allocated them and remain available within their 12-month validity window, even across plan changes. The flows below describe what happens in common membership scenarios for team-scoped (grandfathered, pre-May 2026) Add-on credits: -* **A user leaves a paid team** - When you leave a team, you lose access to any remaining Reload credits tied to it. If you rejoin the same team later, you regain access to any unused, non-expired Reload credits. The admin pays a prorated rate for your seat on rejoin. -* **An admin removes a member** - When an admin removes a member from the team, the member loses access to any remaining Reload credits tied to that team. If they rejoin later, they regain access to any unused, non-expired Reload credits. -* **An admin deletes the team** - Deleting a team removes access to any remaining Reload credits tied to it. Team members can no longer use those credits. -* **A user downgrades to Free** - Downgrading to Free forfeits access to Reload credits tied to your previous team. Reload credits require an active subscription. +* **A user leaves a paid team** - You lose access to any team-pooled Add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired pooled credits. The admin pays a prorated rate for your seat on rejoin. +* **An admin removes a member** - That member loses access to any team-pooled Add-on credits tied to the team. If they rejoin later, they regain access to any unused, non-expired pooled credits. +* **An admin deletes the team** - Any remaining team-pooled Add-on credits tied to the team are no longer usable. :::note -All unused Reload 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. ::: From aa8083d0826e7c9aa42ddc98f283cbfca06932c3 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 21:34:47 -0700 Subject: [PATCH 10/14] Drop 'no longer pooled' historical framing on add-on-credits.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 'Teams using Add-on Credits' lead-in said 'Add-on credits are tied to individual users — they are no longer pooled across the team.' Readers don't need the 'no longer' transition framing; the current state is the only one that matters. Now reads 'Add-on credits are scoped to individual users.' Co-Authored-By: Oz --- .../support-and-community/plans-and-billing/add-on-credits.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 ee3beef2..52e2f83f 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 @@ -73,7 +73,7 @@ You can track your remaining credits and spending in the credits transparency fo #### Teams using Add-on Credits -On Build, Max, and Business self-serve plans, Add-on credits are tied to individual users — they are no longer pooled across the team. Each team member's Add-on credits draw down only for their own usage. +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**: From 7708f841104d39b4cca7394a4b8cfd261f19659a Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 21:36:30 -0700 Subject: [PATCH 11/14] Remove the pre-May 2026 grandfathering caution callout Drops the 'Grandfathering for pre-May 2026 pooled credits' :::caution block from add-on-credits.mdx. The historical transition isn't worth calling out in a permanent doc page. Co-Authored-By: Oz --- .../plans-and-billing/add-on-credits.mdx | 6 ------ 1 file changed, 6 deletions(-) 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 52e2f83f..68fb10fc 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 @@ -98,12 +98,6 @@ Some cloud agent runs aren't initiated by a specific team member — for example 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. -:::caution -**Grandfathering for pre-May 2026 pooled credits** - -Pooled Add-on credits purchased before May 21, 2026 remain available to the team and are consumed first when team members exceed their included monthly credits. No new pooled credits will be added — Add-on credit purchases on or after May 21, 2026 are attributed to individual users. -::: - ### 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. From 09fa17736c2d4e68a73456ff29e8a9ea512bebe6 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 21:39:04 -0700 Subject: [PATCH 12/14] Restore 'active subscription' caution and 12-month qualifier MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Earlier I over-interpreted Isaiah's 'this isn't right anymore... if you churn you still can use your individual reload credits' comment and removed the broader 'Add-on credits require an active subscription' caution + the trailing 'as long as you have an active subscription' qualifier. Isaiah's correction was narrower than that — he was flagging the specific 'Downgrading to Free forfeits Reload credits tied to your previous team' bullet, which incorrectly conflated team-pooled and individual credits. Restoring both pieces of copy: - The active-subscription caution before 'When membership or subscription changes'. - The 'as long as you have an active subscription' qualifier on the bottom 12-month-validity note. The lead-in for the 'When membership or subscription changes' section is rewritten so it no longer over-claims 'even across plan changes'. It now reads: 'Individual Add-on credits stay with the user who purchased or was allocated them, so they're not lost when team membership changes alone.' This keeps Isaiah's narrower correction while staying consistent with the restored caution. Co-Authored-By: Oz --- .../plans-and-billing/add-on-credits.mdx | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) 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 68fb10fc..799ba4d5 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 @@ -104,14 +104,18 @@ Any purchased Add-on Credits remain in your account and can continue to be used 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 require an active subscription. If your subscription lapses, ends, or you're no longer a member of a paying team, you lose access to your Add-on credits until you reactivate or rejoin. +::: + #### When membership or subscription changes -Individual Add-on credits stay with the user who purchased or was allocated them and remain available within their 12-month validity window, even across plan changes. The flows below describe what happens in common membership scenarios for team-scoped (grandfathered, pre-May 2026) Add-on credits: +Individual Add-on credits stay with the user who purchased or was allocated them, so they're not lost when team membership changes alone. The flows below describe what happens in common scenarios: * **A user leaves a paid team** - You lose access to any team-pooled Add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired pooled credits. The admin pays a prorated rate for your seat on rejoin. * **An admin removes a member** - That member loses access to any team-pooled Add-on credits tied to the team. If they rejoin later, they regain access to any unused, non-expired pooled credits. * **An admin deletes the team** - Any remaining team-pooled Add-on credits tied to the team are no longer usable. :::note -All unused Add-on credits remain valid for 12 months from purchase. +All unused Add-on credits remain valid for 12 months from purchase, as long as you have an active subscription. ::: From 70e744122a6c8242d6f83997906ed65f16b85aeb Mon Sep 17 00:00:00 2001 From: hongyi-chen Date: Thu, 21 May 2026 16:48:49 +0000 Subject: [PATCH 13/14] PR #114 review pass: align with Isaiah's Slack clarifications - add-on-credits.mdx: rework the "active subscription" caution and the "When membership or subscription changes" intro to match Isaiah's confirmation that Add-on credits are tied to the team, not to the user's service agreement. Drop the "team-pooled" qualifier from the membership bullets (Add-on credits are tied to the team regardless of whether they came from a pooled or individual purchase), and rename the section header to "When team membership changes" since subscription lapses are no longer in scope. Keep the existing restrictive "Plan changes and cancellations" paragraph and 12-month note untouched per Hong Yi's "let's leave it as is" comment. - Normalize "Reload credits" / "Reload pool" / "Reload settings" to "Add-on credits" / "Add-on credit pool" / "Add-on credit settings" across the four other PR files (team-access-billing-and-identity, credits, api-keys, enterprise billing) so the launch copy matches the canonical product name in AGENTS.md's glossary and the title of add-on-credits.mdx. "auto-reload" stays lowercase as the action. Co-Authored-By: Oz --- .../team-access-billing-and-identity.mdx | 14 +++++++------- .../enterprise/support-and-resources/billing.mdx | 2 +- src/content/docs/reference/cli/api-keys.mdx | 6 +++--- .../plans-and-billing/add-on-credits.mdx | 12 ++++++------ .../plans-and-billing/credits.mdx | 6 +++--- 5 files changed, 20 insertions(+), 20 deletions(-) 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 e6bad043..8e9328bc 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 @@ -81,11 +81,11 @@ Your team must meet the following requirements to run 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: -* **User-triggered runs on Build, Max, or Business** - Warp draws from any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) the user has, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user and are not shared across the team. -* **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 Reload 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. +* **User-triggered runs on Build, Max, or Business** - Warp draws from any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) the user has, then the user's plan-included credits, then the user's Add-on credits. Add-on credits are scoped to the individual user and are not shared across the team. +* **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 [Reload 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. @@ -216,13 +216,13 @@ How credits are consumed depends on how the agent run is triggered and authentic **User-triggered runs** (CLI with personal API key, Slack, Linear, or the Warp app): * Runs are tied to the triggering user's identity. -* On Build, Max, and Business plans, credits are consumed starting with any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) allocated to the user, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user. +* On Build, Max, and Business plans, credits are consumed starting with any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) allocated to the user, then the user's plan-included credits, then the user's Add-on credits. Add-on credits are scoped to the individual user. * On Enterprise plans, runs draw from the team-scoped credit pool, per your Enterprise contract terms. **Team API key and scheduled cloud agent runs** (fully automated or headless workflows): * 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 Reload 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 Reload pool subject to the team-wide monthly spend cap. +* 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 off, the request is blocked when both pools are depleted. With auto-reload on, usage can trigger a reload on the owner's Add-on credit pool subject to the team-wide monthly spend cap. * On Enterprise plans, these runs draw from the team-scoped credit pool, per your Enterprise contract terms. * Ideal for CI/CD pipelines, scheduled tasks, and other automated workflows. * For workflows that require code changes (opening pull requests, pushing branches, or writing to a repository), configure [team GitHub authorization](#team-github-authorization) so the agent can authenticate with the Oz by Warp GitHub App. Alternatively, use a [personal API key](/reference/cli/api-keys/) to authenticate as an individual user. @@ -244,7 +244,7 @@ All triggers and instructions used by cloud agents are defined and controlled by Because triggers and instructions are configured by your team, the credits consumed when an agent runs are billed according to the model above: -* **Build, Max, Business** - User-triggered runs draw from the triggering user's pools (plan-included credits, then their Reload credits). Team API key and scheduled cloud agent runs are billed to the team owner (the owner's plan-included credits, then the owner's Reload credits, subject to the team-wide spend cap when auto-reload is on). +* **Build, Max, Business** - User-triggered runs draw from the triggering user's pools (plan-included credits, then their Add-on credits). Team API key and scheduled cloud agent runs are billed to the team owner (the owner's plan-included credits, then the owner's Add-on credits, subject to the team-wide spend cap when auto-reload is on). * **Enterprise** - All runs draw from the team-scoped credit pool, per your Enterprise contract terms. It's the team's responsibility to manage triggers, confirm they behave as intended, and monitor usage. Reviewing triggers, prompts, and agent behavior periodically helps ensure that credit usage aligns with expectations. @@ -253,6 +253,6 @@ It's the team's responsibility to manage triggers, confirm they behave as intend ## Related resources -* [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) - How user-scoped Reload 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/enterprise/support-and-resources/billing.mdx b/src/content/docs/enterprise/support-and-resources/billing.mdx index 525e22df..12ebb5a5 100644 --- a/src/content/docs/enterprise/support-and-resources/billing.mdx +++ b/src/content/docs/enterprise/support-and-resources/billing.mdx @@ -73,7 +73,7 @@ Enterprise administrators can set monthly spending limits across the following f 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 Reload 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/). +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/). ::: #### Monthly spend alerts diff --git a/src/content/docs/reference/cli/api-keys.mdx b/src/content/docs/reference/cli/api-keys.mdx index b60eb1e8..9adfe51b 100644 --- a/src/content/docs/reference/cli/api-keys.mdx +++ b/src/content/docs/reference/cli/api-keys.mdx @@ -43,10 +43,10 @@ Team keys without GitHub App authorization are the right fit for automated workf Warp supports two types of API keys, each with different billing and identity behavior: -* **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 Reload 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 Reload 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. +* **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 Reload credits, see [Access, billing, and identity permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/) and [Reload 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 799ba4d5..67b88d16 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 @@ -105,16 +105,16 @@ Any purchased Add-on Credits remain in your account and can continue to be used 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 require an active subscription. If your subscription lapses, ends, or you're no longer a member of a paying team, you lose access to your Add-on credits until you reactivate or rejoin. +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. ::: -#### When membership or subscription changes +#### When team membership changes -Individual Add-on credits stay with the user who purchased or was allocated them, so they're not lost when team membership changes alone. The flows below describe what happens in common scenarios: +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 paid team** - You lose access to any team-pooled Add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired pooled credits. The admin pays a prorated rate for your seat on rejoin. -* **An admin removes a member** - That member loses access to any team-pooled Add-on credits tied to the team. If they rejoin later, they regain access to any unused, non-expired pooled credits. -* **An admin deletes the team** - Any remaining team-pooled Add-on credits tied to the team are no longer usable. +* **A user leaves a paid 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. 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 d78e4bf6..0a56cea1 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 @@ -168,11 +168,11 @@ Cloud agent runs that aren't initiated by a specific team member — for example 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 Reload credits. -3. If auto-reload is enabled for the team, cloud agent usage can trigger auto-reload on the team owner's Reload pool, subject to the team-wide spend cap. +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 Reload credits pool, so a single balance covers AI credits, platform credits, and compute credits. +[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/). From 5331b437215f2aa3b8eb8e317e0ffda0e01e8721 Mon Sep 17 00:00:00 2001 From: hongyi-chen Date: Thu, 21 May 2026 18:06:15 +0000 Subject: [PATCH 14/14] PR #114: drop "paid" qualifier from "leaves a team" bullet Isaiah's nit on line 115: any team that owns Add-on credits is by definition on a paid plan (Free can't buy them), so "paid" is redundant in the bullet header. Drop the qualifier. Co-Authored-By: Oz --- .../support-and-community/plans-and-billing/add-on-credits.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 67b88d16..83a8e5d3 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 @@ -112,7 +112,7 @@ 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 paid 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. +* **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.