Skip to main content
Challenge

Build a Generative Workload Token and Power Cost Attribution Engine

Correlate per-request token usage with real-time accelerator power consumption. Attribute energy and hardware depreciation costs across internal teams and model architectures.

EngineeringHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Correlate per-request token usage with real-time accelerator power consumption. Attribute energy and hardware depreciation costs across internal teams and model architectures.

FinOps and Sustainability Lead

Ingest serving request logs alongside DCGM and Neuron power telemetry records.

Calculate Joules-per-token and watt-hour attribution across concurrent tenants.

Prompt hosted Claude to summarize cost attribution anomalies and carbon footprints.

Compile an auditable monthly billing and sustainability report for department heads.

Multi-tenant dashboard displaying energy consumption charts, Joules/token heatmaps, and cost allocation breakdowns.

Create synthetic time-aligned logs combining open-weight model request traces (token counts) and sampled power draw (Watts) metrics. Starter examples below are synthetic. They are not downloaded records.

NVIDIA DCGM exporter Extracts DCGM GPU power draw metrics (DCGM_FI_DEV_POWER_USAGE) to calculate precise watt-hour consumption per inference window.

pydantic-ai, anthropic-claude, mlflow. Guarantees mathematical schema consistency across energy measurements, token tallies, and currency conversions. Hosted Claude API for natural language variance reporting and sustainability insight drafting.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Calculates energy-per-token metrics across at least two concurrent tenant workloads.

Reconciles aggregate power draw against individual request attributions within 3% tolerance.

Produces verified FinOps cost summaries exportable as JSON.

```json [ { "input": { "tenant_id": "search-team", "window_hours": 1, "tokens_processed": 5000000, "avg_power_watts": 420, "kwh_rate_usd": 0.12, "node_depreciation_hourly_usd": 1.5 }, "expected_output": { "energy_consumed_kwh": 0.42, "energy_cost_usd": 0.05, "total_attributed_cost_usd": 1.55, "joules_per_token": 0.302, "efficiency_rating": "optimal" } }, { "input": { "tenant_id": "idle-team", "window_hours": 1, "tokens_processed": 0, "avg_power_watts": 110, "kwh_rate_usd": 0.12, "node_depreciation_hourly_usd": 1.5 }, "expected_output": { "energy_consumed_kwh": 0.11, "energy_cost_usd": 0.013, "total_attributed_cost_usd": 1.513, "joules_per_token": 0, "efficiency_rating": "idle_waste" } } ] ```

Calculates accounting figures only; does not manipulate power caps or server governor settings. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Calculates accounting figures only; does not manipulate power caps or server governor settings. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Calculates energy-per-token metrics across at least two concurrent tenant workloads. Reconciles aggregate power draw against individual request attributions within 3% tolerance. Produces verified FinOps cost summaries exportable as JSON.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest serving request logs alongside DCGM and Neuron power telemetry records. Calculate Joules-per-token and watt-hour attribution across concurrent tenants. Prompt hosted Claude to summarize cost attribution anomalies and carbon footprints. Compile an auditable monthly billing and sustainability report for department heads.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Calculates energy-per-token metrics across at least two concurrent tenant workloads. Reconciles aggregate power draw against individual request attributions within 3% tolerance. Produces verified FinOps cost summaries exportable as JSON.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Multi-tenant dashboard displaying energy consumption charts, Joules/token heatmaps, and cost allocation breakdowns.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Calculates accounting figures only; does not manipulate power caps or server governor settings.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest serving request logs alongside DCGM and Neuron power telemetry records.

  • Calculate Joules-per-token and watt-hour attribution across concurrent tenants.

  • Prompt hosted Claude to summarize cost attribution anomalies and carbon footprints.

  • Compile an auditable monthly billing and sustainability report for department heads.

Resources and assets

Reference links and supporting material

Dataset notes

Create synthetic time-aligned logs combining open-weight model request traces (token counts) and sampled power draw (Watts) metrics. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Pydantic AI

Typed Python agent framework.

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest serving request logs alongside DCGM and Neuron power telemetry records. Calculate Joules-per-token a...
  • Calculates energy-per-token metrics across at least two concurrent tenant workloads. Reconciles aggregate p...
  • Multi-tenant dashboard displaying energy consumption charts, Joules/token heatmaps, and cost allocation bre...
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 2 configured tools

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • Pydantic AI · Optional
Orchestration
  • Pydantic AI · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Generative Workload Token and Power Cost Attribution Engine