PixVerse Video Generation

PixVerse is a high-quality AI video generation platform. AutoRouter integrates with PixVerse OpenAPI v2 and exposes it via the OpenAI-compatible /v1/videos endpoint. All 8 PixVerse model versions are supported for text-to-video and image-to-video.

PixVerse uses an async task-based API: submit a request, receive a task_id, poll for status, then download the video via the proxy endpoint.

1. Supported Models

In the model field, always use the PixVerse/<version> form, e.g. PixVerse/v5.6.

The PixVerse/ prefix is case-sensitive. Use exactly PixVerse/v5.6. The version suffix (v5.6, c1) is case-insensitive but lowercase is recommended.

2. Common Endpoints

All PixVerse models use the OpenAI-compatible /v1/videos endpoint.

2.1 Submit Task

POST /v1/videos

Request Headers

Request Body Fields

Response

{
  "id": "task_xxxxxxxxxxxxx",
  "task_id": "task_xxxxxxxxxxxxx",
  "object": "video",
  "model": "PixVerse/v5.6",
  "status": "queued",
  "progress": 0,
  "created_at": 1730000000
}

The id / task_id is a public ID generated by AutoRouter (prefixed with task_). Use this value for subsequent queries — it's not the same as PixVerse's upstream video_id.

2.2 Query Task Status

GET /v1/videos/{task_id}

Response (in progress)

{
  "id": "task_xxxxxxxxxxxxx",
  "status": "in_progress",
  "progress": 30,
  "created_at": 1730000000
}

Response (completed)

{
  "id": "task_xxxxxxxxxxxxx",
  "status": "completed",
  "progress": 100,
  "created_at": 1730000000,
  "completed_at": 1730000060,
  "size": "1280x720",
  "metadata": {
    "url": "https://media.pixverse.ai/xxx.mp4"
  }
}

Status Enum

2.3 Download Video Content

GET /v1/videos/{task_id}/content

Returns raw video bytes (Content-Type: video/mp4). AutoRouter proxies the PixVerse temporary URL so your client never sees the upstream URL, and you don't have to worry about URL expiration.

Strongly recommended: use the /content proxy endpoint to download videos, not the raw metadata.url. The raw URL is a temporary link (usually valid for a few hours); the proxy endpoint never expires as long as the task record exists.

3. PixVerse-Specific Parameters (metadata)

All PixVerse-specific fields are passed via the metadata object in the request body.

3.1 Common Fields

motion_mode: fast has strict limits: only V4.5 / V4 / V3.5 models, at 5s duration, and at 360p/540p/720p resolution. Illegal combinations (e.g., 1080p + fast or 8s + fast) will return a 400 error with no charge.

3.2 Audio Generation (C1 / V6 / V5.6 / V5.5)

V5 / V4.5 / V4 / V3.5 do not support audio generation. Passing generate_audio_switch: true on these models returns a 400 error.

3.3 Image-to-Video Advanced Fields

PixVerse image-to-video requires uploading an image first to get an img_id. AutoRouter automates the upload step:

• Pass image: "https://..." or image: "data:image/png;base64,..." in the request body
• AutoRouter uploads to PixVerse and forwards the img_id automatically

If you already have an img_id (advanced use case), you can pass it directly:

4. Full Examples

# Step 1: Submit the task
curl -X POST https://autorouter.top/v1/videos \
  -H "Authorization: Bearer sk-YourApiKey" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "PixVerse/v5.6",
    "prompt": "A cat walking on the moon with a starry background",
    "duration": 5,
    "size": "720p",
    "metadata": {
      "aspect_ratio": "16:9",
      "seed": 42
    }
  }'

# Response:
# {
#   "id": "task_abc123...",
#   "task_id": "task_abc123...",
#   "status": "queued",
#   ...
# }

# Step 2: Poll for status (every 3~5 seconds is recommended)
curl https://autorouter.top/v1/videos/task_abc123... \
  -H "Authorization: Bearer sk-YourApiKey"

# Step 3: Once status is "completed", download the video
curl https://autorouter.top/v1/videos/task_abc123.../content \
  -H "Authorization: Bearer sk-YourApiKey" \
  -o cat_on_moon.mp4

