Skip to content

May 2026 pricing: user-scoped Reload credits + service-account billing#70

Open
hongyi-chen wants to merge 2 commits into
hyc/plan-updatesfrom
hyc/plan-updates-reload
Open

May 2026 pricing: user-scoped Reload credits + service-account billing#70
hongyi-chen wants to merge 2 commits into
hyc/plan-updatesfrom
hyc/plan-updates-reload

Conversation

@hongyi-chen
Copy link
Copy Markdown
Collaborator

Part of the May 2026 Warp pricing docs overhaul. Targets the umbrella branch hyc/plan-updates.

Summary

  • add-on-credits.mdx

    • Adds Max to the plan eligibility list (Build, Max, Business, Enterprise).
    • Rewrites the Teams using Add-on Credits section: Reload credits are now tied to individual users on Build/Max/Business self-serve plans, with an admin-managed team-wide spend cap and auto-reload (admin selects the denomination; fires when any user drops below 100 credits, subject to the spend cap; disables individual purchases when on).
    • Documents the service-account / team-scoped API key billing waterfall to the team admin (included credits → admin's Reload credits → blocked if the admin has none and auto-reload is off; can trigger auto-reload subject to the cap when on).
    • Adds a :::caution "Grandfathering for pre-May 2026 pooled credits" callout: existing pooled credits drain first, no new pooled credits are added.
    • Adds a "Leaving a paid team" paragraph under "Plan changes and cancellations" (user loses access to team-attributed Reload credits; rejoining restores any non-expired credits).
    • Strips the legacy 1,500 credits per team member example and User A/User B framing.
  • credits.mdx

    • Adds a new ### Service account and team-scoped API key billing section after Cloud Agent Credits, with self-serve (Build/Max/Business waterfall) and Enterprise (draws from the team's Enterprise pool, per custom contract terms) subsections. Links back to add-on-credits.mdx for auto-reload/spend-cap details.
    • Model examples left as-is (per the agent task — current list isn't outright wrong).

Editorial rule compliance

  • No per-plan monthly credit counts anywhere in either file.
  • Reload denomination SKU prices ($10/400 … $100/6,500) preserved — these are endpoint SKU prices, not plan-included counts.
  • 100-credit auto-reload threshold preserved — it's a mechanic, not a plan-included count.

Plan / context

Co-Authored-By: Oz oz-agent@warp.dev

- add-on-credits.mdx: User-scoped Reload credits replace pooled team
  credits on Build/Max/Business self-serve plans. Documents team-wide
  spend cap, admin-managed auto-reload semantics, and the service
  account / team-scoped API key billing waterfall to the team admin.
  Adds a grandfathering callout for pre-May 2026 pooled credits and a
  'leaving a paid team' clause under plan changes. Strips legacy
  '1,500 credits per team member' framing.
- credits.mdx: Adds a 'Service account and team-scoped API key billing'
  section covering both self-serve (waterfall: admin's included credits
  -> admin's Reload credits, gated by auto-reload + team-wide spend cap)
  and Enterprise (draws from team Enterprise pool, per contract terms).

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label May 13, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented May 13, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment May 13, 2026 1:36am

Request Review

@oz-for-oss
Copy link
Copy Markdown
Contributor

oz-for-oss Bot commented May 13, 2026

@hongyi-chen

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR updates the billing docs for user-scoped Reload credits, team spend caps, service-account billing waterfalls, and pre-May 2026 pooled-credit grandfathering. I found no blocking correctness or security issues in the changed documentation.

Concerns

  • Minor style issue: one changed Settings path should orient readers to the Warp app, and the new list can use the docs-standard bold term + dash pattern.

Verdict

Found: 0 critical, 0 important, 1 suggestions

Approve with nits

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Comment on lines +84 to +88
Team admins manage Reload credit settings for the team in **Settings** > **Billing and usage**:

* Enabling or disabling Auto reload
* Adjusting monthly spend limits
* Choosing Add-on credit increments
* Viewing usage and spending breakdowns
* **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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 [SUGGESTION] Orient the Settings path to the Warp app and use the docs-standard bold term + dash list pattern.

Suggested change
Team admins manage Reload credit settings for the team in **Settings** > **Billing and usage**:
* Enabling or disabling Auto reload
* Adjusting monthly spend limits
* Choosing Add-on credit increments
* Viewing usage and spending breakdowns
* **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 admins manage Reload credit settings for the team in the Warp app under **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.

The :::caution callout linked to a Pricing FAQs anchor
(#what-happens-to-my-current-plan-pro-turbo-lightspeed) that Agent 1
deleted as part of removing the Oct 30, 2025 pricing-change FAQ
section. The Oct 2025 legacy-plan transition window is also over, so
drop the callout entirely.

Co-Authored-By: Oz <oz-agent@warp.dev>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant