Skip to content
Warp

Support > Plans and billing

Platform usage

Open in ChatGPT ↗
Ask ChatGPT about this page
Open in Claude ↗
Ask Claude about this page
Copied!

Understand agent-hour charges for cloud runs and eligible local runs, including how platform usage differs from inference and compute.

Platform usage covers running and managing agents through Warp. Cloud runs, including Warp Factories runs, and local runs on Business and Enterprise that use customer-supplied inference incur charges for billable agent time. Dollar-billed plans deduct platform charges from their usage balance; Enterprise billing follows your contract.

Customer-supplied inference is any setup where Warp isn’t paying for the model call: Bring Your Own API Key (BYOK), a ChatGPT subscription for local Warp Agent conversations, custom inference endpoints, BYOLLM, or team-managed API keys and endpoints on Business and Enterprise plans.

How platform usage is measured

Section titled “How platform usage is measured”

An agent hour is one hour of billable agent activity. Partial hours are billed proportionally. See Warp pricing for current rates; Enterprise rates follow your contract.

Agent hours are not the same as a run’s elapsed time. For cloud runs, billable time starts when the agent begins work inside its environment, including initial setup before the first response. Queued time, provisioning before the agent starts, and idle time between turns are excluded.

Billable activity depends on the harness:

  • Warp Agent - After initial setup, time spent generating responses. Command and tool execution time, such as a five-minute test suite, isn’t billable as platform usage.
  • Claude Code and Codex - Active runtime, including command execution and time spent waiting on the model provider.

Billable time stops when the agent finishes, fails, or is cancelled.

Inference, compute, and platform usage

Section titled “Inference, compute, and platform usage”

These are cost components, not independent allowances. A run can incur more than one:

  • Inference - Model calls billed through Warp. Your own provider bills customer-supplied inference separately.
  • Compute - The sandbox on Warp-hosted compute. Local or self-hosted compute does not incur this charge.
  • Platform - Billable agent time for the runs listed below.

For example, a cloud run with Warp-provided inference on Warp-hosted compute incurs all three components. See usage and billing for how they draw from your balance.

When platform charges apply

Section titled “When platform charges apply”

Whether a run incurs platform charges depends on where it runs and who pays for inference.

Uses platform services

Section titled “Uses platform services”
  • Cloud runs - Billable agent time incurs platform charges regardless of the harness, inference provider, or compute host. Self-hosted workers avoid Warp-hosted compute charges, not platform charges. Enterprise exceptions follow your contract.
  • Local runs on Business or Enterprise with customer-supplied inference - Platform charges apply when the run uses BYOK, a connected subscription, a custom inference endpoint, or BYOLLM instead of Warp-provided inference.

Doesn’t incur platform charges

Section titled “Doesn’t incur platform charges”
  • Local runs on Free, Build, or Max - No platform charge, whether inference is provided by Warp or by you.
  • Local runs on Business or Enterprise with Warp-provided inference - Inference is charged without a separate platform charge.
  • Regular terminal usage - Shell commands and non-AI terminal features don’t consume agent usage.
  • Third-party agent CLIs run directly - Running claude, codex, or another CLI yourself, outside a Warp-managed run, doesn’t incur Warp platform charges.

Tracking platform usage

Section titled “Tracking platform usage”

In the Warp app, open Settings > Billing and usage to check account usage. Team admins can review the usage breakdown in the Admin Panel under Billing.

Detailed turn, conversation, and factory summaries show platform cost when available. These cost summaries are not agent-hour counters, and a run’s displayed duration is not a substitute for billable agent hours.

Platform charges draw from the billed user or agent’s eligible usage balances. See included and purchased usage for allocation and spending order.

Section titled “Related pages”