Skip to main content
POST
Estimate the price of a video upscale request
Estimate the cost of a video upscale job before submitting it.

Authorizations

Authorization
string
header
required

Sanctum personal access token, sent as Authorization: Bearer <token>. The token is opaque — it carries no claims and no embedded expiry, so do not attempt to decode it. Issue and revoke tokens from your account dashboard.

Headers

Accept
enum<string>
default:application/json
required
Available options:
application/json

Body

multipart/form-data

Video upscaling parameters

Every example in this schema is a working set for the model example shown — they are not defaults and not portable. Sizes, step counts, frame counts and frame rates are all per-model: read info.limits and info.defaults for the model you actually intend to use from GET /api/v2/models. Substituting a different model while keeping these values is the most common source of a 422.

video
file
required

Video file to upscale. Supported formats: MP4, MPEG, QuickTime, AVI, WMV, OGG. Maximum file size: 10 MB.

model
string
required

The upscaling model to use

Example:

"RealESRGAN_Vid_x4"

scale
integer | null

Upscale factor. Accepted ONLY by models that publish info.limits.min_scale/max_scale in GET /api/v2/models, and REQUIRED by those models — read them for your model before sending. A fixed-scale model (both limits absent or null, e.g. RealESRGAN_Vid_x4) rejects this field with a 422; a configurable one rejects its absence. Deliberately carries no example, because no single value is valid across models.

Required range: 1 <= x <= 16

Response

Calculated price for video upscaling inference.

data
object