Text to video
Turn a complete shot brief into a generated video sequence.
All API models
VideoGoogleAvailable
MODEL API
Veo 3.1 API
Cinematic video generation with image guidance, shot control, first/last frames, and native audio.
- Text to video
- Image to video
- Native audio
- First / last frame
API usage is billed separately from Studio credits.
LIVE REQUEST BUILDER
Try the API in the playground
Configure a request, inspect the exact JSON, then run it with your account.
API key
Loading keys…
Response
The API response will appear here.
API PRICING
Programmatic pricing, separate from Studio
Compare the complete API billing table for this route. Token models separate input, output, cache-read, cache-write, and long-context rates; media models vary by configuration.
Entry configuration720P
Billing unitPer generated second
API price$0.38 / sec
Comparable Studio price$0.48 / sec
API launch saving21%
Resolution tiers
720P$0.38 / second
1080P$0.38 / second
4K$0.55 / second
The accepted task response is the source of truth for its final pricing snapshot.
CAPABILITIES
What this route supports
Use one stable PixMind model ID while keeping provider-specific setup out of your application.
Image to video
Animate a supplied image while preserving its subject and visual direction.
Native audio
Generate an audio-capable result on supported video routes.
First / last frame
Control a transition by defining both the opening and closing composition.
MODEL WORKFLOWS
What to build with Veo 3.1
Choose a task that matches the live route capabilities, then adapt one of these prompt starters.
Best-fit tasks
- Turn a complete shot brief into a generated video sequence.
- Animate a supplied image while preserving its subject and visual direction.
- Generate an audio-capable result on supported video routes.
- Control a transition by defining both the opening and closing composition.
Prompt starters
Replace the bracketsStarter
Create one [duration]-second shot of [subject] in [setting]. The subject [action]. Camera: [movement and framing]. Lighting: [direction and mood]. Keep motion physically coherent and the shot continuous.
Starter
Animate the supplied image into a [duration]-second shot. Preserve [subject details]. Add [subject motion] and [camera motion]. Keep the original composition, lighting, and visual identity stable.
Starter
Start exactly from the first frame and end on the supplied last frame. Build one continuous transition where [subject or camera action] connects both compositions without cuts.
MODEL SELECTION
Choose Veo 3.1 when the job fits
Compare nearby live routes by task, supported capability, and current entry price before you lock a model ID into production.
| Model | Best for | Key capabilities | Entry price | Availability | Action |
|---|---|---|---|---|---|
Veo 3.1 Google · current page | Turn a complete shot brief into a generated video sequence. | Text to video · Image to video · Native audio | $0.38 / sec | Available | Selected |
Veo 3 Google | Turn a complete shot brief into a generated video sequence. | Text to video · Image to video | Pricing coming soon | Planned | View route |
Veo 3.0 Fast Google | Turn a complete shot brief into a generated video sequence. | Text to video · Image to video | Pricing coming soon | Planned | View route |
Veo 3.1 Eco Google | Turn a complete shot brief into a generated video sequence. | Text to video · Image to video | Pricing coming soon | Planned | View route |
Capabilities and starting prices are a current PixMind route snapshot. The accepted request contains the final configuration and billing quote.
GET STARTED
From playground to production
Create a scoped key
Create an API key for the image or video permission this route needs.
Send the request
Use the model ID and endpoint shown above from your backend service.
Track the task
Store the returned task ID and query its status until it reaches a terminal state.
FAQ
Veo 3.1 API questions
What model ID should I use for the Veo 3.1 API?+
Use veo-3.1 in the model field. This is the stable PixMind route identifier shown in the playground request JSON.
Which endpoint does the Veo 3.1 API use?+
Send POST requests to /v1/generations. Keep your API key on your server and pass it as a Bearer token.
Is the playground using a real API request?+
Yes. When you click Run model, PixMind forwards the displayed payload with the API key you entered. A successful request may create a paid task.
Does PixMind save the API key entered here?+
No. The playground keeps the key only in component memory and sends it for the current request; it is not written to browser storage.
Is API pricing the same as PixMind Studio pricing?+
No. API usage resolves through the apiPlatform pricing role and a separate pay-as-you-go ledger. Studio pricing includes the creation interface and product workflow services.
Why can the final price differ from the starting price?+
The entry price reflects the configuration displayed on this page. Resolution, duration, quality, audio, references, and output count can affect the final task price.
How do I receive a finished image or video?+
Generation routes can return an asynchronous task. Save its ID and query the task endpoint until the status is succeeded, failed, or cancelled.
Can I use the same integration for other PixMind models?+
Yes. Models in the same workload family share the generation contract, so switching usually means changing the model ID and supported parameters.
START WITH THE CONTROL PLANE
Turn your first Veo 3.1 prompt into a real API request
Test the exact payload in the playground, then create a scoped key and move the same model ID into your application.