Remove PAYG mentions from Enterprise plan billing copy

Drop the pay-as-you-go (PAYG) fallback language from the Enterprise
bullets in cloud-agent team billing and credits — PAYG is an internal
contract detail. The Enterprise sections now describe runs as drawing
from the team-scoped credit pool, with overage behavior governed by
the Enterprise contract terms.

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

Author: hongyi-chen

src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx

@@ -85,9 +85,9 @@ When a user triggers an agent through an integration (like Slack or Linear), the
 
 * **User-triggered runs on Build, Max, or Business** - Warp draws from any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) the user has, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user and are not shared across the team.
 * **Team API key or scheduled cloud agent runs on Build, Max, or Business** - Warp bills the team owner. The waterfall is: the owner's plan-included credits, then the owner's Reload credits. With auto-reload off, the request is blocked when both pools are depleted. With auto-reload on, usage can trigger a reload on the owner's pool subject to the team-wide monthly spend cap.
-* **Enterprise plans** - Runs draw from the team-scoped credit pool. When the pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract.
+* **Enterprise plans** - Runs draw from the team-scoped credit pool, per your Enterprise contract terms.
 
-If all applicable credit sources are exhausted and no auto-reload or PAYG path is available, integrations and cloud agents will not run until credits are added. See [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) for the full self-serve waterfall and [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the third bucket that applies to every cloud agent run.
+If all applicable credit sources are exhausted and no auto-reload is configured, integrations and cloud agents will not run until credits are added. See [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) for the full self-serve waterfall and [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the third bucket that applies to every cloud agent run.
 
 :::note
 If you're on an Enterprise plan, please reach out to [warp.dev/contact-sales](https://www.warp.dev/contact-sales) with any billing questions related to integrations.
@@ -219,13 +219,13 @@ How credits are consumed depends on how the agent run is triggered and authentic
 
 * Runs are tied to the triggering user's identity.
 * On Build, Max, and Business plans, credits are consumed starting with any [cloud agent credits](/support-and-community/plans-and-billing/credits/#compute-credits) allocated to the user, then the user's plan-included credits, then the user's Reload credits. Reload credits are scoped to the individual user.
-* On Enterprise plans, runs draw from the team-scoped credit pool, falling back to pay-as-you-go (PAYG) when the pool is depleted, if enabled in the contract.
+* On Enterprise plans, runs draw from the team-scoped credit pool, per your Enterprise contract terms.
 
 **Team API key and scheduled cloud agent runs** (fully automated or headless workflows):
 
 * Runs are not tied to any individual user.
 * On Build, Max, and Business plans, Warp bills the team owner: the owner's plan-included credits, then the owner's Reload credits. With auto-reload off, the request is blocked when both pools are depleted. With auto-reload on, usage can trigger a reload on the owner's Reload pool subject to the team-wide monthly spend cap.
-* On Enterprise plans, these runs draw from the team-scoped credit pool, falling back to pay-as-you-go (PAYG) when the pool is depleted, if enabled in the contract.
+* On Enterprise plans, these runs draw from the team-scoped credit pool, per your Enterprise contract terms.
 * Ideal for CI/CD pipelines, scheduled tasks, and other automated workflows.
 * For workflows that require code changes (opening pull requests, pushing branches, or writing to a repository), configure [team GitHub authorization](#team-github-authorization) so the agent can authenticate with the Oz by Warp GitHub App. Alternatively, use a [personal API key](/reference/cli/api-keys/) to authenticate as an individual user.
 
@@ -247,7 +247,7 @@ All triggers and instructions used by cloud agents are defined and controlled by
 Because triggers and instructions are configured by your team, the credits consumed when an agent runs are billed according to the model above:
 
 * **Build, Max, Business** - User-triggered runs draw from the triggering user's pools (plan-included credits, then their Reload credits). Team API key and scheduled cloud agent runs are billed to the team owner (the owner's plan-included credits, then the owner's Reload credits, subject to the team-wide spend cap when auto-reload is on).
-* **Enterprise** - All runs draw from the team-scoped credit pool, with PAYG as a fallback if enabled in the contract.
+* **Enterprise** - All runs draw from the team-scoped credit pool, per your Enterprise contract terms.
 
 It's the team's responsibility to manage triggers, confirm they behave as intended, and monitor usage. Reviewing triggers, prompts, and agent behavior periodically helps ensure that credit usage aligns with expectations.
 

src/content/docs/support-and-community/plans-and-billing/credits.mdx

@@ -178,4 +178,4 @@ For details on auto-reload, manual purchases, and the team-wide spend cap, see [
 
 #### Enterprise plans
 
-On Enterprise plans, these runs draw from the team's Enterprise credit pool. When the pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract; otherwise the request is blocked. Overage behavior follows your Enterprise contract terms.
+On Enterprise plans, these runs draw from the team's Enterprise credit pool. Overage behavior follows your Enterprise contract terms.