Array of conditions that must ALL be met for this tier to match (AND logic).
The default tier must have an empty array (conditions=[]). Conditional tiers should define one or more conditions that specify when this tier's pricing applies.
Conditions can compare summed matching usage details to a numeric threshold, or exactly match a top-level model parameter or metadata value.
Whether this is the default tier. Exactly one tier per model must be marked as default.
Requirements for default tier:
The default tier acts as a fallback when no conditional tiers match.
Name of the pricing tier for display and identification purposes.
Must be unique within the model. Common patterns: "Standard", "High Volume Tier", "Extended Context"
Prices (USD) by usage type for this tier. At least one price must be defined.
Common usage types: "input", "output", "total", "request", "image" Prices are in USD per unit (e.g., per token).
Example: {"input": 0.000003, "output": 0.000015} represents $3 per million input tokens and $15 per million output tokens.
Priority for tier matching evaluation. Lower numbers = higher priority (evaluated first).
Must be unique within the model. The default tier must have priority=0. Conditional tiers should use priority 1, 2, 3, etc. based on their specificity.
Input schema for creating a pricing tier. The tier ID will be automatically generated server-side.
When creating a model with pricing tiers:
See PricingTier for detailed information about how tiers work and why they're useful.