docs(pricing-may-2026): credits, billing, and service-account model#114
Open
hongyi-chen wants to merge 12 commits into
Open
docs(pricing-may-2026): credits, billing, and service-account model#114hongyi-chen wants to merge 12 commits into
hongyi-chen wants to merge 12 commits into
Conversation
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 <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
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 Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Overview
This PR updates billing and credit documentation across cloud agents, API keys, Enterprise billing, and plan credit pages for the May 2026 pricing model.
Concerns
- The PR adds a link to the custom inference endpoint billing page, but that target page is not present in the provided diff or current docs checkout context. This matches the PR description's note that the build depends on a companion PR, so this branch can fail link validation or ship a 404 if merged independently.
Verdict
Found: 0 critical, 1 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
|
|
||
| * **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. |
Contributor
There was a problem hiding this comment.
/support-and-community/plans-and-billing/custom-inference-endpoint/, but that page is not present in the provided diff or current docs checkout context. Merge/add the target page before this link, or remove the link until the dependency lands.
…im 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 <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
…its.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 <oz-agent@warp.dev>
…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 <oz-agent@warp.dev>
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 <oz-agent@warp.dev>
- 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 <oz-agent@warp.dev>
- 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 <oz-agent@warp.dev>
| * 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/). |
Contributor
There was a problem hiding this comment.
nit: do enterprise plans even call them "addon credits" or is it just "reload pool?
|
|
||
| * **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. |
Contributor
There was a problem hiding this comment.
i think technically we don't even let you delete a team with leftover credits remaining on it... but still, i think this is a good callout and covers us if that block changes.
| * **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. |
Contributor
There was a problem hiding this comment.
|
|
||
| :::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. |
Contributor
There was a problem hiding this comment.
nit: we refer to these as add-on credits above in this doc... any reason we switch to Reload here + a couple lines above?
- 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 <oz-agent@warp.dev>
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 <oz-agent@warp.dev>
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 <oz-agent@warp.dev>
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 <oz-agent@warp.dev>
hongyi-chen
added a commit
that referenced
this pull request
May 21, 2026
Umbrella tracker for the May 21, 2026 pricing and packaging docs launch. Populates as the three thematic PRs land: - #114 - Credits, billing, and cloud-agent team billing - #115 - BYOK + custom inference endpoint + BYOLLM - #116 - Plans summary, pricing FAQs, teams copy Co-Authored-By: Oz <oz-agent@warp.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of the May 14, 2026 Warp pricing-and-packaging docs launch. Targets the umbrella branch
hyc/plan-updates.This PR carries the credits + billing model edits. Companion thematic PRs:
hyc/plan-updates-byok-cie-byollm— customer-supplied inference pages (BYOK, CIE, BYOLLM)hyc/plan-updates-plans-faqs-teams— plan summary, pricing FAQs, team-management consequencesWhat's covered
team-access-billing-and-identity.mdxandapi-keys.mdxfor the new user-scoped / team-owner / team-pool model.agents.mdxmirroring the same waterfall language.Files changed
src/content/docs/support-and-community/plans-and-billing/add-on-credits.mdxsrc/content/docs/support-and-community/plans-and-billing/credits.mdxsrc/content/docs/enterprise/support-and-resources/billing.mdxsrc/content/docs/agent-platform/cloud-agents/agents.mdxsrc/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdxsrc/content/docs/reference/cli/api-keys.mdxEditorial rules followed
warp.dev/pricing.Validation
npm run buildwill be verified once all three thematic PRs are open — the build depends on PR #2 (sidebar + custom-inference-endpoint.mdx) for one of the cross-page links to resolve cleanly.Co-Authored-By: Oz oz-agent@warp.dev