docs(pricing-may-2026): credits, billing, and service-account model

src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx

@@ -76,12 +76,16 @@ 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 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 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 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 [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.
@@ -211,14 +215,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 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 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
-* 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.
+* 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.
 
 For more details on creating and using API keys, see [API Keys](/reference/cli/api-keys/).
@@ -236,7 +242,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 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.
+
+---
+
+## 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.
+* [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.

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

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

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**.
 
@@ -17,11 +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), 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**.
 
-:::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/).
-:::
+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
 
@@ -47,10 +45,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,28 +73,49 @@ 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, Add-on credits are scoped to individual users. Each team member's Add-on credits draw down only for their own usage.
+
+Team admins manage Add-on credit settings for the team in **Settings** > **Billing and usage**:
+
+* **Team-wide spend cap** — Sets the maximum amount the team can spend on Add-on credits per calendar month, applied across all members.
+* **Auto-reload** — When enabled, the admin selects an Add-on credit denomination for the team. Warp automatically purchases that denomination for any user whose Add-on credit balance drops below 100 credits, subject to the team-wide spend cap. While auto-reload is on, individual users cannot purchase Add-on credits manually.
+* **Manual purchases** — When auto-reload is off, eligible team members can purchase Add-on credits for themselves, as long as the team stays below the team-wide spend cap.
 
-Team admins can manage:
+**Cloud agent runs on team plans**
 
-* Enabling or disabling Auto reload
-* Adjusting monthly spend limits
-* Choosing Add-on credit increments
-* Viewing usage and spending breakdowns
+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**.
 
-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.
+**When auto-reload is off:**
 
-For example, if your plan includes 1,500 credits per team member:
+1. Warp first consumes the team owner's included monthly plan credits.
+2. After those are used, Warp draws from the team owner's Add-on credits.
+3. If both are exhausted, the request is blocked.
 
-* 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.
+**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 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.
 
 ### 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.
 
 If you move to the Free plan, you'll lose access to any previously purchased Add-on Credits and won't be able to use them. You also can't buy additional Add-on Credits until you're subscribed again.
 
+:::caution
+Add-on credits are tied to your team. Leaving the team, being removed by an admin, or having the team deleted revokes your access to any credits tied to that team. Premium models require an active paid plan.
+:::
+
+#### When team membership changes
+
+Add-on credits are tied to the team they were purchased under. The flows below describe what happens in common team-membership scenarios:
+
+* **A user leaves a team** - You lose access to any Add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin.
+* **An admin removes a member** - That member loses access to any Add-on credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits.
+* **An admin deletes the team** - Any remaining Add-on credits tied to the team are no longer usable.
+
 :::note
-All unused Add-on Credits remain valid for 12 months from purchase, as long as you have an active subscription. 
+All unused Add-on credits remain valid for 12 months from purchase, as long as you have an active subscription.
 :::