docs(pricing-may-2026): weave platform credits into BYOK + CIE billing copy

Soften the "never consumes Warp credits" claims on the BYOK and Custom inference
endpoint (CIE) pages so they accurately reflect the May 2026 launch: on Business
and Enterprise, local agent runs that use customer-supplied inference still
consume platform credits for Warp's platform infrastructure (run lifecycle,
integrations, observability).

Changes on each page:
- Trim the frontmatter description to mention the Business/Enterprise platform
  credits caveat for local runs (keeping length around the 160-char target).
- Add a :::note callout right after the "never consumes your credits" paragraph
  pointing readers at the platform credits doc.
- Add a footnote line under the BYOK / CIE / BYOLLM comparison table noting
  that platform credits may apply for local agent runs on Business and
  Enterprise across all three customer-supplied inference paths.

Co-Authored-By: Oz <oz-agent@warp.dev>

Author: hongyi-chen

src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx

@@ -1,15 +1,19 @@
 ---
 title: Bring your own API key
 description: >-
-  Use your own OpenAI, Anthropic, or Google API keys with Warp's agents.
-  BYOK is available on the Free plan and all eligible paid plans, and never
-  consumes Warp credits.
+  Use your own OpenAI, Anthropic, or Google API keys. Never consumes AI
+  credits — on Business and Enterprise, platform credits may apply for
+  local agent runs.
 ---
 
 Warp supports **Bring your own API key (BYOK)** for users who want to connect Warp's agents to their own Anthropic, OpenAI, or Google API accounts.
 
 BYOK gives you full control over model selection, billing, and data routing. See [Model Choice](/agent-platform/capabilities/model-choice/) for the full list of supported models. When you route a request through your own key, Warp **never consumes your** [credits](/support-and-community/plans-and-billing/credits/) for that request.
 
+:::note
+On the Business and Enterprise plans, local agent runs that use BYOK still consume platform credits for Warp's platform infrastructure (run lifecycle, integrations, observability). See [platform credits](/support-and-community/plans-and-billing/platform-credits/) for what's covered.
+:::
+
 :::note
 BYOK is available on the Free plan and on all eligible paid plans. See [warp.dev/pricing](https://www.warp.dev/pricing) for the current list of eligible plans.
 :::
@@ -30,6 +34,8 @@ Warp offers three ways to bring your own AI infrastructure. Use this table to pi
 
 See [warp.dev/pricing](https://www.warp.dev/pricing) for current plan availability.
 
+Platform credits may apply for local agent runs on Business and Enterprise when using BYOK, CIE, or BYOLLM. See [platform credits](/support-and-community/plans-and-billing/platform-credits/).
+
 ## How BYOK works
 
 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**.

src/content/docs/support-and-community/plans-and-billing/custom-inference-endpoint.mdx

@@ -1,9 +1,9 @@
 ---
 title: Custom inference endpoint
 description: >-
-  Connect Warp to any OpenAI-compatible custom inference endpoint, such as
-  OpenRouter, LiteLLM, z.ai, or an internal gateway. Available on the Free
-  plan and all eligible paid plans.
+  Connect Warp to OpenAI-compatible endpoints (OpenRouter, LiteLLM, z.ai,
+  internal gateways). On Business and Enterprise, platform credits may
+  apply for local runs.
 ---
 
 A **Custom inference endpoint (CIE)** lets you connect Warp's agents to any OpenAI-compatible inference endpoint, so you can route AI requests through your preferred model router, hosted gateway, or internal infrastructure.
@@ -69,6 +69,10 @@ When you select a CIE-routed model from the model picker:
 * Inference is billed directly by your endpoint provider, according to their pricing.
 * The credit transparency footer will show "0 credits used" for CIE-routed requests.
 
+:::note
+On Business and Enterprise plans, local agent runs that use a custom inference endpoint still consume platform credits for Warp's platform infrastructure. See [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the full breakdown.
+:::
+
 ### Auto routing still uses Warp credits
 
 Warp's **Auto** models dynamically route across providers using Warp's infrastructure. Because Auto routing depends on Warp, **Auto always consumes Warp's credits**, even if you've configured a custom inference endpoint.
@@ -109,6 +113,8 @@ Warp offers three ways to bring your own AI infrastructure. Use this table to pi
 | **Custom inference endpoint** (CIE) | Connect Warp to an OpenAI-compatible endpoint such as OpenRouter, LiteLLM, z.ai, or an internal gateway. | Free and all eligible paid plans |
 | **[Bring your own LLM](/enterprise/enterprise-features/bring-your-own-llm/)** (BYOLLM) | Enterprise-managed inference through your cloud provider (AWS Bedrock, Azure Foundry, Google Vertex) or approved internal infrastructure, with Warp handling routing, orchestration, governance, and observability. | Enterprise only |
 
+Platform credits may apply for local agent runs on Business and Enterprise when using BYOK, CIE, or BYOLLM. See [platform credits](/support-and-community/plans-and-billing/platform-credits/).
+
 ## Related resources
 
 * [Bring your own API key](/support-and-community/plans-and-billing/bring-your-own-api-key/) — Use your own OpenAI, Anthropic, or Google API keys.