Open Brain
VercelEngineering PostOfficial Source

Deployments now show billable duration and CPU minutes

Vercel now exposes per-deployment billable duration and CPU minutes in its dashboard, CLI, and API, making agent-triggered build costs easier to inspect.

Vercel · Sep 21, 2026
Open Source Open MarkdownOpen JSON
Source Summary

Vercel deployments now expose **billable duration** and **CPU minutes** in the dashboard, REST API, and vc inspect with CLI **59.23.1 or later**. Duration combines build and post-build time, rounded up to a whole minute; CPU minutes multiply that result by vCPUs.

Practical Implication

Use the per-deployment breakdown to identify expensive builds from agent-driven branches, retries, or preview deployments and compare machine-size tradeoffs.

Agent-Ready Context
Vercel deployments now expose **billable duration** and **CPU minutes** in the dashboard, REST API, and vc inspect with CLI **59.23.1 or later**. Duration combines build and post-build time, rounded up to a whole minute; CPU minutes multiply that result by vCPUs.

Use the per-deployment breakdown to identify expensive builds from agent-driven branches, retries, or preview deployments and compare machine-size tradeoffs.

These are billing measures rather than raw runtime measures: whole-minute rounding and the selected machine's vCPU count both affect the totals.
Connected Context · Feed7 Judgment

This closes a cost-observability gap for agent-created builds by making deployment-level billing inputs inspectable through both human and machine interfaces. It enables comparisons across branches, retries, previews, and machine sizes, but the figures must not be treated as execution latency because whole-minute rounding and vCPU multiplication deliberately encode billing policy.

Context Map
infracoding#observability#dev-ux
Uncertainty
These are billing measures rather than raw runtime measures: whole-minute rounding and the selected machine's vCPU count both affect the totals.