curl -X POST https://autorouter.top/v1/videos \
  -H "Authorization: Bearer sk-YourApiKey" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "PixVerse/v5.6",
    "prompt": "Make the cat jump",
    "image": "https://example.com/cat.jpg",
    "duration": 5,
    "size": "720p"
  }'

# Encode image as a data URI
IMG_BASE64=$(base64 -i cat.jpg)

curl -X POST https://autorouter.top/v1/videos \
  -H "Authorization: Bearer sk-YourApiKey" \
  -H "Content-Type: application/json" \
  -d "{
    \"model\": \"PixVerse/v5.6\",
    \"prompt\": \"Make the cat jump\",
    \"image\": \"data:image/jpeg;base64,${IMG_BASE64}\",
    \"duration\": 5,
    \"size\": \"720p\"
  }"

# C1 / 720p / 5s with upstream-synthesized audio
curl -X POST https://autorouter.top/v1/videos \
  -H "Authorization: Bearer sk-YourApiKey" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "PixVerse/c1",
    "prompt": "Ocean waves crashing on the shore, seagulls circling above",
    "duration": 5,
    "size": "720p",
    "metadata": {
      "generate_audio_switch": true,
      "aspect_ratio": "16:9"
    }
  }'

5. Error Handling

5.1 HTTP 400 Invalid Parameters (intercepted pre-submit, no charge)

AutoRouter strictly validates parameter combinations before forwarding upstream. The following illegal combinations return 400 Bad Request:

5.2 HTTP 401 / 403 Auth Errors

• 401 Unauthorized: API Key invalid or expired
• 403 Forbidden: API Key not authorized for this model (check token model whitelist)

5.3 HTTP 402 Insufficient Balance

Returns insufficient user quota. Please top up in the AutoRouter console.

5.4 Task failed Status

Task was accepted but generation failed. Common reasons:

When a task ends with failed, AutoRouter automatically refunds the charge to your account. Refund records are visible in the console logs page.

6. FAQ

How should I format the model field?

Use the PixVerse/<version> form, e.g., PixVerse/c1 / PixVerse/v6 / PixVerse/v5.6 / PixVerse/v5.5 / PixVerse/v5 / PixVerse/v4.5 / PixVerse/v4 / PixVerse/v3.5. The PixVerse/ prefix is the public display name and must be included. The version suffix is case-insensitive but lowercase is recommended.

Should I use '720p' or '1280x720' for size?

Both work. AutoRouter internally maps both forms to PixVerse's quality parameter (360p / 540p / 720p / 1080p). metadata.quality overrides top-level size.

How do duration limits differ across models?

• PixVerse/c1 / PixVerse/v6: per-second billing, any 1~15s value
• PixVerse/v5.6 / PixVerse/v5.5: fixed tiers 5 / 8 / 10s
• PixVerse/v5: fixed tiers 5 / 8s
• PixVerse/v4.5 / PixVerse/v4 / PixVerse/v3.5: fixed tiers 5 / 8s (fast mode is 5s only)

Unsupported values return 400 without charging.

Do I need to upload the image first for image-to-video?

No. PixVerse officially requires two steps (upload → generate), but AutoRouter wraps it into one: just pass image: "https://..." or base64, and the server auto-uploads and forwards the img_id. If you already have an img_id, pass it in metadata.img_id to skip the upload.

How long does a task typically take?

Typical latencies:

• 360p / 540p / 5s video: 10 ~ 30 seconds
• 720p / 5s video: 30 ~ 60 seconds
• 1080p / 8s video: 60 ~ 120 seconds
• May be longer under high load

Poll every 3~5 seconds and timeout after 10 minutes.

Do video URLs expire?

Yes. The raw metadata.url is a temporary link (usually valid for a few hours). Please download or re-host the video to your own storage promptly after obtaining it.

How do I pick the right model?

• Best quality, flexible per-second billing: PixVerse/c1 (flagship)
• Need audio: PixVerse/c1 / PixVerse/v6 / PixVerse/v5.6 / PixVerse/v5.5
• Need fast motion: PixVerse/v4.5 / PixVerse/v4 / PixVerse/v3.5 + motion_mode: fast
• General purpose / best value: PixVerse/v5.6 (recommended default)