By token
Text, reasoning, multimodal, and some video routes where the upstream bills by model usage.
Pricing overview
Usage-based billing for model access and video routes
Each route uses the unit that matches upstream billing: token, second, task, or reserved capacity.
TokenText, multimodal, some video routes
SecondDuration-based video routes
TaskFixed submitted job units
ReservedManaged or enterprise capacity
By second
Video routes where duration and resolution determine the billing unit.
By task
Image, video, or special workflows where one submitted job has a fixed unit.
Reserved route
Enterprise capacity, managed access, special providers, and volume arrangements.
Video generation
Video pricing depends on route, resolution, and billing unit
Use this overview to understand how video routes are charged before checking live model prices in the console.
Route typeResolutionBilling unitWhere to confirm
Premium video720p / 1080pSecond or taskContact for pricing
High-volume videoModel dependentToken or secondContact for pricing
Human / asset workflowsReviewed per routeCustomEnterprise review
Async billing notes
Task billing follows the final task state
- A submitted task remains pending until the provider returns a final state.
- Successful tasks record model, route, resolution, duration or usage, and amount.
- Failed tasks and upstream refunds are matched against the task ID.
- Detailed invoices and task records are handled in the console.