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 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.
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.
This adds deployment-level cost observability to agent-driven delivery, making expensive branches, retries, previews, and machine choices inspectable through both human and programmable interfaces. It complements runtime tracing but narrows interpretation: billable duration and CPU minutes measure rounded resource charges, so they should not be read as direct evidence of execution latency or agent efficiency.