> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Platform usage

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, including orchestration, integrations, and run tracking. Cloud runs, including [Warp Factories](https://docs.warp.dev/factories/) runs, incur charges for billable agent time. Some local runs also incur these charges, depending on the [product and plan billed for the work](#when-platform-charges-apply).

Customer-supplied inference is any setup where Warp isn’t paying for the model call: [Bring Your Own API Key (BYOK)](https://docs.warp.dev/agents/inference/bring-your-own-api-key/), a [ChatGPT subscription](https://docs.warp.dev/agents/inference/chatgpt-subscription/) for local Warp Agent conversations, [custom inference endpoints](https://docs.warp.dev/agents/inference/custom-inference-endpoint/), [BYOLLM](https://docs.warp.dev/enterprise/enterprise-features/bring-your-own-llm/), or [team-managed API keys and endpoints](https://docs.warp.dev/enterprise/enterprise-features/team-managed-keys-and-endpoints/).

Caution

Personal BYOK and endpoints have [organization-size and plan requirements](https://docs.warp.dev/agents/inference/bring-your-own-api-key/). Factory runs use [team-managed inference](https://docs.warp.dev/enterprise/enterprise-features/team-managed-keys-and-endpoints/#plan-eligibility) or harness credentials, not keys stored on a member’s device.

## How platform usage is measured

An *agent hour* (AH) is one hour of billable agent activity. On Free, Build, Max, and Business accounts for Warp Terminal and local agents billed in dollars, platform usage costs $3 per AH, or $0.05 per billable minute. Partial hours are billed proportionally: 30 minutes of billable activity costs $1.50. Enterprise rates and credit-billed accounts follow your contract.

Agent hours are not the same as a run’s elapsed time. Queued time, provisioning before the agent starts, idle time between turns, and time blocked waiting for human input are excluded. Waiting for a model response during active execution is different from waiting for a person.

Billable activity depends on the [harness](https://docs.warp.dev/factories/harnesses/):

-   **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.
-   **Third-party harnesses** - 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

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](https://docs.warp.dev/support-and-community/plans-and-billing/credits/) for how they draw from your balance.

## When platform charges apply

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

### Warp Terminal and local agents

| Plan for Warp Terminal and local agents | Local platform charges |
| --- | --- |
| Free, Build, or Max | None, whether inference is supplied by Warp or by you |
| Business or Enterprise | Billable agent time when using customer-supplied inference, including connected ChatGPT subscriptions; no separate platform charge for Warp-provided inference |

### Warp Factories

Factory runs incur platform charges for billable agent time on Start, Scale, and Enterprise plans for Warp Factories, regardless of harness, inference provider, or compute host. A local run billed under a team’s Scale plan for Warp Factories also incurs platform charges when it uses customer-supplied inference. Enterprise rates and exceptions follow your contract.

Self-hosted workers avoid Warp-hosted compute charges, not platform charges.

### Doesn’t incur platform charges

-   **Local runs 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

In the Warp app, open **Settings** > **Billing and usage** to check account usage. Team admins can review the usage breakdown in the [Admin Panel](https://docs.warp.dev/knowledge-and-collaboration/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.

Factory platform charges draw from [shared team or workspace funding](https://docs.warp.dev/support-and-community/plans-and-billing/plans-pricing-refunds/#funding-factory-runs), not a member’s personal included allowance. For other runs, see [included and purchased usage](https://docs.warp.dev/support-and-community/plans-and-billing/credits/#included-and-purchased-usage) for allocation and spending order.

## Related pages

-   [Usage and billing](https://docs.warp.dev/support-and-community/plans-and-billing/credits/) - How inference, compute, and platform costs are calculated.
-   [Purchasing additional usage](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/) - Buy usage or enable auto-reload.
-   [Bring Your Own API Key](https://docs.warp.dev/agents/inference/bring-your-own-api-key/) - Connect your own model provider keys.
-   [ChatGPT subscription](https://docs.warp.dev/agents/inference/chatgpt-subscription/) - Use eligible OpenAI models through your ChatGPT plan.
-   [Custom inference endpoint](https://docs.warp.dev/agents/inference/custom-inference-endpoint/) - Route Warp through any OpenAI-compatible endpoint.
-   [Plans, pricing, and refunds](https://docs.warp.dev/support-and-community/plans-and-billing/plans-pricing-refunds/) - Compare plans and refund policies.
