Interface PricingTierCondition

Condition for matching a pricing tier based on usage details. Used to implement tiered pricing models where costs vary based on usage thresholds.

How it works:

The regex pattern matches against usage detail keys (e.g., "input_tokens", "input_cached")
Values of all matching keys are summed together
The sum is compared against the threshold value using the specified operator
All conditions in a tier must be met (AND logic) for the tier to match

Common use cases:

Threshold-based pricing: Match when accumulated usage exceeds a certain amount
Usage-type-specific pricing: Different rates for cached vs non-cached tokens, or input vs output
Volume-based pricing: Different rates based on total request or token count

interface PricingTierCondition {
    caseSensitive: boolean;
    operator: PricingTierOperator;
    usageDetailPattern: string;
    value: number;
}

Properties

caseSensitive: boolean

Whether the regex pattern matching is case-sensitive. Default is false (case-insensitive matching).

Comparison operator to apply between the summed value and the threshold.

usageDetailPattern: string

Regex pattern to match against usage detail keys. All matching keys' values are summed for threshold comparison.

Examples:

The pattern is case-insensitive by default. If no keys match, the sum is treated as zero.

value: number

Threshold value for comparison. For token-based pricing, this is typically the token count threshold (e.g., 200000 for a 200K token threshold).