Enterprise DNAEnterprise DNA
LModelsBest vision
Google logo

Veo-3.1

by Google

Video model for prompt-guided generation, editing, and motion workflows

Visit GoogleSubmit your build →
V

Models

Veo-3.1

Added 13 July 2026

#google#tool-call

Overview

Video model for prompt-guided generation, editing, and motion workflows

Best for

Best for
Directed short video

How to use / API access

Call via other with model id `google/veo-3.1`.

  • other · google/veo-3.1

OpenRouter id: google/veo-3.1

Notes

Veo-3.1 is listed in the EDNA Models directory, sourced from models.dev.

Pros

  • Developing a scene from text or an owned reference image
  • text, image input; video output on the listed OpenRouter route

Cons

  • Confusing video generation with analysis of an uploaded video
  • Quoting a zero token row as a complete video price
  • This route produces non-text output or rerank results. Listed text-token rates are not a complete workload price; zero text-token rates do not mean free generation. Verify the route-specific billing unit before estimating cost.
Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.

← Back to ModelsSubmit your own entry →

MODEL FIELD GUIDE / SOURCE EVIDENCE

What you can do with Veo-3.1.

Specifications reviewed; no EDNA task evaluation has been run. Sources checked 2026-10-20. Hosting routes and app features can differ.

DeveloperGoogle
Exact model identifiergoogle/veo-3.1
Inputtext, image
Outputvideo
Tool calling
Not established
Structured output
Listed support
Reasoning controls
Not established
Availability
available
Price basis
unknown
Licence verification
Check the developer licence; the model name is insufficient

This route produces non-text output or rerank results. Listed text-token rates are not a complete workload price; zero text-token rates do not mean free generation. Verify the route-specific billing unit before estimating cost.

Consider it for

  • Developing a scene from text or an owned reference image
  • Testing frame-specific direction in an existing Veo workflow

Watch for

  • Confusing video generation with analysis of an uploaded video
  • Quoting a zero token row as a complete video price

PRACTICAL EXERCISE / NOT RUN BY ENTERPRISE DNA

Try the model on a small, checkable task.

Create a short fixed-camera shot of a red paper boat moving across a shallow puddle, with natural rain sound and no captions or people.

Check the result: Inspect temporal continuity, fixed camera, boat identity and requested sound; no generation has been run.

Compare another approach

bytedance seedance 2 0 ↗
Inspect the sources and their scope
provider source ↗

Developer documentation for model family or task. OpenRouter route-specific properties remain catalogue claims; EDNA has not executed a task evaluation.

Checked 2026-10-19
catalogue source ↗

google/veo-3.1: listed route capabilities, availability and prices; provider endpoints can differ.

Checked 2026-10-20
How to evaluate a model for your work →

FROM SPECIFICATIONS TO YOUR WORK

Is this the right model for your job?

Start with a realistic sample. These workflows match the model’s listed capabilities, not a verified result on your task.

Understand the capabilitiesRead the model guide ↗

Check the source

This route uses unknown pricing. A token calculator is not a quote for this model. Your app subscription, uploads, browsing and tools are separate.

Model source & availability ↗

Understand the evidence

Listed capabilities and third-party benchmark scores do not establish Enterprise DNA task-test results. Validate accuracy and total cost on your own sample.

Compare this model with alternatives →