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 <oz-agent@warp.dev>

Author: hongyi-chen

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/).

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.

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.