Google DeepMind · video · exact comparison

Veo 3.1 API pricing by provider

Review source-linked Veo 3.1 API pricing across first-party and hosted routes without mixing configurations.

Current answer: 7 accepted Veo 3.1 observations; one current example is $0.1 / video second, checked Aug 22, 2026. Open the evidence source, then compare an exact matching configuration below.

Model-level provider comparison

Veo 3.1 price ranking status

Reviewed scopes, no current winner

Current answer: No current cheapest provider is published. The reviewed scopes do not have enough fresh, like-for-like offers to name a winner.

Provider routes with evidence
3
Accepted observations
7
Billing meters
source request, video second
Latest accepted check
Aug 22, 2026

Veo 3.1 Fast 720p API pricing without audio

Veo 3.1 Fast 720p, no-audio price

Not currently rankable
Reviewed comparison scope
Veo 3.1 Fast · text to video · 720p · no audio · global route · USD per generated video second
Publication gate
At least 3 unique providers with accepted, fresh, reviewed evidence

Why there is no winner

Ranking withheld: 0 of 3 required providers have fresh, matching evidence.

The Kie.ai offer is billed per fixed eight-second request with audio, so it is excluded. Google Vertex AI and fal remain below the three-provider publication gate.

Uncollapsed source records

All accepted offer evidence

These rows remain separate until their offered model ID, route, meter, tier, resolution, duration, audio, and region are proven comparable.

Veo 3.1 provider offers · exact configuration scope
ProviderModelConfigurationRecorded priceEvidence
Google Vertex AIofficialVeo 3.1text-to-video · fast · 720p · audio$0.1 / video secondstaleProvider sourceChecked Aug 22, 2026
Google Vertex AIofficialVeo 3.1text-to-video · fast · 720p · no audio$0.08 / video secondstaleProvider sourceChecked Aug 22, 2026
Kie.aiaggregatorVeo 3.1text-to-video · fast · 720p · 8s · audio$0.3 / source requeststaleProvider sourceChecked Aug 22, 2026
fal.aiaggregatorVeo 3.1text-to-video · fast · 720p · audio$0.15 / video secondstaleProvider sourceChecked Aug 22, 2026
fal.aiaggregatorVeo 3.1text-to-video · fast · 720p · no audio$0.1 / video secondstaleProvider sourceChecked Aug 22, 2026
fal.aiaggregatorVeo 3.1text-to-video · standard · 720p · audio$0.4 / video secondstaleProvider sourceChecked Aug 22, 2026
fal.aiaggregatorVeo 3.1text-to-video · standard · 720p · no audio$0.2 / video secondstaleProvider sourceChecked Aug 22, 2026

Checked evidence, not a ranking: fresh rows were checked against the linked first-party source on the shown date. APIDir does not name a cheapest provider unless exact configurations and units match. Recheck before purchasing.

Developer resources

Provider documentation and pricing links

Compare integration documentation beside the exact first-party source used for each accepted observation.

Provider documentation, pricing, and accepted evidence for this model
ProviderChannelDeveloper resourcesAccepted evidence
fal.aiaggregatorDocumentationPricing page4 observationsEvidence source 1
Google Vertex AIofficialDocumentationPricing page2 observationsEvidence source 1
Kie.aiaggregatorDocumentationPricing page1 observationEvidence source 1

Decision guide

How to compare Veo 3.1 API providers

Veo 3.1 is available through first-party cloud access and hosted provider channels. Those channels may expose different route names, fixed-duration requests, per-second meters, fast tiers, audio defaults, and operational limits. APIDir preserves the channel and configuration so a hosted quote is never presented as Google's direct price.

Choose the output configuration first, then compare providers. A useful test holds mode, tier, resolution, duration, and audio constant and measures total completed-work cost. Documentation quality, quota controls, region availability, retry handling, storage, and support can matter more than a small difference in the generation meter.

What changes Veo 3.1 API cost

  • Fast versus standard tier, generated duration, resolution, and audio
  • Per-second versus fixed-request billing and any minimum duration
  • Failed generations, retry policy, storage, egress, and post-production steps

Integration checks before production

  • Confirm the exact Veo 3.1 endpoint and region before load testing
  • Keep audio and duration explicit in every request and cost log
  • Treat submission retries differently from idempotent status polling

Workloads this comparison can inform

Narrative clips with sound

Compare only audio-enabled offers at the same duration and resolution.

Silent product loops

Exclude audio routes and fixed eight-second products when the workload needs shorter clips.

Cloud-governed workloads

A direct cloud route may be preferable when region, IAM, billing consolidation, or enterprise controls dominate.

How to read the price result

The table intentionally shows both direct and hosted evidence. It does not merge a fixed request with a per-second offer, and it does not call one channel cheapest until three exact configurations pass review.

Related model price comparisons

Use this evidence safely

A recorded price is not a complete production quote. Open the source, reproduce the exact configuration, and include retries, failed work, storage, egress, support, rate limits, and downstream processing in total cost.

Questions developers ask

What makes two Veo offers comparable?

The model version, generation mode, tier, resolution, duration, audio setting, region, and billing unit must match.

Does APIDir name a cheapest provider on this page?

Only when at least three explicitly reviewed provider offers are fresh, publication-permitted, and within the same published comparison scope. Stale or mismatched evidence cannot support that claim.

How should I confirm a budget?

Open the linked provider source, verify the configuration, then calculate your own successful and failed workload volume.

APIDir Delta · controlled rollout

Join the source-linked pricing update waitlist.

Confirm your address to join the waitlist. Editorial delivery starts only after sender, suppression, and evidence checks are active.