PixVerse AI Models
PixVerse V6 video generation — text, image, reference, transition, and extension capabilities behind one key.
PixVerse develops video generation models. PixVerse V6 exposes five capabilities through RunAPI — text-to-video, image-to-video, reference-guided generation, frame transitions, and extension of finished results — with clips from 1 to 15 seconds and optional synchronized audio.
- Single API key shared across all providers
- No separate PixVerse account required
- Model skills carry docs, schemas, and setup steps into your workspace
- Per-call billing in USD, no subscription or minimum spend
- Failed generations are never charged
- Switch models by changing one parameter
- Billing consolidated into one monthly invoice
What stands out
One of the most-used model APIs from PixVerse, chosen by developers for its balance of output quality, speed, and pricing.
One of the most-used model APIs from PixVerse, chosen by developers for its balance of output quality, speed, and pricing.
Lowest starting price across the PixVerse catalog, suited for high-volume workflows and cost-sensitive production pipelines.
All PixVerse models available through RunAPI
Install a PixVerse model skill for your app.
Pick a model and add its skill so your coding tool has docs, schemas, pricing notes, and setup steps. Skills work with Claude Code, Codex, Gemini CLI, Cursor, and VS Code. Install once, then switch models by changing one parameter.
curl -X POST https://runapi.ai/api/v1/pixverse/extend_video \
-H "Authorization: Bearer $RUNAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "pixverse-v6",
"task_id": "task_abc123"
}'import { PixverseClient } from "@runapi.ai/pixverse";
const client = new PixverseClient();
const result = await client.extendVideo.run({
model: "pixverse-v6",
task_id: "task_abc123",
});require "runapi/pixverse"
client = RunApi::Pixverse::Client.new
result = client.extend_video.run(
model: "pixverse-v6",
task_id: "task_abc123"
)npx skills add runapi-ai/pixverse -g# Claude Code
claude mcp add runapi -s user -- npx -y @runapi.ai/mcp
# Codex
codex plugin install runapi-mcp@agents
# Cursor / Windsurf / VS Code
npx @runapi.ai/mcp init cursorFrequently asked questions about PixVerse
Is this an official PixVerse integration?
RunAPI exposes a managed API surface with transparent per-call pricing, fully documented capability and parameters, and clear error behavior. You get the same model output quality without managing a direct provider relationship or provider-side account.
Do I need a PixVerse account?
No. Your RunAPI API key is enough for managed access to all PixVerse models. You do not need to create a separate account, manage provider-specific credentials, or handle provider-side billing.
What's the latency overhead from proxying through RunAPI?
Typically under 20 ms. RunAPI keeps the proxy layer close to model execution regions to minimize added latency. Media generation time is dominated by the model itself, not the proxy.
Are images / videos cached?
Generated outputs are stored and retrievable by task ID. You can fetch completed results at any time using the task status endpoint or the RunAPI dashboard. Output URLs remain accessible for the retention period shown in the API docs. Inputs are not cached or stored.
Can I bring my own key?
Not currently. Calls use RunAPI-managed access, which simplifies authentication and lets RunAPI handle rate limiting, retries, and billing consolidation on your behalf.
How is billing consolidated?
All API calls across all providers appear on a single monthly USD invoice. There is no per-provider billing, no subscription, and no minimum spend. Failed generations are never charged.
What SDKs can I use with PixVerse models?
Official SDKs are available for Python, Node.js, PHP, Java, Ruby, and Go. Each SDK handles authentication, async task polling, and typed responses. For LLM models, the OpenAI and Anthropic SDKs also work by pointing the base URL to RunAPI.
What are model skills and how do they work?
Model skills are installable packages that load a model's docs, typed schemas, pricing notes, and setup steps directly into your coding workspace. Install a skill with one command and your agent has the right context before you write integration code. Skills work with Claude Code, Codex, Gemini CLI, Cursor, and VS Code.
How do I switch between PixVerse models?
Change the model parameter in your API request. All PixVerse models share the same API key, the same request shape, and the same billing. No code changes, no re-authentication, and no separate billing setup are required when switching between models or between variants of the same model. You can also switch to models from other providers by changing the same parameter — the API surface is unified across the entire catalog.