Skip to content
EnglishENPortuguêsPT
Try chatGet API key

Quote a video generation

POST
/video/quote
curl --request POST \
  --url https://api.bayle.ai/video/quote \
  --header 'Accept-Language: pt-BR' \
  --header 'Content-Type: application/json' \
  --data '{ "model": "seedance-2-0-mini-text-to-video-basic", "duration": "5s", "aspect_ratio": "16:9", "resolution": "720p", "audio": true }'

Prices a video generation before you queue it. No credential is required to call this endpoint.

The fields that affect a quote are model, duration, aspect_ratio, resolution, and audio, all model-dependent. reference_video_total_duration is recognized here and has no effect on POST /video/queue. Fields Bayle does not name below are forwarded as sent.

Parameters

Section titled “Parameters”

Header Parameters

Section titled “Header Parameters”
Accept-Language
string
Example
pt-BR

Chooses the language of any error message in this request’s response. A tag beginning with the two letters pt, in any case, selects Brazilian Portuguese; anything else, including an absent header, selects English. The tag may appear anywhere in a multi-tag header, for example fr-FR;q=0.9,pt;q=0.5,en;q=0.3. Quality values are accepted but ignored, since this is a presence check rather than weighted negotiation.

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json

The quote request. Any field not listed here is forwarded as sent.

object
model

The video model to price, as returned by GET /models.

string
duration

Requested clip length, as a string of whole seconds followed by s, for example "5s". A bare number such as 5 is rejected. The accepted values differ by model: each video model lists them under model_spec.constraints.durations in GET /models?type=video, and a value that model does not list is rejected.

string
aspect_ratio

For example "16:9". Each video model lists the values it takes under model_spec.constraints.aspect_ratios.

string
resolution

For example "720p". Each video model lists the values it takes under model_spec.constraints.resolutions.

string
audio

Whether the generation includes audio.

boolean
reference_video_total_duration

Recognized by this endpoint only. It has no effect on POST /video/queue.

integer
key
additional properties
any
Examples

Text-to-video, with audio

{
  "model": "seedance-2-0-mini-text-to-video-basic",
  "duration": "5s",
  "aspect_ratio": "16:9",
  "resolution": "720p",
  "audio": true
}

Responses

Section titled “Responses”

200

Section titled “200”

The quoted price. The decimal price is relayed exactly as issued, without being decoded and re-encoded, so it is safe to compare or store verbatim.

Media typeapplication/json
object
quote
required

The decimal price, relayed exactly as issued without being decoded and re-encoded.

number
key
additional properties
any
Examples

Text-to-video, 5s, 720p, with audio

{
  "quote": 0.47
}

Headers

Section titled “Headers”
Content-Language
string
Allowed values: en pt-BR

Confirms which of the two supported locales, en or pt-BR, this response was rendered in, so a caller can detect it without reading the message text. Present on every response, success and error alike. On a chat completions stream it is committed together with the initial 200, so it appears whichever way the stream ends.

default

Section titled “default”

The request failed. The body uses the shared error envelope, rendered in the locale negotiated through Accept-Language. type and code identify the specific failure when Bayle recognizes it, and fall back to type: api_error with a null code when it does not. Where a failure carries a meaningful status code, Bayle preserves it; a transport failure, such as a timeout or a refused connection, is reported as 502. The exception is an operation that documents its own time limit, which reports running past it as 504 with the request_timeout code.

Media typeapplication/json

Bayle’s OpenAI-shaped error envelope, shared by every error response this API returns.

object
error
required
object
message
required

A human-readable description of the failure, in the negotiated locale. See the Accept-Language request parameter for how that locale is chosen, and the Content-Language response header for which one was served.

string
type
required

OpenAI’s error type vocabulary, for example api_error, authentication_error, invalid_request_error, or rate_limit_error, matching the class of failure so an OpenAI SDK’s exception mapping keeps working.

string
param
required

The request field the failure names, when it names one. Null when the failure is not field-specific, as with authentication or rate limiting.

string
nullable
code
required

Bayle’s semantic error code, reusing OpenAI’s vocabulary where an equivalent exists, for example invalid_api_key or rate_limit_exceeded. Null when Bayle could not identify the specific failure; the envelope is still valid and carries a generic message. The full list lives in Bayle’s error reference rather than being enumerated here.

string
nullable
Examples

400: a missing or invalid parameter, for example an unknown `type` on `GET /models`, no `input` on `POST /embeddings`, `n` above 1 or an unlisted `size` on `POST /images/generations`, a numeric or unlisted `duration` on the video endpoints, or no `queue_id`

{
  "error": {
    "message": "Bayle could not process this request because one or more parameters are invalid.",
    "type": "invalid_request_error",
    "param": null,
    "code": "invalid_request"
  }
}

Headers

Section titled “Headers”
Content-Language
string
Allowed values: en pt-BR

Confirms which of the two supported locales, en or pt-BR, this response was rendered in, so a caller can detect it without reading the message text. Present on every response, success and error alike. On a chat completions stream it is committed together with the initial 200, so it appears whichever way the stream ends.