# Deployments now show billable duration and CPU minutes

Source: [Vercel](https://vercel.com/changelog/deployments-now-show-billable-duration-and-cpu-minutes)  
Feed7 permalink: https://feed7.dev/p/deployments-now-show-billable-duration-and-cpu-minutes-0pyayzb  
Published: 2026-09-21T15:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

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

## 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 across 843 accumulated Signals:

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.

- [Measure time between steps in Vercel Workflows](https://feed7.dev/p/measure-time-between-steps-in-vercel-workflows-0dtmqf6) — Workflow gap measurements can explain where elapsed time accumulates, while the new deployment fields show how rounded duration and machine size translate that activity into billing units.
- [Agent Runs now available in the Vercel MCP and CLI](https://feed7.dev/p/agent-runs-vercel-mcp-cli-06cfo04) — Agent Runs traces expose reasoning, tool calls, and token use; deployment billing metrics add the infrastructure-cost side needed to investigate expensive agent-generated delivery attempts.
- [Vercel CLI expands support for DNS, domains, and project commands](https://feed7.dev/p/vercel-cli-expands-support-for-dns-domains-and-project-commands-1iy7kh7) — The broader structured CLI surface enables supervised infrastructure automation, and per-deployment billing data gives those automated workflows a concrete cost signal to inspect.

## Context Map

- Layer: infra
- Domains: coding
- Topics: 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.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.