Skip to content
llms.party

Video generation

Video is an asynchronous task API on the same bearer token, under /v1/videos. The shape follows OpenAI's video routes:

  1. POST /v1/videos creates a job and returns its id immediately.
  2. GET /v1/videos/{id} is polled until the job finishes.
  3. Download the finished clip from GET /v1/videos/{id}/content.

The gateway serves two video families:

GroupProviderResolutionsDuration
minimax-h3MiniMax768P, 2K4–15 s
minimax-h3-maxMiniMax480P, 768P5–15 s
seedanceBytePlus480p, 720p, 1080p4–30 s

A deployment serves a group only when its provider credential is configured. GET /v1/models lists the video groups your key can call.

See BytePlus Seedance for its image-to-video and billing details.

Try it

Generate a video

POST /v1/videos

MiniMax H3 · billed per second

Create a job

curl -sS "https://llms.party/v1/videos" \
  -H "Authorization: Bearer $LLMS_PARTY_KEY" \
  -H "content-type: application/json" \
  -d '{
    "model": "minimax-h3",
    "prompt": "A glass city at sunset, slow aerial push-in.",
    "seconds": 4,
    "resolution": "768P",
    "ratio": "16:9"
  }'
FieldValues
modelA video group or one of its aliases.
promptText description of the shot.
secondsH3: 4–15. H3-Max: 5–15. Seedance: 4–30.
resolutionGroup-specific; see the table above (Seedance is lowercase).
ratio16:9, 9:16, 1:1, 4:3, 3:4, 21:9.
input_referenceOptional image URL for image-to-video.

Poll

curl -sS "https://llms.party/v1/videos/$VIDEO_ID" \
  -H "Authorization: Bearer $LLMS_PARTY_KEY"

Statuses are normalized across providers: the gateway maps running to in_progress and succeeded to completed, but older payloads may still say succeeded. Terminal states are completed, failed and cancelled.

StatusMeaning
queuedAccepted, not started upstream yet.
in_progressRendering; progress may be populated.
completedReady to download.
failederror.message explains why.
cancelledCancelled upstream.

Polling every 2–5 s is plenty; renders take tens of seconds to a few minutes.

Download

Download the finished clip through the OpenAI-compatible content route:

curl -sS "https://llms.party/v1/videos/$VIDEO_ID/content" \
  -H "Authorization: Bearer $LLMS_PARTY_KEY" \
  -o clip.mp4

The response is video/mp4. The gateway streams the clip from the provider as it downloads (Range requests are supported), so large 720p/1080p files are not buffered. Provider signed URLs are resolved internally and are not returned in the task object; on BytePlus they expire after 24 hours or 100 downloads, so always download through /content. Task records are kept for 7 days; after that a finished clip can no longer be downloaded.

What it costs

MiniMax is billed per second of output; Seedance is billed per million tokens.

MiniMax H3

Group480P768P2K
minimax-h3n/a$0.08/s$0.13/s
minimax-h3-max$0.05/s$0.08/sn/a

BytePlus Seedance 2.5

ResolutionUSD per 1M tokens5 s, 16:930 s, 16:9
480p$10.70$0.514$3.08
720p$10.70$1.156$6.94
1080p$11.70$2.843$17.06

Seedance cost is (input video seconds + output seconds) × width × height × fps / 1024 tokens, priced per million tokens; see BytePlus Seedance for the full formula and caveats. The largest Seedance job through the gateway, 30 s at 1080p, costs about $17.06.

Figures are vendor list prices; the gateway meters them as spend against the key's budget. Sources: MiniMax pricing and BytePlus ModelArk pricing.