Where the inputs come from
The estimate is driven by three fields you declare per model, in the Metrics section of the model declaration form (Governe → Models → Add/Edit model → Advanced):
Calculation
For a call within input tokens and out output tokens, and a model whose declared energy per token is ept:
1. GPU energy
Input tokens (encoding) are counted at ~33% of an output token’s energy:2. Server overhead
A fixed server draw of 0.1 kW over an estimated 0.02 s of processing per token:3. Datacenter efficiency (PUE)
The raw energy is scaled by the Power Usage Effectiveness of the datacenter:4. CO₂eq emissions
The energy is converted with the grid emission factor of the model’s region:5. Uncertainty range
Both energy and emissions are reported with a ±20% band (min = value × 0.8, max = value × 1.2).
Condensed formula
Worked example
A short call of 51 input + 18 output tokens on a model declared atept = 0.0000103 kWh/token, average PUE, us-west:
gpu_energy= (51 × 0.0000103 × 0.33) + (18 × 0.0000103) ≈ 0.000359 kWhserver_energy= 0.1 × (69 × 0.02) / 3600 ≈ 0.0000038 kWhtotal_energy= (0.000359 + 0.0000038) × 1.58 ≈ 0.000573 kWhgwp= 0.000573 × 0.352 ≈ 0.0002 kg CO₂eq (~0.2 g CO₂eq)
Result shape
Each call returns:The constants (0.33 input factor, 0.1 kW server draw, 0.02 s/token, PUE multipliers and regional emission factors, ±20% band) are fixed in the gateway. Only
energy_per_token, pue_profile and region are per-model. A model with no energy_per_token reports pricing only and no footprint.Related
- Observability — where the aggregated Carbon (kg CO₂eq) card is surfaced
- Available Models — the governed model catalog
- Model Governance — access, routing and failover controls