diff --git a/src/content/docs/agents/inference/bring-your-own-api-key.mdx b/src/content/docs/agents/inference/bring-your-own-api-key.mdx
index f0e4622e..3c05ac77 100644
--- a/src/content/docs/agents/inference/bring-your-own-api-key.mdx
+++ b/src/content/docs/agents/inference/bring-your-own-api-key.mdx
@@ -97,7 +97,7 @@ To use your own key, select a specific provider model (for example, Claude Opus
 
 When you select a model with the key icon in your model picker, Warp routes the request through your API key. In that case:
 
-* Inference is billed directly through your provider account rather than drawing from your Warp AI credits.
+* Inference is billed directly through your provider account rather than drawing from your AI credits.
 * Agent Mode prioritizes BYOK over any available Warp credits.
 
 :::note
diff --git a/src/content/docs/agents/inference/custom-inference-endpoint.mdx b/src/content/docs/agents/inference/custom-inference-endpoint.mdx
index f3d57e09..fea4e193 100644
--- a/src/content/docs/agents/inference/custom-inference-endpoint.mdx
+++ b/src/content/docs/agents/inference/custom-inference-endpoint.mdx
@@ -81,9 +81,9 @@ For example, with a default Ollama install listening on port `11434`, run `ngrok
 
 ## Billing behavior
 
-### Warp AI credits
+### AI credits
 
-When you select an endpoint-routed model from the model picker, inference is billed directly by your endpoint provider, according to their pricing, rather than drawing from your Warp AI credits.
+When you select an endpoint-routed model from the model picker, inference is billed directly by your endpoint provider, according to their pricing, rather than drawing from your AI credits.
 
 :::note
 On Business and Enterprise plans, local agent runs that route through 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.