> For the complete documentation index, see [llms.txt](/llms.txt). > Markdown versions of each page are available by appending .md to any URL. # Platform credits Platform credits are calculated from agent hours and cover Warp's platform layer on cloud agent runs and local runs with customer-supplied inference. Platform credits cover Warp’s platform layer: run lifecycle, integrations, dashboard, APIs, and observability. They’re calculated from agent hours, the time an agent spends working on a task. Platform credits apply to every cloud agent run, including [Warp Factories](/factories/) runs, plus local agent runs on Business and Enterprise plans that use customer-supplied inference. Customer-supplied inference is any setup where Warp isn’t paying for the model call: [Bring Your Own API Key (BYOK)](/agents/inference/bring-your-own-api-key/), [custom inference endpoints](/agents/inference/custom-inference-endpoint/), [BYOLLM](/enterprise/enterprise-features/bring-your-own-llm/), or Enterprise [team-managed API keys and endpoints](/enterprise/enterprise-features/team-managed-keys-and-endpoints/). Caution BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp’s [Terms of Service](https://www.warp.dev/legal/terms-of-service). Companies or organizations with more than 10 employees need a Warp Business or Enterprise plan to use these features. ## How platform credits are measured Platform credits are calculated from **agent hours**. An agent hour is an hour an agent spends working on a task. The clock starts when the agent starts up in its environment, including any environment setup the run performs, and stops when the run finishes, fails, is cancelled, or pauses for your input. Time spent queued before the agent starts, time waiting on your input, and idle time between turns don’t count. Usage is billed on exact time rather than rounded up to whole hours, so a run that works for 15 minutes bills a quarter of an agent hour. See [Warp pricing](https://www.warp.dev/pricing) for current rates. ## The three credit buckets Warp meters three types of infrastructure, each with its own credit bucket. Credit types and where an agent runs (local or cloud) are independent: each run consumes from whichever buckets apply to it. - **AI credits** - Cover inference, the model call itself. Consumed when Warp pays for the model call through Warp-managed providers. See [credits](/support-and-community/plans-and-billing/credits/) for how AI credits are calculated. - **Compute credits** - Cover the sandbox an agent runs in. Consumed when a run uses Warp-hosted compute, which in practice means cloud agent runs; local agent runs use your own machine. See [compute credits](/support-and-community/plans-and-billing/credits/#compute-credits). - **Platform credits** - Cover the platform layer that runs around the agent, billed by the agent hour. A single run can consume from more than one bucket. A Warp-managed cloud agent run consumes AI credits for the model call, compute credits for the hosted sandbox, and platform credits for the platform layer. ## When platform credits apply Whether a run uses platform credits depends on where it runs and who pays for inference. ### Uses platform credits - **Cloud agent runs on any plan** - Every cloud agent run uses platform credits, whichever harness (Warp Agent, Claude Code, or Codex), inference source (Warp-managed, BYOK, or BYOLLM), or compute source (Warp-hosted or self-hosted workers) it uses. [Warp Factories](/factories/) runs are cloud agent runs, so a factory’s agents draw platform credits the same way. - **Local agent runs on Business or Enterprise with customer-supplied inference** - When a local run uses [BYOK](/agents/inference/bring-your-own-api-key/), a [custom inference endpoint](/agents/inference/custom-inference-endpoint/), or BYOLLM, Warp isn’t paying for the model call but still runs the platform layer around the agent. ### Doesn’t use platform credits - **Local agent runs on Free, Build, or Max plans** - Don’t use platform credits, whether the run uses Warp-managed or customer-supplied inference. - **Local agent runs on Business or Enterprise with Warp-managed inference** - Don’t use platform credits because Warp already charges AI credits for the model call. - **Regular terminal usage** - Shell commands and non-AI Warp features don’t consume credits. - **Third-party agent CLIs run directly** - Running `claude`, `codex`, or another agent CLI outside Warp doesn’t consume platform credits. ## Where platform credits appear Platform credits appear in the same billing views as the rest of your credit usage. - **Per-user credit totals** - In the Warp app, **Settings** > **Billing and usage** shows platform credits alongside AI credits and compute credits. - **Admin usage breakdown** - For team admins, the Admin Panel billing view shows a per-bucket breakdown for each member and for the team as a whole. Platform credits appear as their own segment in the stacked usage bar. - **Add-on credits and limits** - Platform credits draw from the same pool as the rest of your usage: monthly Warp credits first, then [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) once those run out. ## Related pages - [Credits](/support-and-community/plans-and-billing/credits/) - How AI credits are measured and calculated. - [Add-on credits](/support-and-community/plans-and-billing/add-on-credits/) - Purchase additional credits or enable auto-reload. - [Bring Your Own API Key](/agents/inference/bring-your-own-api-key/) - Connect your own model provider keys. - [Custom inference endpoint](/agents/inference/custom-inference-endpoint/) - Route Warp through any OpenAI-compatible endpoint. - [Plans, pricing, and refunds](/support-and-community/plans-and-billing/plans-pricing-refunds/) - Compare plans and refund policies.