From badcf46e82480bcd6ce1f5cdce9a4af63fc73670 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Sat, 16 May 2026 13:26:09 -0700 Subject: [PATCH 1/4] docs: add Platform Credits page and three-bucket model 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 --- .../plans-and-billing/credits.mdx | 30 ++++++++++ .../plans-pricing-refunds.mdx | 1 + .../plans-and-billing/platform-credits.mdx | 57 +++++++++++++++++++ 3 files changed, 88 insertions(+) create mode 100644 src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx 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 f039eed..9752dea 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 @@ -12,6 +12,14 @@ Any interaction with Warp's Agent consumes credits. Credits are primarily based Credits also include a small hosting fee, charged only when running agents in the cloud, hosted on Warp's infrastructure. For details on cloud agent credits, see [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). +Warp meters usage in three buckets: + +* **AI credits** - The primary bucket. Consumed by Agent conversations and other AI features whenever Warp pays for the model inference. +* **Cloud Agent Credits** - Charged for cloud agent runs that execute on Warp-hosted compute. See [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). +* **Platform Credits** - Charged for the Oz orchestration layer when an agent is actively working but Warp isn't paying for inference or compute (for example, BYOLLM via Amazon Bedrock or self-hosted cloud agents). See [Platform Credits](/support-and-community/plans-and-billing/platform-credits/). + +All three buckets draw from the same plan credit pool and [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/), so you can manage them as a single balance in **Settings** > **Billing and usage**. + Each interaction consumes **at least one credit**, though more complex interactions may use **multiple credits**. Because of factors such as codebase size, model choice, number of tool calls, and the nature of LLMs, credit usage is **non-deterministic** — two similar prompts can still use a different number of credits. :::note @@ -130,3 +138,25 @@ 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 + +### Platform Credits + +Platform Credits cover the Oz orchestration layer when Warp isn't paying for inference or compute — for example, when you bring your own LLM provider (BYOLLM via Amazon Bedrock or Google Vertex), use [Bring Your Own API Key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/), or run cloud agents on your own infrastructure. + +#### Eligible for Platform Credits + +The following scenarios use Platform Credits: + +* **Cloud agents on any plan** — Any cloud agent run, regardless of harness or where inference comes from +* **Local agents on Business or Enterprise with customer-supplied inference** — Local Oz runs that use BYOK or BYOLLM (Amazon Bedrock, Google Vertex) on a Business or Enterprise plan + +#### Not eligible for Platform Credits + +The following scenarios do **not** use Platform Credits: + +* **Local agents on Free, Build, or Max plans** — Regardless of inference source +* **Local agents on Business or Enterprise using Warp-managed inference** — AI credits already cover the cost +* **Regular terminal usage** — Shell commands and non-AI features +* **Third-party harnesses run directly** — Running `claude`, `codex`, or another CLI outside of Oz + +For a full breakdown of how Platform Credits work, see [Platform Credits](/support-and-community/plans-and-billing/platform-credits/). diff --git a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx index 4423f9d..f5536b2 100644 --- a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx @@ -20,6 +20,7 @@ Visit [warp.dev/pricing](https://warp.dev/pricing) to see the latest plans and w * [Credits](/support-and-community/plans-and-billing/credits/) — learn how credits are used and calculated across AI features. * [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) — purchase additional credits or enable automatic reloads at discounted rates. +* [Platform Credits](/support-and-community/plans-and-billing/platform-credits/) — understand the third credit bucket that covers Oz orchestration for BYOLLM, BYOK, and self-hosted cloud agent scenarios. * [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) — connect your own model provider API keys for custom usage and billing. * [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) — information for users on legacy plans with overages enabled. * [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/) — answers to common questions about plans, billing, and usage. Don’t have Warp yet? [Download Warp](https://warp.dev/download) and get started for free today. diff --git a/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx b/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx new file mode 100644 index 0000000..3995daa --- /dev/null +++ b/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx @@ -0,0 +1,57 @@ +--- +title: Platform Credits +description: >- + Platform Credits cover Oz orchestration when Warp isn't paying for inference + or compute. Learn when they apply, when they don't, and where they appear. +--- + +Platform Credits are the third credit bucket in Warp, alongside [AI credits](/support-and-community/plans-and-billing/credits/) and [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). They cover the orchestration layer that Oz provides — task lifecycle, scheduling, integrations, run history, and the rest of the platform — for the cases where Warp isn't already paying for inference or compute. + +Platform Credits exist so that customers who bring their own model provider (BYOLLM via Amazon Bedrock or Google Vertex), connect their own LLM API keys, or run cloud agents on their own infrastructure can still use Oz as the orchestration platform. AI credits and Cloud Agent Credits don't apply in those cases — but Warp is still hosting, coordinating, and tracking the work, and Platform Credits charge for that. + +## The three credit buckets + +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. +* **Cloud Agent Credits** - Charged for cloud agent runs that execute on Warp-hosted compute. Consumed by Slack and Linear integrations, `oz agent run-cloud`, the Oz API, and Cloud Mode in the Warp app. See [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). +* **Platform Credits** - Charged for the Oz orchestration layer when an agent is actively working but Warp isn't paying for inference or compute. Covers BYOLLM, BYOK, and self-hosted cloud agent scenarios. + +The three buckets are independent. A single agent run can consume from more than one bucket — for example, a cloud agent run that uses Warp-managed inference consumes AI credits for the model call and Cloud Agent Credits for the hosted compute, with no Platform Credits charged. + +## How Platform Credits are measured + +Platform Credits accrue while an Oz agent is actively working on a task — from when the task starts running to when it finishes, fails, or is cancelled. Idle time, time spent waiting on user input, and time before the task starts don't accrue Platform Credits. + +The per-minute rate is published on [warp.dev/pricing](https://warp.dev/pricing). Enterprise plans can negotiate a custom rate as part of their contract. + +## When Platform Credits apply + +Whether Platform Credits are charged depends on where the agent runs and who's paying for inference. + +### 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. +* **Local agents on Business or Enterprise with customer-supplied inference** - Local Oz runs on a Business or Enterprise plan that use [Bring Your Own API Key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/) or BYOLLM (Amazon Bedrock, Google Vertex). In these cases Warp isn't paying for the model call, but Oz is still orchestrating the local agent, so Platform Credits apply. + +### Not charged + +* **Local agents on Free, Build, or Max plans** - Regardless of whether you're using Warp-managed inference or BYOK. +* **Local agents on Business or Enterprise using Warp-managed inference** - Warp is already paying for the model call through AI credits, so no separate Platform Credits charge applies. +* **Regular terminal usage** - Running shell commands and using non-AI Warp features never consumes Platform Credits. +* **Third-party harnesses run directly** - Running `claude`, `codex`, or another harness as a standalone CLI without going through Oz. Oz isn't in the path, so there's nothing to charge. + +## Where Platform Credits appear + +Platform Credits roll into the same surfaces as your other credit usage. + +* **Per-user credit totals** - Your total credit usage in **Settings** > **Billing and usage** in the Warp app includes Platform Credits alongside AI and Cloud Agent Credits. +* **Admin usage breakdown** - For team admins, the Admin Panel billing view shows a per-bucket breakdown for each member and for the team as a whole. Platform Credits appear as their own segment in the stacked usage bar with a `(Platform)` label in the tooltip, distinct from `(AI)` and `(Compute)` segments. +* **Add-on Credits and limits** - Platform Credits draw from the same plan and [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) pools as your other credit usage. Once your monthly plan credits are exhausted, Platform Credits continue to consume from Add-on Credits if you have them. + +## Related pages + +* [Credits](/support-and-community/plans-and-billing/credits/) - How AI credits are measured and calculated. +* [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) - Purchase additional credits or enable auto reload. +* [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) - Connect your own model provider keys. +* [Plans, pricing, and refunds](/support-and-community/plans-and-billing/plans-pricing-refunds/) - Compare plans and refund policies. From db2fdd3dd46945d581147cab97660bd7c806d4a7 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Sat, 16 May 2026 13:54:27 -0700 Subject: [PATCH 2/4] docs(platform-credits): align charge matrix and tighten copy - 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 --- .../plans-and-billing/credits.mdx | 8 +++--- .../plans-pricing-refunds.mdx | 2 +- .../plans-and-billing/platform-credits.mdx | 26 +++++++++---------- 3 files changed, 18 insertions(+), 18 deletions(-) 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 9752dea..d6af6f7 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 @@ -16,7 +16,7 @@ Warp meters usage in three buckets: * **AI credits** - The primary bucket. Consumed by Agent conversations and other AI features whenever Warp pays for the model inference. * **Cloud Agent Credits** - Charged for cloud agent runs that execute on Warp-hosted compute. See [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). -* **Platform Credits** - Charged for the Oz orchestration layer when an agent is actively working but Warp isn't paying for inference or compute (for example, BYOLLM via Amazon Bedrock or self-hosted cloud agents). See [Platform Credits](/support-and-community/plans-and-billing/platform-credits/). +* **Platform Credits** - Charged for the Oz orchestration layer that coordinates agent runs. Applies to every cloud agent run, plus local runs on Business and Enterprise plans that use customer-supplied inference (BYOK or BYOLLM via Amazon Bedrock or Google Vertex). See [Platform Credits](/support-and-community/plans-and-billing/platform-credits/). All three buckets draw from the same plan credit pool and [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/), so you can manage them as a single balance in **Settings** > **Billing and usage**. @@ -141,14 +141,14 @@ The following scenarios do **not** use Cloud Agent Credits: ### Platform Credits -Platform Credits cover the Oz orchestration layer when Warp isn't paying for inference or compute — for example, when you bring your own LLM provider (BYOLLM via Amazon Bedrock or Google Vertex), use [Bring Your Own API Key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/), or run cloud agents on your own infrastructure. +Platform Credits charge for the Oz orchestration layer that coordinates agent runs — task lifecycle, scheduling, integrations, run history, and the rest of the platform. #### Eligible for Platform Credits The following scenarios use Platform Credits: -* **Cloud agents on any plan** — Any cloud agent run, regardless of harness or where inference comes from -* **Local agents on Business or Enterprise with customer-supplied inference** — Local Oz runs that use BYOK or BYOLLM (Amazon Bedrock, Google Vertex) on a Business or Enterprise plan +* **Cloud agents on any plan** — Every cloud agent run, regardless of harness or inference source +* **Local agents on Business or Enterprise with customer-supplied inference** — Local Oz runs on a Business or Enterprise plan that use [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 #### Not eligible for Platform Credits diff --git a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx index f5536b2..1554c00 100644 --- a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx @@ -20,7 +20,7 @@ Visit [warp.dev/pricing](https://warp.dev/pricing) to see the latest plans and w * [Credits](/support-and-community/plans-and-billing/credits/) — learn how credits are used and calculated across AI features. * [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) — purchase additional credits or enable automatic reloads at discounted rates. -* [Platform Credits](/support-and-community/plans-and-billing/platform-credits/) — understand the third credit bucket that covers Oz orchestration for BYOLLM, BYOK, and self-hosted cloud agent scenarios. +* [Platform Credits](/support-and-community/plans-and-billing/platform-credits/) — the third credit bucket, which covers Oz orchestration for every cloud agent run and for local Business and Enterprise runs that use customer-supplied inference. * [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) — connect your own model provider API keys for custom usage and billing. * [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) — information for users on legacy plans with overages enabled. * [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/) — answers to common questions about plans, billing, and usage. Don’t have Warp yet? [Download Warp](https://warp.dev/download) and get started for free today. diff --git a/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx b/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx index 3995daa..98c8a7b 100644 --- a/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx @@ -1,29 +1,29 @@ --- title: Platform Credits description: >- - Platform Credits cover Oz orchestration when Warp isn't paying for inference - or compute. Learn when they apply, when they don't, and where they appear. + Platform Credits charge for the Oz orchestration layer. Learn when they + apply, when they don't, and where they appear in your billing. --- -Platform Credits are the third credit bucket in Warp, alongside [AI credits](/support-and-community/plans-and-billing/credits/) and [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). They cover the orchestration layer that Oz provides — task lifecycle, scheduling, integrations, run history, and the rest of the platform — for the cases where Warp isn't already paying for inference or compute. +Platform Credits are the third credit bucket in Warp, alongside [AI credits](/support-and-community/plans-and-billing/credits/) and [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). They charge for the Oz orchestration layer — task lifecycle, scheduling, integrations, run history, and the rest of the platform that coordinates your agent runs. -Platform Credits exist so that customers who bring their own model provider (BYOLLM via Amazon Bedrock or Google Vertex), connect their own LLM API keys, or run cloud agents on their own infrastructure can still use Oz as the orchestration platform. AI credits and Cloud Agent Credits don't apply in those cases — but Warp is still hosting, coordinating, and tracking the work, and Platform Credits charge for that. +Platform Credits apply to every cloud agent run, and to local agent runs on Business and Enterprise plans that use customer-supplied inference — [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. They don't apply to local runs on Free, Build, or Max plans, or to local Business and Enterprise runs where Warp pays for inference through AI credits. ## The three credit buckets 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. +* **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. * **Cloud Agent Credits** - Charged for cloud agent runs that execute on Warp-hosted compute. Consumed by Slack and Linear integrations, `oz agent run-cloud`, the Oz API, and Cloud Mode in the Warp app. See [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). -* **Platform Credits** - Charged for the Oz orchestration layer when an agent is actively working but Warp isn't paying for inference or compute. Covers BYOLLM, BYOK, and self-hosted cloud agent scenarios. +* **Platform Credits** - Charged for the Oz orchestration layer that coordinates agent runs. Applies to every cloud agent run, plus local runs on Business and Enterprise plans that use customer-supplied inference. -The three buckets are independent. A single agent run can consume from more than one bucket — for example, a cloud agent run that uses Warp-managed inference consumes AI credits for the model call and Cloud Agent Credits for the hosted compute, with no Platform Credits charged. +The three buckets are independent and a single run can consume from more than one. A Warp-managed cloud agent run, for example, consumes AI credits for the model call, Cloud Agent Credits for the hosted compute, and Platform Credits for the orchestration layer. ## How Platform Credits are measured Platform Credits accrue while an Oz agent is actively working on a task — from when the task starts running to when it finishes, fails, or is cancelled. Idle time, time spent waiting on user input, and time before the task starts don't accrue Platform Credits. -The per-minute rate is published on [warp.dev/pricing](https://warp.dev/pricing). Enterprise plans can negotiate a custom rate as part of their contract. +See [warp.dev/pricing](https://warp.dev/pricing) for current rates. Enterprise plans can negotiate a custom rate as part of their contract. ## When Platform Credits apply @@ -31,12 +31,12 @@ Whether Platform Credits are charged depends on where the agent runs and who's p ### 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. -* **Local agents on Business or Enterprise with customer-supplied inference** - Local Oz runs on a Business or Enterprise plan that use [Bring Your Own API Key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/) or BYOLLM (Amazon Bedrock, Google Vertex). In these cases Warp isn't paying for the model call, but Oz is still orchestrating the local agent, so Platform Credits apply. +* **Cloud agents on any plan** - Every cloud agent run charges Platform Credits, regardless of harness (Warp Agent, Claude Code, Codex, Gemini) or inference source (Warp-managed, BYOK, or BYOLLM). Oz is always orchestrating the run. +* **Local agents on Business or Enterprise with customer-supplied inference** - Local Oz runs on a Business or Enterprise plan that use [Bring Your Own API Key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/) or BYOLLM (Amazon Bedrock, Google Vertex). Warp isn't paying for the model call, but Oz is still orchestrating the local agent. ### Not charged -* **Local agents on Free, Build, or Max plans** - Regardless of whether you're using Warp-managed inference or BYOK. +* **Local agents on Free, Build, or Max plans** - No Platform Credits charge, regardless of whether you use Warp-managed inference or BYOK. * **Local agents on Business or Enterprise using Warp-managed inference** - Warp is already paying for the model call through AI credits, so no separate Platform Credits charge applies. * **Regular terminal usage** - Running shell commands and using non-AI Warp features never consumes Platform Credits. * **Third-party harnesses run directly** - Running `claude`, `codex`, or another harness as a standalone CLI without going through Oz. Oz isn't in the path, so there's nothing to charge. @@ -46,8 +46,8 @@ Whether Platform Credits are charged depends on where the agent runs and who's p Platform Credits roll into the same surfaces as your other credit usage. * **Per-user credit totals** - Your total credit usage in **Settings** > **Billing and usage** in the Warp app includes Platform Credits alongside AI and Cloud Agent Credits. -* **Admin usage breakdown** - For team admins, the Admin Panel billing view shows a per-bucket breakdown for each member and for the team as a whole. Platform Credits appear as their own segment in the stacked usage bar with a `(Platform)` label in the tooltip, distinct from `(AI)` and `(Compute)` segments. -* **Add-on Credits and limits** - Platform Credits draw from the same plan and [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) pools as your other credit usage. Once your monthly plan credits are exhausted, Platform Credits continue to consume from Add-on Credits if you have them. +* **Admin usage breakdown** - For team admins, the Admin Panel billing view shows a per-bucket breakdown for each member and for the team as a whole. Platform Credits appear as their own segment in the stacked usage bar, distinct from the AI and Compute segments. +* **Add-on Credits and limits** - Platform Credits draw from the same plan credits and [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) pools as your other usage. Once your monthly plan credits are exhausted, Platform Credits continue to consume from Add-on Credits if you have them. ## Related pages From bad4452b715f8e867cff58f91c5ca3ee13d50bc0 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Sat, 16 May 2026 14:22:29 -0700 Subject: [PATCH 3/4] docs: reframe Platform Credits around inference / compute / platform 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 --- .../plans-and-billing/credits.mdx | 10 ++++---- .../plans-and-billing/platform-credits.mdx | 24 ++++++++++--------- 2 files changed, 18 insertions(+), 16 deletions(-) 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 d6af6f7..57b9ab8 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 @@ -12,11 +12,11 @@ Any interaction with Warp's Agent consumes credits. Credits are primarily based Credits also include a small hosting fee, charged only when running agents in the cloud, hosted on Warp's infrastructure. For details on cloud agent credits, see [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). -Warp meters usage in three buckets: +Warp meters credits across three types of infrastructure — inference, compute, and platform — each with its own bucket: -* **AI credits** - The primary bucket. Consumed by Agent conversations and other AI features whenever Warp pays for the model inference. -* **Cloud Agent Credits** - Charged for cloud agent runs that execute on Warp-hosted compute. See [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). -* **Platform Credits** - Charged for the Oz orchestration layer that coordinates agent runs. Applies to every cloud agent run, plus local runs on Business and Enterprise plans that use customer-supplied inference (BYOK or BYOLLM via Amazon Bedrock or Google Vertex). See [Platform Credits](/support-and-community/plans-and-billing/platform-credits/). +* **AI credits** - Charged for inference infrastructure Warp pays for. Consumed by Agent conversations and other AI features that route through Warp-managed model providers. +* **Cloud Agent Credits** - Charged for compute infrastructure when cloud agents run on Warp-hosted compute. See [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). +* **Platform Credits** - Charged for platform infrastructure (run lifecycle, integrations, dashboard, APIs, and observability) when Warp isn't paying for inference or compute. Applies to every cloud agent run, plus local runs on Business and Enterprise plans that use customer-supplied inference (BYOK or BYOLLM via Amazon Bedrock or Google Vertex). See [Platform Credits](/support-and-community/plans-and-billing/platform-credits/). All three buckets draw from the same plan credit pool and [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/), so you can manage them as a single balance in **Settings** > **Billing and usage**. @@ -141,7 +141,7 @@ The following scenarios do **not** use Cloud Agent Credits: ### Platform Credits -Platform Credits charge for the Oz orchestration layer that coordinates agent runs — task lifecycle, scheduling, integrations, run history, and the rest of the platform. +Platform Credits charge for Warp's platform infrastructure — run lifecycle, scheduling, integrations, dashboard, APIs, and observability — when Warp isn't paying for the inference or compute. #### Eligible for Platform Credits diff --git a/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx b/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx index 98c8a7b..1b6becc 100644 --- a/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx @@ -1,29 +1,31 @@ --- title: Platform Credits description: >- - Platform Credits charge for the Oz orchestration layer. Learn when they - apply, when they don't, and where they appear in your billing. + Platform Credits charge for Warp's platform infrastructure when Warp isn't + paying for inference or compute. Learn when they apply and where they appear. --- -Platform Credits are the third credit bucket in Warp, alongside [AI credits](/support-and-community/plans-and-billing/credits/) and [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). They charge for the Oz orchestration layer — task lifecycle, scheduling, integrations, run history, and the rest of the platform that coordinates your agent runs. +Warp meters credits across three types of infrastructure: **inference** (the model call), **compute** (the sandbox an agent runs in), and **platform** (everything that runs around the agent — run lifecycle, integrations, dashboard, APIs, and observability). Each type maps to one credit bucket: [AI credits](/support-and-community/plans-and-billing/credits/), [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits), and Platform Credits. + +Platform Credits charge for Warp's platform infrastructure when Warp isn't paying for the inference or compute. Customers who bring their own model provider (BYOLLM via Amazon Bedrock or Google Vertex), connect their own LLM API keys, or run cloud agents on their own compute still rely on Warp's platform to coordinate, observe, and integrate their agents — and Platform Credits charge for that. Platform Credits apply to every cloud agent run, and to local agent runs on Business and Enterprise plans that use customer-supplied inference — [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. They don't apply to local runs on Free, Build, or Max plans, or to local Business and Enterprise runs where Warp pays for inference through AI credits. ## The three credit buckets -Warp meters AI and agent usage in three buckets. Each bucket charges for a different part of the system: +Each credit bucket charges for a different layer of the infrastructure Warp provides: -* **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. -* **Cloud Agent Credits** - Charged for cloud agent runs that execute on Warp-hosted compute. Consumed by Slack and Linear integrations, `oz agent run-cloud`, the Oz API, and Cloud Mode in the Warp app. See [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). -* **Platform Credits** - Charged for the Oz orchestration layer that coordinates agent runs. Applies to every cloud agent run, plus local runs on Business and Enterprise plans that use customer-supplied inference. +* **AI credits** - Charged for inference infrastructure Warp pays for. Consumed by Agent conversations, [Generate](/agent-platform/local-agents/generate/), Workflow autofill, and other AI features that route through Warp-managed model providers. See [credits](/support-and-community/plans-and-billing/credits/) for how AI credits are calculated. +* **Cloud Agent Credits** - Charged for compute infrastructure when cloud agents run on Warp-hosted compute. Consumed by Slack and Linear integrations, `oz agent run-cloud`, the Oz API, and Cloud Mode in the Warp app. See [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). +* **Platform Credits** - Charged for platform infrastructure (run lifecycle, integrations, dashboard, APIs, and observability) when an agent is actively working but Warp isn't paying for inference or compute. Applies to every cloud agent run, plus local runs on Business and Enterprise plans that use customer-supplied inference. -The three buckets are independent and a single run can consume from more than one. A Warp-managed cloud agent run, for example, consumes AI credits for the model call, Cloud Agent Credits for the hosted compute, and Platform Credits for the orchestration layer. +The three buckets are independent and a single run can consume from more than one. A Warp-managed cloud agent run, for example, consumes AI credits for the model call, Cloud Agent Credits for the hosted compute, and Platform Credits for the platform infrastructure that runs the agent. ## How Platform Credits are measured Platform Credits accrue while an Oz agent is actively working on a task — from when the task starts running to when it finishes, fails, or is cancelled. Idle time, time spent waiting on user input, and time before the task starts don't accrue Platform Credits. -See [warp.dev/pricing](https://warp.dev/pricing) for current rates. Enterprise plans can negotiate a custom rate as part of their contract. +See [warp.dev/pricing](https://warp.dev/pricing) for current rates. ## When Platform Credits apply @@ -31,8 +33,8 @@ Whether Platform Credits are charged depends on where the agent runs and who's p ### Charged -* **Cloud agents on any plan** - Every cloud agent run charges Platform Credits, regardless of harness (Warp Agent, Claude Code, Codex, Gemini) or inference source (Warp-managed, BYOK, or BYOLLM). Oz is always orchestrating the run. -* **Local agents on Business or Enterprise with customer-supplied inference** - Local Oz runs on a Business or Enterprise plan that use [Bring Your Own API Key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/) or BYOLLM (Amazon Bedrock, Google Vertex). Warp isn't paying for the model call, but Oz is still orchestrating the local agent. +* **Cloud agents on any plan** - Every cloud agent run charges Platform Credits, regardless of harness (Warp Agent, Claude Code, Codex, Gemini) or inference source (Warp-managed, BYOK, or BYOLLM). Warp's platform infrastructure is always running the agent. +* **Local agents on Business or Enterprise with customer-supplied inference** - Local Oz runs on a Business or Enterprise plan that use [Bring Your Own API Key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/) or BYOLLM (Amazon Bedrock, Google Vertex). Warp isn't paying for the model call, but Warp's platform infrastructure is still running the local agent. ### Not charged From 617c97e0a2abf3de6f92fae19feea1b45e10264d Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Sat, 16 May 2026 16:31:16 -0700 Subject: [PATCH 4/4] docs(platform-credits): address audit findings - 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 --- .../plans-and-billing/credits.mdx | 6 +++--- .../plans-and-billing/plans-pricing-refunds.mdx | 2 +- .../plans-and-billing/platform-credits.mdx | 17 +++++++++-------- 3 files changed, 13 insertions(+), 12 deletions(-) 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 57b9ab8..d819054 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 @@ -16,7 +16,7 @@ Warp meters credits across three types of infrastructure — inference, compute, * **AI credits** - Charged for inference infrastructure Warp pays for. Consumed by Agent conversations and other AI features that route through Warp-managed model providers. * **Cloud Agent Credits** - Charged for compute infrastructure when cloud agents run on Warp-hosted compute. See [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). -* **Platform Credits** - Charged for platform infrastructure (run lifecycle, integrations, dashboard, APIs, and observability) when Warp isn't paying for inference or compute. Applies to every cloud agent run, plus local runs on Business and Enterprise plans that use customer-supplied inference (BYOK or BYOLLM via Amazon Bedrock or Google Vertex). See [Platform Credits](/support-and-community/plans-and-billing/platform-credits/). +* **Platform Credits** - Charged for Warp's platform infrastructure (run lifecycle, integrations, dashboard, APIs, and observability). Applies to every cloud agent run, plus local agent runs on Business and Enterprise plans that use customer-supplied inference (BYOK or BYOLLM via Amazon Bedrock or Google Vertex). See [Platform Credits](/support-and-community/plans-and-billing/platform-credits/). All three buckets draw from the same plan credit pool and [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/), so you can manage them as a single balance in **Settings** > **Billing and usage**. @@ -141,14 +141,14 @@ The following scenarios do **not** use Cloud Agent Credits: ### Platform Credits -Platform Credits charge for Warp's platform infrastructure — run lifecycle, scheduling, integrations, dashboard, APIs, and observability — when Warp isn't paying for the inference or compute. +Platform Credits charge for Warp's platform infrastructure — run lifecycle, scheduling, integrations, dashboard, APIs, and observability — for every cloud agent run, plus local agent runs on Business and Enterprise plans that use customer-supplied inference. #### Eligible for Platform Credits The following scenarios use Platform Credits: * **Cloud agents on any plan** — Every cloud agent run, regardless of harness or inference source -* **Local agents on Business or Enterprise with customer-supplied inference** — Local Oz runs on a Business or Enterprise plan that use [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** — Local agent runs on a Business or Enterprise plan that use [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 #### Not eligible for Platform Credits diff --git a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx index 1554c00..93c2d00 100644 --- a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx @@ -20,7 +20,7 @@ Visit [warp.dev/pricing](https://warp.dev/pricing) to see the latest plans and w * [Credits](/support-and-community/plans-and-billing/credits/) — learn how credits are used and calculated across AI features. * [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) — purchase additional credits or enable automatic reloads at discounted rates. -* [Platform Credits](/support-and-community/plans-and-billing/platform-credits/) — the third credit bucket, which covers Oz orchestration for every cloud agent run and for local Business and Enterprise runs that use customer-supplied inference. +* [Platform Credits](/support-and-community/plans-and-billing/platform-credits/) — the third credit bucket, which covers Warp's platform infrastructure for every cloud agent run and for local Business and Enterprise runs that use customer-supplied inference. * [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) — connect your own model provider API keys for custom usage and billing. * [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) — information for users on legacy plans with overages enabled. * [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/) — answers to common questions about plans, billing, and usage. Don’t have Warp yet? [Download Warp](https://warp.dev/download) and get started for free today. diff --git a/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx b/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx index 1b6becc..b0b379c 100644 --- a/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx @@ -1,23 +1,24 @@ --- title: Platform Credits description: >- - Platform Credits charge for Warp's platform infrastructure when Warp isn't - paying for inference or compute. Learn when they apply and where they appear. + Platform Credits charge for Warp's platform infrastructure on every cloud + agent run, plus local agent runs on Business and Enterprise plans that use + customer-supplied inference. Learn when they apply and where they appear. --- Warp meters credits across three types of infrastructure: **inference** (the model call), **compute** (the sandbox an agent runs in), and **platform** (everything that runs around the agent — run lifecycle, integrations, dashboard, APIs, and observability). Each type maps to one credit bucket: [AI credits](/support-and-community/plans-and-billing/credits/), [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits), and Platform Credits. -Platform Credits charge for Warp's platform infrastructure when Warp isn't paying for the inference or compute. Customers who bring their own model provider (BYOLLM via Amazon Bedrock or Google Vertex), connect their own LLM API keys, or run cloud agents on their own compute still rely on Warp's platform to coordinate, observe, and integrate their agents — and Platform Credits charge for that. +Platform Credits charge for Warp's platform infrastructure on every cloud agent run, plus local agent runs on Business and Enterprise plans that use customer-supplied inference. Even when you bring your own model provider, connect your own LLM API keys, or run cloud agents on your own compute, Warp's platform still coordinates, observes, and integrates your agents — and Platform Credits charge for that. -Platform Credits apply to every cloud agent run, and to local agent runs on Business and Enterprise plans that use customer-supplied inference — [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. They don't apply to local runs on Free, Build, or Max plans, or to local Business and Enterprise runs where Warp pays for inference through AI credits. +Customer-supplied inference covers [Bring Your Own API Key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/) and BYOLLM via Amazon Bedrock or Google Vertex. Platform Credits don't apply to local runs on Free, Build, or Max plans, or to local Business and Enterprise runs where Warp pays for inference through AI credits. ## The three credit buckets Each credit bucket charges for a different layer of the infrastructure Warp provides: -* **AI credits** - Charged for inference infrastructure Warp pays for. Consumed by Agent conversations, [Generate](/agent-platform/local-agents/generate/), Workflow autofill, and other AI features that route through Warp-managed model providers. See [credits](/support-and-community/plans-and-billing/credits/) for how AI credits are calculated. +* **AI credits** - Charged for inference infrastructure Warp pays for. Consumed by Agent conversations, [Generate](/agent-platform/local-agents/generate/), [AI Autofill](/knowledge-and-collaboration/warp-drive/workflows/#ai-autofill), and other AI features that route through Warp-managed model providers. See [credits](/support-and-community/plans-and-billing/credits/) for how AI credits are calculated. * **Cloud Agent Credits** - Charged for compute infrastructure when cloud agents run on Warp-hosted compute. Consumed by Slack and Linear integrations, `oz agent run-cloud`, the Oz API, and Cloud Mode in the Warp app. See [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits). -* **Platform Credits** - Charged for platform infrastructure (run lifecycle, integrations, dashboard, APIs, and observability) when an agent is actively working but Warp isn't paying for inference or compute. Applies to every cloud agent run, plus local runs on Business and Enterprise plans that use customer-supplied inference. +* **Platform Credits** - Charged for Warp's platform infrastructure (run lifecycle, integrations, dashboard, APIs, and observability). Applies to every cloud agent run, plus local agent runs on Business and Enterprise plans that use customer-supplied inference. The three buckets are independent and a single run can consume from more than one. A Warp-managed cloud agent run, for example, consumes AI credits for the model call, Cloud Agent Credits for the hosted compute, and Platform Credits for the platform infrastructure that runs the agent. @@ -33,8 +34,8 @@ Whether Platform Credits are charged depends on where the agent runs and who's p ### Charged -* **Cloud agents on any plan** - Every cloud agent run charges Platform Credits, regardless of harness (Warp Agent, Claude Code, Codex, Gemini) or inference source (Warp-managed, BYOK, or BYOLLM). Warp's platform infrastructure is always running the agent. -* **Local agents on Business or Enterprise with customer-supplied inference** - Local Oz runs on a Business or Enterprise plan that use [Bring Your Own API Key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/) or BYOLLM (Amazon Bedrock, Google Vertex). Warp isn't paying for the model call, but Warp's platform infrastructure is still running the local agent. +* **Cloud agents on any plan** - Every cloud agent run charges Platform Credits, regardless of harness (Warp Agent, Claude Code, Codex, Gemini), inference source (Warp-managed, BYOK, or BYOLLM), or compute source (Warp-hosted or self-hosted workers). Warp's platform infrastructure is always running the agent. +* **Local agents on Business or Enterprise with customer-supplied inference** - Local agent runs on a Business or Enterprise plan that use [BYOK](/support-and-community/plans-and-billing/bring-your-own-api-key/) or BYOLLM via Amazon Bedrock or Google Vertex. Warp isn't paying for the model call, but Warp's platform infrastructure is still running the local agent. ### Not charged