App route: text-to-video; Google also documents image inputs
Resolution reference
Google: 720p / 1080p / 4K
Duration reference
Google: 4, 6 or 8 seconds; higher-resolution constraints apply
Audio reference
Google: native audio
Serving host
WaveSpeed
Catalog status
App-listed in owner audit; not live-tested
API model or route: google/veo3.1/text-to-video
App catalog ID: veo-3.1
Capabilities & boundaries
What it supports. What the app exposes.
Provider features and app integration are different layers. A feature in the upstream documentation is not automatically enabled in your workspace.
Model and hosting capabilities
Google documents audiovisual generation and 24 fps output for this Veo generation.
At the provider level, written scene descriptions and supported image inputs can guide a shot; this app route is text-to-video.
Google documents reference-image and extension workflows with their own duration and resolution restrictions.
Before you choose
The shared app wrapper and the host's accepted durations can differ. A value inside the app's clamp is not necessarily valid for this specific endpoint.
Google requires 8-second requests for 1080p, 4K where supported, and reference-image workflows. Do not apply the wrapper's default 5 seconds as a universal valid Veo duration.
Google's direct API capabilities and prices do not prove identical WaveSpeed options or app billing. A seed is not a guarantee of deterministic output.
Review motion, anatomy, continuity and any generated sound before publishing. Prompt instructions are creative targets, not guarantees of an exact result.
Only upload media you have permission to use, including consent for identifiable performers. Provider safety rules and usage terms still apply.
Controls in the audited app integration
The audited WaveSpeed wrapper forwards prompt, duration and aspect_ratio. It clamps duration to 3–10 seconds (default 5); this is a wrapper range, not the endpoint's supported set of durations.
Resolution and audio settings are not forwarded by this wrapper. Neither are reference images, seed or advanced camera controls. Provider support for them does not establish app support.
Put it to work
Start with a more useful visual brief.
Original examples from EZ Ai Assist. Choose supported controls separately. Some workflows require source media; a text brief does not supply those inputs.
Workflow 01
Workshop atmosphere
Start with one clear action and a restrained camera move. Select supported duration and framing separately, then inspect continuity in the result.
A wooden toy sailboat sits on a craftsperson's bench. The camera drifts slowly past its fabric sail as fine dust moves through a sunbeam. Maintain the boat's geometry and realistic scale, with one continuous shot and a still frame at the end.
Workflow 02
Outdoor establishing shot
Start with one clear action and a restrained camera move. Select supported duration and framing separately, then inspect continuity in the result.
A narrow footbridge crosses a clear stream in a mossy forest. Move the camera gently forward from the near bank while leaves stir and water flows beneath the bridge. Keep the horizon level, the bridge intact and the scene free of people or signs.
Workflow 03
Food detail
Start with one clear action and a restrained camera move. Select supported duration and framing separately, then inspect continuity in the result.
Show a single ripe peach on a white plate as a small droplet slowly travels down its skin. Use a steady macro camera and soft window light. Preserve the fruit's shape and fine texture, with no hands, extra fruit or sudden focus changes.
Developer reference
Provider & hosting API pricing
Public provider or hosting API reference prices in USD, not EZ Ai Assist subscription prices or app charges. Check the app for your current plan, allowance and charge before generating.
These are Google's direct Gemini API rates, not the WaveSpeed route's charges. Audio is included in the quoted Google rates; the app's audio switch is not forwarded by its WaveSpeed wrapper.
The owner audit found differences between some app-card estimates and backend calculations. This website update does not change or certify app billing.
Common questions
VEO 3.1 FAQs
What is VEO 3.1 useful for?
VEO 3.1 specifications, Google reference rates and practical shot briefs, with WaveSpeed routing and the audited app's parameter limitations explained.
Which inputs does this workflow need?
App route: text-to-video; Google also documents image inputs. Confirm that the app accepts any required media before using a provider-only workflow.
What duration and resolution can I use?
Google: 4, 6 or 8 seconds; higher-resolution constraints apply. Google: 720p / 1080p / 4K. Provider values, app labels and successful runtime behavior are different layers; the audit is not a generation test.
Are these prices what EZ Ai Assist charges?
Public provider or hosting API reference prices in USD, not EZ Ai Assist subscription prices or app charges. Check the app for your current plan, allowance and charge before generating. These are Google's direct Gemini API rates, not the WaveSpeed route's charges. Audio is included in the quoted Google rates; the app's audio switch is not forwarded by its WaveSpeed wrapper.
Is this model available or retired?
This choice appears in the owner-supplied app audit. No provider retirement date is asserted without a model-specific notice. Check current app access and the linked provider references; a catalog listing is not a live availability test.
Sources & freshness
Check the original references.
Reviewed . Public provider or hosting documentation supports the reference specifications and prices. App behavior is based on the owner-supplied code-audit reports labeled October 9, 2026, not live generation tests. No retirement date is inferred from a missing listing, a legacy name or an unresolved route.