docs: add Platform Credits page and three-bucket model#83
Conversation
Adds a new conceptual page introducing Platform Credits as the third credit bucket in Warp, alongside AI credits and Cloud Agent Credits. Explains when Platform Credits apply (cloud agents on any plan, and local agents on Business/Enterprise with BYOK or BYOLLM inference), when they don't, and where they appear in usage views. Also updates the existing Credits and Plans pages to introduce the three-bucket model and cross-link to the new page. Pricing specifics are deferred to warp.dev/pricing. Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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}
There was a problem hiding this comment.
Overview
This PR adds the Platform Credits billing page and connects it from the existing billing overview pages. The structure is clear, and I did not find security concerns in this documentation-only diff, but the core charge matrix is internally inconsistent and should be corrected before publishing.
Concerns
- The new page says a Warp-managed cloud agent run has no Platform Credits charged, then later says every cloud agent always consumes Platform Credits regardless of whether inference is Warp-managed. That contradiction would make the billing guidance unreliable.
Verdict
Found: 0 critical, 1 important, 1 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
|
|
||
| ### Charged | ||
|
|
||
| * **Cloud agents on any plan** - Any cloud agent run, regardless of which harness (Warp Agent, Claude Code, Codex, Gemini) or where the inference comes from (Warp-managed, BYOK, or BYOLLM). Cloud agents always consume Platform Credits because Oz is orchestrating the run. |
There was a problem hiding this comment.
There was a problem hiding this comment.
Fixed. The original framing of 'when Warp isn't paying for inference or compute' contradicted the actual charge matrix. Reframed the intro and the multi-bucket example so a Warp-managed cloud agent consumes all three buckets (AI credits + Cloud Agent Credits + Platform Credits), matching the 'Charged' section. Same fix applied to the Platform Credits section in credits.mdx and the one-liner in plans-pricing-refunds.mdx.
|
|
||
| Warp meters AI and agent usage in three buckets. Each bucket charges for a different part of the system: | ||
|
|
||
| * **AI credits** - Charged for inference Warp pays for. Consumed by Agent conversations, [Generate](/agent-platform/local-agents/overview/), Workflow autofill, and other AI features. See [credits](/support-and-community/plans-and-billing/credits/) for how AI credits are calculated. |
There was a problem hiding this comment.
💡 [SUGGESTION] Link Generate to its feature page; /agent-platform/local-agents/overview/ is the general agents overview, so this sends readers to the wrong destination.
| * **AI credits** - Charged for inference Warp pays for. Consumed by Agent conversations, [Generate](/agent-platform/local-agents/overview/), Workflow autofill, and other AI features. See [credits](/support-and-community/plans-and-billing/credits/) for how AI credits are calculated. | |
| * **AI credits** - Charged for inference Warp pays for. Consumed by Agent conversations, [Generate](/agent-platform/local-agents/generate/), Workflow autofill, and other AI features. See [credits](/support-and-community/plans-and-billing/credits/) for how AI credits are calculated. |
There was a problem hiding this comment.
Applied in the latest commit. Generate now links to /agent-platform/local-agents/generate/.
- Fix contradiction flagged in PR #83 review: cloud agents always charge Platform Credits regardless of inference source. Reframe intro, three- bucket section, and the multi-bucket example to match the matrix in 'When Platform Credits apply'. - Point Generate link at /agent-platform/local-agents/generate/. - Remove time-unit details from the rate section; defer to warp.dev/pricing. - Drop internal tooltip-label callouts from the admin section. - Tighten plans-pricing-refunds Platform Credits one-liner to match. Co-Authored-By: Oz <oz-agent@warp.dev>
Revision passLatest commit: Addressed bot review comments
Internal-only scrub
Senior-writer pass
Validation
|
…infrastructure Per review feedback, lead with the three-infrastructure framing (inference, compute, platform) rather than the orchestration-layer framing. Each credit bucket now names the kind of infrastructure it covers. Also drop the enterprise custom-rate sentence; warp.dev/pricing remains the source of truth for rates. Co-Authored-By: Oz <oz-agent@warp.dev>
- Reframe Platform Credits intro to lead with the rule (every cloud agent run, plus Business/Enterprise local agent runs with customer-supplied inference) instead of the negative 'when Warp isn't paying' framing. - Align cross-file framing in credits.mdx and plans-pricing-refunds.mdx so all three pages describe Platform Credits in the same terms. - Replace 'Workflow autofill' with linked 'AI Autofill'. - Replace 'Local Oz runs' with 'local agent runs' (Oz run is cloud-only). - Deduplicate the second BYOK parenthetical and normalize BYOLLM wording. - Clarify that self-hosted cloud workers count as cloud agents for Platform Credits purposes. Co-Authored-By: Oz <oz-agent@warp.dev>
|
Audit fixes applied in 617c97e:
Validation: |
1 participant
Summary
Adds documentation for Platform Credits, the third credit bucket in Warp launching as part of the Oz Orchestration Launch (Codename Maestro). Platform Credits cover the Oz orchestration layer for the cases where Warp isn't paying for inference or compute — BYOLLM via Amazon Bedrock or Google Vertex, BYOK direct keys, or self-hosted cloud agents. AI credits and Cloud Agent Credits already cover the other two parts of the system; Platform Credits close the gap for customers who use Oz purely as an orchestration platform.
The new page is purely conceptual: it explains what Platform Credits are, when they apply, when they don't, and where they appear in usage views. Per scope, pricing specifics (per-minute rate, wall-time math, feature-flag rollout modes, telemetry, tier overrides, stale-fail short-circuit) are intentionally not documented and are deferred to warp.dev/pricing or kept internal.
Pages
New
src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx— Conceptual page covering the three-bucket model, how Platform Credits are measured (at the conceptual "while an agent is actively working" level), when they apply / don't apply, and where they appear in user and admin usage surfaces.Edited
src/content/docs/support-and-community/plans-and-billing/credits.mdx— Added a three-bucket model summary near the top (AI credits, Cloud Agent Credits, Platform Credits) and a "Platform Credits" subsection at the bottom mirroring the existing "Cloud Agent Credits" subsection. Both link to the new page.src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx— Added a Platform Credits entry to the credit-types list so the new page is discoverable from the plans landing surface.Out of scope (per launch coordination)
src/sidebar.ts(reserved for the cross-cutting launch PR).vercel.jsonredirects (reserved).Open questions / things to confirm before merge
warp-server/config/prod.yaml,platform_credits_modeis currentlyreport— meaning telemetry is being emitted for calibration but no platform-credit charges are landing in the ledger yet. Staging and local arecharge. I drafted the page to describe Platform Credits as an active billing concept ("are charged") rather than "will be charged," but if Platform Credits won't be inchargemode in prod on the launch date, we may want to soften the language (e.g., "Platform Credits are rolling out for [cohort]") or hold the page until the flag flips. Please confirm with Product/PM.warp.dev/pricing. Confirm the public pricing page will publish the rate by launch; otherwise the "The per-minute rate is published on warp.dev/pricing" sentence should be revised.(Platform)label in the tooltip" and "a stacked usage bar segment." Once the Admin Panel UI is finalized for launch, a screenshot would strengthen the "Where Platform Credits appear" section.Validation
python3 .agents/skills/style_lint/style_lint.py --changed→ 3 files scanned, 0 issues.Context
warp-server/specs/REV-1551/TECH.mdwarp-server/model/types/billing.go::ShouldChargePlatformCreditswarp-server/client/src/components/admin/billing/memberUsageUtils.ts(BUCKET_LABELS)Conversation
Co-Authored-By: Oz oz-agent@warp.dev