Google Veo 3.1 generates short videos from text and images with realistic motion, native audio options, multiple quality tiers, and reference-guided control.
• Price shown is charged from the model configuration in admin.
• Calls consume current account credits and write usage records.
• Media tasks are processed with the same async pipeline as the public API.
Pricing
Model ID
Type
Quality
Price
veo3-1-fast-4k
Video Generation
Default
660 credits per request · ≈ $0.33-$0.66
Model IDveo3-1-fast-4k
TypeVideo Generation
QualityDefault
Price660 credits per request · ≈ $0.33-$0.66
Model overview
What is the Veo 3.1 API?
Google Veo 3.1 generates short videos from text and images with realistic motion, native audio options, multiple quality tiers, and reference-guided control.
Start with the desired visual outcome, references, and delivery format, then shape the generation workflow around them.
APIAny exposes Veo 3.1 through one documented API surface with live pricing, model status, request examples, and an on-page playground. Teams can evaluate the model here, then keep authentication, usage records, and production routing in the same platform.
These workflows show where Veo 3.1 fits in a real product. Test the same inputs in the playground, compare the output with related models, and choose the route that meets your quality, latency, and budget requirements.
01
Cinematic scenes and visual storytelling
Use Veo 3.1 for composed shots, narrative sequences, and atmosphere-led video concepts. Detailed prompts and reference inputs make camera direction, visual continuity, and mood easier to evaluate.
Cinematic scenes and visual storytelling with Veo 3.1.
02
Short-form social video
Use Veo 3.1 to produce short clips for social posts, campaign variants, and concept testing. Evaluate motion, framing, duration, and audio options against the target publishing format.
Turn product images or written concepts into review-ready motion with Veo 3.1. Reference-led generation helps teams explore transitions, camera movement, and short demonstrations before final production.
The following capabilities explain the practical input, output, and workflow characteristics that matter when evaluating Veo 3.1. Available request parameters remain visible in the live API reference on this page.
How Veo 3.1 capabilities work together.
/01
Text prompt input
Describe the requested output or task in text and send it through the documented Veo 3.1 API request.
/02
Image and reference input
Provide supported image inputs to guide editing, visual identity, composition, or motion in Veo 3.1 workflows.
/03
Video generation output
Create short video results with Veo 3.1 and retrieve completed media from the asynchronous task workflow.
/04
Audio-aware video generation
Use supported Veo 3.1 variants to create video workflows that can include synchronized sound or audio controls.
/05
High-resolution output
Select supported quality or resolution tiers when the final Veo 3.1 asset needs more detail for review or delivery.
/06
Reference-guided generation
Use supported reference assets to guide subject identity, style, composition, frames, or motion across generated results.
/07
Asynchronous task API
Create a task, store its identifier, and poll or receive a callback until the Veo 3.1 generation reaches a terminal state.
APIAny advantages
Why use Veo 3.1 through APIAny?
APIAny combines direct model access with the operational controls needed to move from evaluation to production without maintaining a separate integration for every provider.
Production value delivered by Veo 3.1.
One stable API surface
Call Veo 3.1 with an APIAny key and a documented request format. Keep your application integration stable while model versions and upstream routes evolve behind the gateway.
Transparent usage and pricing
Review the live Veo 3.1 pricing rules before a request, estimate credits in the playground, and inspect request-level usage records after the call completes.
Production routing controls
Use model status, channel health, retry policy, and usage logs to operate Veo 3.1 as part of a production workflow instead of treating it as an isolated demo.
Integration
How to integrate the Veo 3.1 API
Move from a playground test to an authenticated production request in three steps. The page keeps the model identifier, request schema, pricing, and response examples together. Treat generation as an asynchronous media pipeline with durable task tracking, validation, and asset delivery.
Connecting Veo 3.1 from API request to result.
01
Create an API key
Sign in to APIAny, create a project API key, and assign only the model scope and budget controls your application needs.
02
Send a Veo 3.1 request
Copy the request example from this page, set the model field to the selected Veo 3.1 version, and send it to the documented APIAny endpoint.
03
Monitor and refine
Track status, latency, credits, and returned usage. Compare versions or related models with the same workload before shifting production traffic.
FAQ
Veo 3.1 API frequently asked questions
Direct answers about capabilities, use cases, integration, and choosing the right Veo 3.1 route.
What is the Veo 3.1 API?
Google Veo 3.1 generates short videos from text and images with realistic motion, native audio options, multiple quality tiers, and reference-guided control. APIAny makes this model callable through an authenticated API with live pricing, status information, request examples, and a browser playground on the same page.
What can I build with the Veo 3.1 API?
Common Veo 3.1 workflows include Cinematic scenes and visual storytelling, Short-form social video, Product demos and launch motion. The best fit depends on the input format, output quality, latency, and cost your product requires.
How do I call Veo 3.1 through APIAny?
Create an APIAny key, use the endpoint documented on this page, and set the request model field to the selected Veo 3.1 version. The playground can generate a working payload before you integrate it into application code.
How should I choose a Veo 3.1 version?
Compare the versions shown on this page by price, supported parameters, and capabilities such as Text prompt input, Image and reference input, Video generation output. Test a representative production input before choosing the default route.
API Reference
Call this model through a standard REST API. Authenticate with your API key, then pick an endpoint below to see its parameters and examples.
Authentication
Every request needs a Bearer token in the Authorization header. Create an API key in the console.
Authorization: Bearer YOUR_API_KEY
POSThttps://apiany.ai/v1/videos/generations
Request parameters
Parameter
Type
Required
Notes
model
string
Required
Model identifier to invoke. Use this model's ID.
prompt
string
Required
Text prompt describing what you want to generate.
aspect_ratio
string
Optional
Veo 3.1 public route currently exposes 16:9 and 9:16. · Options: 16:9, 9:16 · Default: 16:9
callback_url
string
Optional
Optional webhook URL called when the async task finishes.
Request example
curl "https://apiany.ai/v1/videos/generations" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "veo3-1-fast-4k",
"prompt": "A smooth cinematic camera arc around a futuristic API operations room, native audio, high contrast studio lighting",
"aspect_ratio": "16:9"
}'
This endpoint is asynchronous: it returns a task_id immediately. Poll the task-status endpoint until status becomes succeeded, then read the result. Generated media links stay valid for 24 hours.