Skip to main content

Endpoint

This endpoint does not require authentication.

Path Parameters

Code Examples

Response

Response Fields

Cost Estimate

When cost is non-null, it contains these fields:
cost is planning guidance, not a quote for a particular input or the final charge. For usage-based pricing, min and max are rates per unit, not the minimum and maximum total price of a request. Estimates may change when model pricing changes. Use metrics.cost on the resulting prediction or workflow execution for the settled value.

Reading rows

rows gives the price of each option combination, so you can estimate a request before you send it.
  • A base row’s label lists the option values in depends_on order, joined by ·, such as 720p · 5 s. Its value is the price per unit for that combination.
  • A label that starts with + is an add-on, such as + audio. Its value is added to the base row when the request turns that option on. When an add-on has its own unit, the label names it, such as + each input image.
  • The label that ends in (default) is the combination used when you leave the inputs unset.
To estimate a request, take the base row that matches its options (or the default row), add each + row the request turns on, and multiply by the quantity of unit: seconds of output, images, or one generation or execution. With the usage-based example above, 10 seconds at 1080p with audio is about (0.12 + 0.02) × 10 = $1.40. Some models still show older labels, such as default, while their rows are updated. Usage-based pricing with unit, amount, min, and max all null means no reliable public rate is listed. It does not mean the model is free. A free model instead has type: "fixed", amount: 0, and estimate: "Free". Render estimate for a readable summary and use the structured fields when you need rates or tier details. Treat a missing numeric estimate as unknown; do not substitute zero.

Error Responses

Last modified on October 14, 2026