diff --git a/.agents/references/terminology.md b/.agents/references/terminology.md
index aea79cf4..3fcce82d 100644
--- a/.agents/references/terminology.md
+++ b/.agents/references/terminology.md
@@ -231,9 +231,11 @@ For the summary of the most critical terms (core features, Oz terms, terms to av
 ## Billing and credits
 
 - **Add-on Credits** — capitalized as a product feature name
-- **Cloud Agent Credits** — capitalized as a billing feature name
+- **compute credits** — lowercase common noun; capitalize the first letter only at the start of a sentence or bullet. The compute bucket, consumed when an agent run uses Warp-hosted compute. Use alongside AI credits and platform credits when describing credit types.
+- **cloud agent credits** — lowercase common noun; capitalize the first letter only at the start of a sentence or bullet. Credits consumed by cloud agents, in contrast with local agent credits. Refers to the same compute bucket as compute credits; choose the term that fits the framing.
+- **platform credits** — lowercase common noun; capitalize the first letter only at the start of a sentence or bullet. The platform-infrastructure bucket, consumed for every cloud agent run plus local runs with customer-supplied inference.
 - **credits** — the unit of usage for AI features in Warp (lowercase, not "AI credits")
-- **plan credits** — credits included with a subscription plan
+- **Warp credits** — credits included with a subscription plan. Use in user-facing copy rather than "plan credits."
 
 ## External product names
 
diff --git a/.agents/skills/style_lint/style_lint.py b/.agents/skills/style_lint/style_lint.py
index 488ed834..414f62e7 100644
--- a/.agents/skills/style_lint/style_lint.py
+++ b/.agents/skills/style_lint/style_lint.py
@@ -35,15 +35,18 @@
 # Feature names that are correctly Title Case (exceptions to sentence-case rule)
 PROPER_FEATURE_NAMES = {
     "Admin Panel", "Agent Management Panel", "Agent Mode", "Agent Profiles",
-    "Ambient Agents", "Auto-detection Mode", "Cloud Agent Credits",
+    "Ambient Agents", "Auto-detection Mode",
     "Codebase Context", "Code Review", "Command Palette", "Global Rules",
-    "Oz CLI", "Oz Platform", "Project Rules", "Slash Commands",
-    "Terminal Mode", "Universal Input", "Warp Drive", "Warp Platform",
+    "Oz CLI", "Oz Platform", "Project Rules",
+    "Slash Commands", "Terminal Mode", "Universal Input", "Warp Drive",
+    "Warp Platform",
 }
 
 # Terminology: wrong → right (case-sensitive checks)
 PRODUCT_CASING = {
     "Warp Terminal": ("Warp", "Use 'Warp' unless specifically distinguishing from Oz"),
+    "Cloud Agent Credits": ("cloud agent credits", "Use lowercase 'cloud agent credits' (host-context) or 'compute credits' (bucket-context); capitalize first letter only at start of a sentence/bullet"),
+    "Platform Credits": ("platform credits", "Use lowercase 'platform credits'; capitalize first letter only at start of a sentence/bullet/heading"),
     "agent mode": ("Agent Mode", "Capitalize as a feature name"),
     "agent management panel": ("Agent Management Panel", "Capitalize as a UI surface name"),
     "warp drive": ("Warp Drive", "Capitalize as a feature name"),
diff --git a/AGENTS.md b/AGENTS.md
index d3ad135b..9e74eb38 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -610,8 +610,10 @@ Product feature names retain their standard capitalization. Match the exact casi
 ### Billing and credits
 - **credits** (lowercase, not "AI credits") - the unit of usage for AI features in Warp
 - **Add-on Credits** (capitalized as a product feature name)
-- **Cloud Agent Credits** (capitalized as a billing feature name)
-- **plan credits** - credits included with a subscription plan
+- **compute credits** (lowercase common noun; capitalize the first letter only at the start of a sentence or bullet) - the compute bucket; consumed when an agent run uses Warp-hosted compute. Used alongside AI credits and platform credits when describing credit types.
+- **cloud agent credits** (lowercase common noun; capitalize the first letter only at the start of a sentence or bullet) - credits consumed by cloud agents (in contrast with local agent credits). Refers to the same compute bucket as compute credits; pick the term that fits the framing.
+- **platform credits** (lowercase common noun; capitalize the first letter only at the start of a sentence or bullet) - the platform-infrastructure bucket
+- **Warp credits** - credits included with a subscription plan. Use in user-facing copy rather than "plan credits."
 - Use "credit" or "credits" without the "AI" prefix throughout documentation
 
 ### UI elements
diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx
index 3b8305f4..ecd2f177 100644
--- a/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx
+++ b/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx
@@ -66,7 +66,7 @@ Because PRs are created as _you_, this makes code review, auditing, and team col
 ### Requirements
 
 * **Team membership** - The Linear integration requires you to be part of a [Warp team](/knowledge-and-collaboration/teams/). Teams can be created on any plan, including Free.
-* **Plan and credits** - Your team must be on a plan that supports integrations (Build, Max, or Business) and have at least 20 credits available (any type of Warp credits work). See [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for details.
+* **Plan and credits** - Your team must be on a plan that supports integrations (Build, Max, or Business) and have at least 20 credits available. See [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for details.
 * **Infrastructure** - By default, agents run on Warp-hosted infrastructure. Enterprise teams can [self-host agents](/agent-platform/cloud-agents/self-hosting/) on their own infrastructure.
 * **Identity** - You must be logged into Warp with the same email as your Linear workspace.
 * **GitHub authorization** - You must authorize the Warp GitHub app the first time you trigger an agent.
diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx
index 9d257977..f724666f 100644
--- a/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx
+++ b/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx
@@ -80,7 +80,7 @@ Because PRs are created as you, the workflow slots seamlessly into your team’s
 ### Requirements
 
 * **Team membership** - The Slack integration requires you to be part of a [Warp team](/knowledge-and-collaboration/teams/). Teams can be created on any plan, including Free.
-* **Plan and credits** - Your team must be on a plan that supports integrations (Build, Max, or Business) and have at least 20 credits available (any type of Warp credits work). See [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for details.
+* **Plan and credits** - Your team must be on a plan that supports integrations (Build, Max, or Business) and have at least 20 credits available. See [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for details.
 * **Infrastructure** - By default, agents run on Warp-hosted infrastructure. Enterprise teams can [self-host agents](/agent-platform/cloud-agents/self-hosting/) on their own infrastructure.
 * **Identity** - You must be logged into Warp with the same email used in your Slack workspace.
 * **GitHub authorization** - You must authorize the **Warp GitHub app** the first time you trigger a Slack integration request.
diff --git a/src/content/docs/agent-platform/cloud-agents/overview.mdx b/src/content/docs/agent-platform/cloud-agents/overview.mdx
index dd242d5e..d5fe8c02 100644
--- a/src/content/docs/agent-platform/cloud-agents/overview.mdx
+++ b/src/content/docs/agent-platform/cloud-agents/overview.mdx
@@ -117,7 +117,7 @@ Cloud agents and [integrations](/agent-platform/cloud-agents/integrations/) run
 
 Individual users can run cloud agents without being on a team. Requirements:
 
-* You need at least 20 credits (any type: normal Warp credits, [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits), or Build plan credits)
+* You need at least 20 credits available
 * Cloud agents run on Warp-hosted infrastructure
 * Self-hosted agents require a team subscription
 
@@ -130,9 +130,7 @@ Integrations require you to be part of a [Warp team](/knowledge-and-collaboratio
   * Not supported: Pro, Turbo, Lightspeed, legacy Business
   * Your plan must support Add-on Credits.
 * **Credit requirements**
-  * Your team must have at least 20 credits available (any type of Warp credits work) to run cloud agents and integrations.
-  * Usage is billed based on credit type and team configuration.
-  * Normal credits, [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits), and [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) all work.
+  * Your team must have at least 20 credits available to run cloud agents and integrations.
 
 For more details, see [Access, Billing, and Identity Permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/).
 
diff --git a/src/content/docs/agent-platform/cloud-agents/quickstart.mdx b/src/content/docs/agent-platform/cloud-agents/quickstart.mdx
index a8d1def8..19d1b643 100644
--- a/src/content/docs/agent-platform/cloud-agents/quickstart.mdx
+++ b/src/content/docs/agent-platform/cloud-agents/quickstart.mdx
@@ -157,7 +157,7 @@ Use official Docker Hub images like `node`, `python`, or `rust` for best compati
 Warp prompts you to authorize GitHub when you create an environment or trigger your first agent. If authorization fails or needs updating, see [How GitHub Authorization works](/reference/cli/integration-setup/#how-github-authorization-works). For automated workflows using team API keys, make sure [team GitHub authorization](/agent-platform/cloud-agents/team-access-billing-and-identity/#team-github-authorization) is configured in the Admin Panel. Also verify that repos are correctly configured in your environment with `oz environment get <ENV_ID>`.
 
 **Not enough credits to run cloud agents**\
-Your team needs at least 20 credits available (any type of Warp credits work). Check your credit balance in Settings or see [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for details on credit requirements and which plans support cloud agents.
+Your team needs at least 20 credits available. Check your credit balance in Settings or see [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for details on credit requirements and which plans support cloud agents.
 
 **More resources**
 
diff --git a/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx b/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx
index 298e9f95..e9c1ab37 100644
--- a/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx
+++ b/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx
@@ -18,7 +18,7 @@ Cloud agents can be used in two ways:
 
 **Individual users** (without a team):
 * Can run cloud agents via CLI or API
-* Can use normal Warp credits, [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits), or a Build plan with available credits
+* Can use Warp credits, including [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits)
 * Agents run on Warp-hosted infrastructure
 * Cannot use integrations (Slack, Linear) or self-hosted agents
 
@@ -27,7 +27,7 @@ Cloud agents can be used in two ways:
 * Can use integrations (Slack, Linear) to trigger agents
 * Can self-host agents on their own infrastructure (Enterprise only)
 * Share team-level configuration (environments, secrets, integrations)
-* Team must be on Build, Max, or Business plan with at least 20 credits (any type) for cloud agents and integrations
+* Team must be on Build, Max, or Business plan with at least 20 credits for cloud agents and integrations
 
 ---
 
@@ -38,7 +38,7 @@ Individual users can run cloud agents via the CLI or API without being part of a
 **How it works:**
 
 * Run agents using `oz agent run-cloud` or the Oz API
-* Credits are drawn from your normal Warp credits, Cloud Agent Credits (if available), or Build plan credits
+* Credits are drawn from your Warp credits (including cloud agent credits, when applicable)
 * Agents execute on Warp-hosted infrastructure
 
 **What you can do:**
@@ -79,9 +79,9 @@ Your team must meet the following requirements to run integrations:
 * You must be on a plan that supports **[Reload Credits (Add-on Credits)](/support-and-community/plans-and-billing/add-on-credits/)**.
   * Supported: **Build, Max, Business**
   * Not supported: Pro, Turbo, Lightspeed, legacy Business.
-* Your team needs at least **20 credits** available to run cloud agents and integrations (any type of Warp credits work)
+* Your team needs at least **20 credits** available to run cloud agents and integrations
 
-When a user triggers an agent through an integration (like Slack or Linear), the run draws from credits in a specific order. It starts with any [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits) the user has, then moves to the user's base credits, followed by the team's Reload Credits, and finally the user's own Reload Credits. Enterprises may have different payment options and credit plans that affect this flow. If all applicable credit sources are exhausted, integrations and cloud agents will not work until credits are added.
+When a user triggers an agent through an integration (like Slack or Linear), the run draws from credits in a specific order. It starts with any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) the user has, then moves to the user's base credits, followed by the team's Reload Credits, and finally the user's own Reload Credits. Enterprises may have different payment options and credit plans that affect this flow. If all applicable credit sources are exhausted, integrations and cloud agents will not work until credits are added.
 
 :::note
 If you're on an Enterprise plan, please reach out to [warp.dev/contact-sales](https://warp.dev/contact-sales) with any billing questions related to integrations.
diff --git a/src/content/docs/enterprise/support-and-resources/billing.mdx b/src/content/docs/enterprise/support-and-resources/billing.mdx
index 8110c6ab..5d4bb48e 100644
--- a/src/content/docs/enterprise/support-and-resources/billing.mdx
+++ b/src/content/docs/enterprise/support-and-resources/billing.mdx
@@ -31,11 +31,11 @@ Credit allocations vary by contract. Contact your account manager for details on
 
 ## Cloud agent billing
 
-Oz cloud agents consume credits that include a small hosting fee in addition to AI usage costs.
+Oz cloud agents consume AI credits for inference, compute credits for the sandbox they run in, and platform credits for the orchestration layer. See [Credits](/support-and-community/plans-and-billing/credits/) for the full breakdown of how each credit type is metered.
 
 ### How credits are consumed
 
-On Enterprise plans, both local and cloud agent usage draw from the same team credit pool. There are no separate "cloud agent credits" or "local credits" — all agent usage consumes from your available credit sources.
+On Enterprise plans, local and cloud agent usage both draw from the same team credit pool across all three credit types (AI credits, compute credits, and platform credits). The credit type a run consumes depends on what infrastructure it uses, not on whether it's local or cloud.
 
 For team API key runs (e.g., CI/CD pipelines, scheduled tasks), credits also draw from the team's shared pool since these runs are not tied to any individual user.
 
diff --git a/src/content/docs/support-and-community/plans-and-billing/add-on-credits.mdx b/src/content/docs/support-and-community/plans-and-billing/add-on-credits.mdx
index 8b032f02..193616e4 100644
--- a/src/content/docs/support-and-community/plans-and-billing/add-on-credits.mdx
+++ b/src/content/docs/support-and-community/plans-and-billing/add-on-credits.mdx
@@ -71,7 +71,7 @@ The limit resets automatically at the start of each calendar month, so you can m
 
 When your monthly credit balance renews:
 
-1. Warp first consumes your included monthly plan credits (e.g., Build plan credits).
+1. Warp first consumes your included monthly credits (e.g., Build plan credits).
 2. After those are used, Warp continues to draw from any available Add-on Credits.
 3. If your Add-on Credits run out and Auto reload is enabled, Warp will automatically purchase more up to your monthly limit.
 
diff --git a/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx b/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx
index cd2f84c7..48f6354d 100644
--- a/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx
+++ b/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx
@@ -15,6 +15,10 @@ BYOK provides greater flexibility in model access and ensures Warp **never consu
 BYOK is currently only available on Warp's paid plans, starting with Build. Learn more about plans and pricing [warp.dev/pricing](https://www.warp.dev/pricing).
 :::
 
+:::caution
+BYOK and customer-supplied inference (BYOLLM via Amazon Bedrock or Google Vertex, plus custom endpoints) are available to individual users and organizations with 10 or fewer employees or users on any plan. Organizations with more than 10 employees or users must be on a Warp Business or Enterprise plan to use BYOK or customer-supplied inference. See Warp's [Terms of Service](https://www.warp.dev/terms-of-service) for details.
+:::
+
 ## How does BYOK work?
 
 When you add your own model API keys in Warp, those keys are stored **locally on your device** and are **never synced to the cloud**.
@@ -113,6 +117,8 @@ Warp itself never stores your LLM API keys.
 
 ### BYOK on Enterprise and Business plans
 
+Organizations with more than 10 employees or users must be on a Warp Business or Enterprise plan to use BYOK or customer-supplied inference. See Warp's [Terms of Service](https://www.warp.dev/terms-of-service) for the full eligibility rule.
+
 Currently, BYOK is configured at the **user level**, not the team or admin level:
 
 * Each team member can add and manage their own API keys locally.
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 f039eedf..17f7a569 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
@@ -10,7 +10,13 @@ description: >-
 
 Any interaction with Warp's Agent consumes credits. Credits are primarily based on AI usage — the number of credits a task consumes varies based on the size and complexity of your codebase, the size of the task, the model you're using, the amount of context the agent needs to gather, and more.
 
-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 credits across three types of infrastructure — inference, compute, and platform — each with its own bucket. Credit types and where an agent runs (local or cloud) are independent: each agent run consumes from whichever credit types apply to it.
+
+* **AI credits** cover inference: the LLM call itself. Consumed when Warp pays for the model call through Warp-managed providers.
+* **Compute credits** cover compute: the sandbox an agent runs in. Consumed when an agent run uses Warp-hosted compute. In practice this is cloud agent runs; local agent runs use your own machine and don't consume compute credits. See [Compute credits](/support-and-community/plans-and-billing/credits/#compute-credits).
+* **Platform credits** cover Warp's platform layer: run lifecycle, integrations, dashboard, APIs, and observability. Apply 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 Warp 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 the Warp app under **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.
 
@@ -36,7 +42,7 @@ You can view your total credit usage, along with other billing details, in **Set
 #### Credit **limits and billing**
 
 * **Seat-level allocation**: On team plans, credit limits apply per seat — each team member has their own allowance. Individual users (not on a team) also have their own credit allocation.
-* **Cloud Agent Credits**: Individual users can run cloud agents via CLI/API using their normal Warp credits, [Cloud Agent Credits](/support-and-community/plans-and-billing/credits/#cloud-agent-credits), or a Build plan with available credits. Integrations (Slack, Linear) require team membership.
+* **Cloud agents and integrations**: Individual users can run cloud agents via the CLI and API, drawing from their Warp credits. Slack and Linear integrations require team membership.
 * **Hitting the credit limits**: Once you hit your monthly credit limit, your access will depend on your plan. On the Free plan, AI access stops until your next billing cycle. On paid plans, you can continue using AI with usage-based billing via [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/).
 
 #### **Other features that use credits**
@@ -111,22 +117,46 @@ Because cache results depend on model provider behavior and timing, two similar
 
 These are the most common factors affecting credit usage, though there are others. Understanding them can help you manage your credits more efficiently and get the most from your plan.
 
-### Cloud Agent Credits
+### Compute credits
+
+Compute credits cover Warp-hosted compute consumed by an agent run. In practice, cloud agent runs consume them because they run on Warp's compute; local agent runs typically don't, since they run on your own machine.
+
+Compute credits are sometimes referred to as **cloud agent credits** when the conversation is framed around cloud agents vs local agents — they're the same bucket described from a different angle.
+
+#### Eligible for compute credits
+
+The following scenarios use compute credits:
+
+* **First-party integrations** - Running agents through Slack or Linear integrations
+* **Cloud agent runs** - Using `oz agent run-cloud` via the CLI
+* **Oz API** - Running agents through Warp's Oz API
+* **Cloud Mode** - Running an agent from Cloud Mode in the Warp app
+
+#### Not eligible for compute credits
+
+The following scenarios don't use compute credits because they don't run on Warp-hosted compute:
+
+* **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 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.
 
-Cloud Agent Credits are a type of credit consumed only by cloud agent runs — AI requests that run on Warp-hosted compute.
+#### Eligible for platform credits
 
-#### Eligible for Cloud Agent Credits
+Platform credits are used in the following scenarios:
 
-The following scenarios use Cloud Agent Credits:
+* **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.
 
-* **First-party integrations** — Running agents through Slack or Linear integrations
-* **Cloud agent runs** — Using `oz agent run-cloud` via the CLI
-* **Oz API** — Running agents through Warp's Oz API
-* **Cloud Mode** — Running an agent from Cloud Mode in the Warp app
+#### Not eligible for platform credits
 
-#### Not eligible for Cloud Agent Credits
+The following scenarios do **not** use platform credits:
 
-The following scenarios do **not** use Cloud Agent Credits:
+* **Local agents on Free, Build, or Max plans** don't use platform credits, regardless of inference source.
+* **Local agents on Business or Enterprise using Warp-managed inference** don't use platform credits because Warp is already paying for the model call through AI credits.
+* **Regular terminal usage** doesn't use platform credits. Shell commands and non-AI Warp features don't consume credits.
+* **Third-party agent CLIs run directly** don't use platform credits when you run `claude`, `codex`, or another agent CLI outside of Oz.
 
-* **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
+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 4423f9d6..95307399 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/) — learn how platform credits cover Warp's platform infrastructure for cloud agent runs and local runs with 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
new file mode 100644
index 00000000..c70d85a2
--- /dev/null
+++ b/src/content/docs/support-and-community/plans-and-billing/platform-credits.mdx
@@ -0,0 +1,63 @@
+---
+title: Platform credits
+description: >-
+  Platform credits cover Warp's platform layer on every cloud agent run
+  and on local runs with customer-supplied inference. Learn when they apply.
+---
+
+Platform credits cover Warp's platform infrastructure for coordinating, observing, and integrating agent runs. They apply to every cloud agent run, plus local agent runs on Business and Enterprise plans that use customer-supplied inference such as BYOK, Amazon Bedrock, or Google Vertex.
+
+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/), [Compute credits](/support-and-community/plans-and-billing/credits/#compute-credits), and platform credits. Credit types and where an agent runs (local or cloud) are independent.
+
+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.
+
+:::caution
+BYOK and customer-supplied inference (BYOLLM via Amazon Bedrock or Google Vertex, plus custom endpoints) are available to individual users and organizations with 10 or fewer employees or users on any plan. Organizations with more than 10 employees or users must be on a Warp Business or Enterprise plan to use BYOK or customer-supplied inference. See Warp's [Terms of Service](https://www.warp.dev/terms-of-service) for details.
+:::
+
+## The three credit buckets
+
+Each credit bucket covers a different layer of the infrastructure Warp provides. Credit types and where an agent runs (local or cloud) are independent — each agent run consumes from whichever credit types apply to it.
+
+* **AI credits** cover inference: the LLM call itself. Consumed when Warp pays for the model call through Warp-managed providers. Used by agent conversations, [Generate](/agent-platform/local-agents/generate/), [AI Autofill](/knowledge-and-collaboration/warp-drive/workflows/#ai-autofill), and other AI features. See [credits](/support-and-community/plans-and-billing/credits/) for how AI credits are calculated.
+* **Compute credits** cover compute: the sandbox an agent runs in. Consumed when an agent run uses Warp-hosted compute. In practice this is cloud agent runs (Slack and Linear integrations, `oz agent run-cloud`, the Oz API, and Cloud Mode in the Warp app); local agent runs use your own machine and don't consume compute credits. See [Compute credits](/support-and-community/plans-and-billing/credits/#compute-credits).
+* **Platform credits** cover Warp's platform layer: run lifecycle, integrations, dashboard, APIs, and observability. Apply 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, compute 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.
+
+## When platform credits apply
+
+Whether platform credits apply depends on where the agent runs and who's paying for inference.
+
+### Uses platform credits
+
+* **Cloud agents on any plan** use platform credits for every cloud agent run, regardless of which agent runs the task (Warp Agent, Claude Code, Codex, or Gemini), inference source (Warp-managed, BYOK, or BYOLLM), or compute source (Warp-hosted or self-hosted workers). Warp's platform infrastructure coordinates every cloud agent run.
+* **Local agents on Business or Enterprise with customer-supplied inference** use platform credits when the local agent run uses [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. BYOK and customer-supplied inference are subject to plan-size eligibility — see the callout above.
+
+### Doesn't use platform credits
+
+* **Local agents on Free, Build, or Max plans** don't use platform credits, regardless of whether you use Warp-managed inference or BYOK.
+* **Local agents on Business or Enterprise using Warp-managed inference** don't use platform credits because Warp is already paying for the model call through AI credits.
+* **Regular terminal usage** doesn't use platform credits. Shell commands and non-AI Warp features don't consume credits.
+* **Third-party agent CLIs run directly** don't use platform credits when you run `claude`, `codex`, or another agent CLI without going through Oz.
+
+## Where platform credits appear
+
+Platform credits appear in the same billing views as your other credit usage.
+
+* **Per-user credit totals** - In the Warp app, **Settings** > **Billing and usage** includes platform credits alongside AI credits and compute 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, distinct from the AI credits and compute credits segments.
+* **Add-on Credits and limits** - Platform credits draw from the same pools as your other usage — your monthly Warp credits first, then [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) once those are exhausted.
+
+## 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.
diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx
index fa5abbc7..2ee0d98d 100644
--- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx
+++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx
@@ -305,7 +305,7 @@ Add-on credits replace overages with a simpler, prepaid system. They’re up to
 
 #### Do credits rollover?
 
-For existing users on legacy plans, plan credits on Pro, Turbo, and Lightspeed do not rollover.
+For existing users on legacy plans, Warp credits on Pro, Turbo, and Lightspeed do not rollover.
 
 For the Build plan, credits will not rollover but Add-on credits will rollover and be valid for 12 months from the date of purchase.
 
@@ -347,6 +347,6 @@ If you’re part of a larger team (up to 50 members) that needs advanced adminis
 For teams on the Build or Business plans, credits are managed at two levels:
 
 * **Included monthly credits**: Each seat on a paid plan receives 1,500 individual credits per month. These credits are tied to the user and reset every 30 days based on their subscription or renewal date.
-* **Add-on Credits**: Once individual plan credits are used up, team members draw from a shared Add-on Credit balance that can be topped up and managed by team admins.
+* **Add-on Credits**: Once individual credits are used up, team members draw from a shared Add-on Credit balance that can be topped up and managed by team admins.
 
 This shared model gives teams the flexibility to handle variable AI usage – heavy users can consume more when needed, while the entire team benefits from shared value and volume-based discounts.