Skip to content

Google: Veo 3.1 provider comparison

google/veo-3.1

Google's state-of-the-art video generation model, built for maximum visual fidelity in final production cuts. Veo 3.1 generates high-quality 1080p video from text or image prompts with native synchronized audio —...

Endpoints:
1
Context:
0
Input:
text, image
Output:
video

Visual comparison

Endpoint pricing chart

Compare published endpoint pricing visually.

Effective price by endpoint

USD per second for duration seconds with audio. Lower is better.

Only directly comparable published units are charted.

Server-rendered comparison

Provider endpoints

Video prices use OpenRouter’s dedicated pricing SKUs, including resolution-specific per-second units. Missing speed data never removes an endpoint.

Endpoint comparison for Google: Veo 3.1
Provider / routeCurrent pricingSpeed measurementsEndpoint details
Provider / route
Google Vertexgoogle-vertex
Current pricing
  • $0.4 per second (duration seconds with audio)
  • $0.6 per second (duration seconds with audio 4k)
  • $0.2 per second (duration seconds without audio)
  • $0.4 per second (duration seconds without audio 4k)
Speed measurements
500-token response
Not applicable
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Uptime (30 min)
Insufficient recent data
Context
0
Model format
unknown
Max output
N/a
5 parameters

max_tokens, response_format, seed, temperature, top_p

Endpoint data fetched .

Veo 3.1 deployment guide

How to choose a Veo 3.1 inference provider

Veo 3.1 is indexed here as a video model by Google, with 1 provider endpoint from Google Vertex. The comparison preserves each exact OpenRouter routing tag so pricing and performance observations can be connected to the route an application would actually request.

Match the endpoint to the workload

The model publishes a 0-token context window. It accepts text, image input and returns video output. 5 distinct supported parameters appear across the listed routes. Confirm limits on the specific endpoint rather than assuming every host exposes the same configuration.

Compare video billing units directly

At least one second is published consistently across the listed endpoints, allowing a direct price chart for duration seconds with audio. Other charges remain in the table using OpenRouter’s exact billing labels.

Verify route format and availability

Published endpoint formats include unknown. Availability, rate limits, and regional support can change independently of catalog pricing, so confirm the selected routing tag before production deployment.