Member Junction
    Preparing search index...
    • Maps a run's recorded usage onto the quantities a driver of driverUnitKind prices, refusing when the two disagree about what is being measured.

      The refusal matters: a transcription run measured in seconds, handed to a per-1M-tokens driver, would be priced by dividing seconds by a million — a cost of approximately zero that looks like a real answer. Refusing surfaces the misconfigured cost row instead of hiding it behind a number.

      Parameters

      • recorded: RecordedRunUsage
      • driverUnitKind: "Tokens" | "Seconds" | "Characters" | "Images"

      Returns NormalizeUsageResult