PixVerse · Video

OpenClaw x PixVerse

PixVerse V6 handles text-to-video, image-to-video, reference-guided edits, frame transitions, and extensions through RunAPI. One model version serves all five endpoints, so the same key and pricing model apply across every capability.

Public versions and endpoints

Model ID	Version	Endpoints	Starting price	Catalog
`pixverse-v6`	pixverse-v6	`/api/v1/pixverse/image_to_video` `/api/v1/pixverse/edit_video` `/api/v1/pixverse/text_to_video` `/api/v1/pixverse/transition_video` `/api/v1/pixverse/extend_video`	$0.190	Model detail

Configuration

Guide endpoint: /api/v1/pixverse/text_to_video

export RUNAPI_API_KEY=your_api_key

curl -X POST https://runapi.ai/api/v1/pixverse/text_to_video \
  -H "Authorization: Bearer $RUNAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "pixverse-v6",
  "prompt": "A cinematic lantern festival above a calm river.",
  "output_resolution": "720p",
  "duration_seconds": 5,
  "aspect_ratio": "16:9"
}'

Verify

POST /api/v1/pixverse/text_to_video and save the returned Task id.
GET /api/v1/pixverse/text_to_video/<task-id> until status is completed or failed.
Verify the completed response contains the endpoint-specific output documented in the API reference.

How it works

1. Choose a model ID
Select a public catalog model ID and review its endpoint and current starting price.
2. Configure RunAPI
Set RUNAPI_API_KEY before making the endpoint request.
3. Verify the result
For asynchronous endpoints, poll the same endpoint until the Task reaches a terminal status.

FAQ

Which model ID should I use?

Choose a public model ID from the version table. Each ID exposes the endpoints shown for that version.

Does this guide configure a chat model?

No. This Model Line uses the endpoint workflow shown here and is not presented as an agent chat model.