Timestamp when the model was created
OptionalinputDeprecated. See 'prices' instead. Price (USD) per input unit
Regex pattern which matches this model definition to generation.model. Useful in case of fine-tuned models. If you want to exact match, use (?i)^modelname$
Name of the model definition. If multiple with the same name exist, they are applied in the following order: (1) custom over built-in, (2) newest according to startTime where model.startTime<observation.startTime
OptionaloutputDeprecated. See 'prices' instead. Price (USD) per output unit
Deprecated. Use 'pricingTiers' instead for models with usage-based pricing variations.
This field shows prices by usage type from the default pricing tier. Maintained for backward compatibility. If the model uses tiered pricing, this field will be populated from the default tier's prices.
Array of pricing tiers with conditional pricing based on usage thresholds.
Pricing tiers enable accurate cost tracking for models that charge different rates based on usage patterns (e.g., different rates for high-volume usage, large context windows, or cached tokens).
Each model must have exactly one default tier (isDefault=true, priority=0) that serves as a fallback. Additional conditional tiers can be defined with specific matching criteria.
If this array is empty, the model uses legacy flat pricing from the inputPrice/outputPrice/totalPrice fields.
OptionalstartApply only to generations which are newer than this ISO date.
OptionaltokenizerOptional. Configuration for the selected tokenizer. Needs to be JSON. See docs for more details.
OptionaltokenizerOptional. Tokenizer to be applied to observations which match to this model. See docs for more details.
OptionaltotalDeprecated. See 'prices' instead. Price (USD) per total unit. Cannot be set if input or output price is set.
OptionalunitUnit used by this model.
Model definition used for transforming usage into USD cost and/or tokenization.
Models can have either simple flat pricing or tiered pricing:
The pricing tiers approach is recommended for models with usage-based pricing variations. When using tiered pricing, the flat price fields (inputPrice, outputPrice, prices) are populated from the default tier for backward compatibility.