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 8b032f02..b5f8575a 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 f039eedf..9fecb697 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 @@ -130,3 +130,24 @@ The following scenarios do **not** use Cloud Agent Credits: * **Local agent runs** — Using `oz agent run` on your local machine * **Self-hosted compute** — Using `oz agent run` on GitHub Actions, CI/CD pipelines, or other self-hosted infrastructure + +### 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.