PixVerse Model API
API Docs

AI video and image generation API

Add PixVerse generation to your product without building the model stack.

PixVerse Model API gives product teams documented building blocks for text-to-video, image-to-video, reference-led video, templates, effects, audio, lip sync, and async result handling.

Explore API Platform Contact Team
1080p video Up to 15s clips Async workflows Webhook support

When API is the right motion

Use API when PixVerse needs to live inside the customer’s product.

The buyer is usually not looking for another creative workspace. They need generative media as infrastructure: reliable requests, predictable outputs, clear docs, and a path from sandbox to production.

AI tools

Creation features inside an existing product

Video generation, image generation, effects, or remixing becomes part of the customer’s own user experience.

Creator platforms

UGC, social, community, and sharing flows

Users create, preview, continue, and share generated media without leaving the platform.

Commerce and marketing

Campaign and product-content automation

Product assets, campaign briefs, and reference images turn into video-ready creative concepts.

Game, media, education

Visual storytelling at product speed

Teams add scenario, avatar, explanation, character, trailer, or interactive content workflows.

Integration workflow

A simple request lifecycle for product teams.

PixVerse API is designed around the product flow builders already understand: collect input, create a task, handle progress, and return a result to the user interface.

Input

Prompt, image, video, audio, or reference

Start from the asset type that matches the feature being built.

Generate

Create an async task

Use the endpoint and parameters that match the selected workflow.

Observe

Trace, poll, or webhook

Use trace IDs, task status, and callbacks to keep the product experience clear.

Deliver

Preview, continue, save, or share

Bring the generated result back into the customer’s product flow.

API capabilities

A fuller map of the PixVerse API surface.

The customer does not need every parameter on this page, but they should see the breadth of what can be evaluated. The public API docs remain the source of truth for schemas, supported inputs, pricing, and limits.

Core generation

Start from prompt, image, or template.

  • Text-to-Video generation
  • Image-to-Video generation
  • Template video generation
  • Video Effects generation
  • Image generation and Image Template generation
Reference and structure

Control what appears and how scenes connect.

  • Transition / first-last frame generation
  • Multi-transition video generation
  • Fusion / reference-to-video generation
  • V6 video reference integration
Edit and improve

Turn existing output into a better asset.

  • Extend generation
  • Modify generation
  • Restyle video generation
  • Restyle effect list
  • Upscale Video
Motion and replacement

Reuse motion or replace a selected subject.

  • Motion Control / Mimic generation
  • Swap mask generation
  • Swap video generation
Audio, voice, avatar

Add speech, sound, or avatar-led video.

  • Sound effect generation
  • Speech / Lip sync generation
  • Lip sync TTS speaker list
  • Avatar generation
  • Create Custom Voice
  • Delete Custom Voice
Agent workflows

Use packaged workflows for higher-level outcomes.

  • Viral Recreation Agent
  • One-click Real Estate Video
Media and templates

Prepare assets and discover reusable formats.

  • Upload Image
  • Upload Video and Audio
  • Get template list
Operations

Run the integration like production software.

  • Get Video Generation Status
  • Get user credit balance
  • Usage Deduction Query
  • Webhook integration
  • Rate limit and concurrency planning

Model layer

V6 and C1 cover the core production-grade video paths.

Public PixVerse materials position V6 around 15-second 1080p generation, multi-shot structure, native audio, flexible aspect ratios, and stronger text-to-video or image-to-video results from one creative workspace.

V6

General video generation for product and creative workflows.

  • Text-to-video and image-to-video
  • First/last-frame transition
  • Video extension
  • Reference-to-video fusion
  • Inline audio and multi-clip controls
C1

Cinematic, high-fidelity generation for stronger visual direction.

  • Text-to-video and image-to-video
  • First/last-frame transition
  • Reference-to-video fusion
  • Inline audio generation
  • Up to 15 seconds and 1080p
How to evaluate

Run one real product scenario before discussing scale.

Ask the customer to test their own prompt, image, reference package, or user workflow. Review motion stability, subject fidelity, instruction following, sound timing, and whether the result fits the product experience.

Evaluation material

Help technical buyers make a decision, not just watch a demo.

Technical fit

Docs coverage, endpoint choice, request parameters, result status, webhooks, trace IDs, media upload, balance query, and error-handling path.

Output fit

Quality, prompt adherence, motion stability, visual fidelity, aspect ratio, duration, audio behavior, and limits for the specific customer workflow.

Operational fit

Concurrency, usage tracking, pricing in credits, procurement process, production support, and plan or volume conversation.

Credits, limits, and commercial path

Keep pricing concrete and route scale questions early.

Public docs define generation pricing in credits per second, with different rates by model, resolution, and audio. Higher concurrency is plan-based and should be discussed before production launch.

Example video-generation credits

Model720p no audio1080p no audio1080p audio
V69/sec18/sec23/sec
C110/sec19/sec24/sec

Reference-to-video with video references can consume higher credits. Confirm final pricing against the live docs before quoting.

Concurrency tiers

Free3
Essential15
Scale20
Business25

Concurrent requests are simultaneously generating tasks. Larger production needs should be discussed with the team before launch planning.

Enterprise confidence

Bring procurement and engineering into the same conversation.

For production API buyers, trust is part of the product. PixVerse public materials include ISO/IEC 27001 certified information security management and SOC 2 controls for service organizations.

ISO/IEC 27001

Certified information security management

PixVerse maintains an information security management system certified by DNV to ISO/IEC 27001.

SOC 2

Service organization controls

PixVerse applies SOC 2 controls supporting secure operations and customer information protection.

Support packet

Make issues diagnosable

Collect environment, account, endpoint, request time, error code, trace ID, logs, and reproduction steps before escalation.

FAQ

Questions buyers usually ask before starting an API evaluation.

What can we build with the PixVerse API?

Product experiences around text-to-video, image-to-video, image generation, templates, effects, creative transformations, reference-led video, sound, and lip-sync workflows.

Should we start with V6 or C1?

Start with the model that matches the first customer workflow. V6 is the broad default for modern video generation workflows; C1 is positioned for cinematic, high-fidelity visual output. Test with the customer’s own scenario.

How should we evaluate a POC?

Pick one live user journey, build the request path, review generated outputs, confirm status/webhook handling, estimate credit usage, and agree what production concurrency or support would require.

Where do we get the latest implementation details?

The public API documentation is the source of truth for endpoint schemas, parameters, rate limits, pricing, and limitations.

Next step

Evaluate PixVerse with one real workflow.

Start with the docs, test a real scenario, then bring the output, integration questions, and production needs to the PixVerse team.

Read API Docs View V6 Contact Team