Gemini Omni 1.2 Flash vs Google Veo

Gemini Omni 1.2 Flash 45

Model reading for gemini-omni-1.2-flash on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Status page at aistudio.google.com/status with no readable components or history (10 of 20) and no readable incident record (5 of 30). Platform rate-limit tiers; the public rate-limit page has no Omni 1.2 row (5 of 15). Backoff guidance for 429 and 503 and SDK retries (15). No SLA read for the Gemini API route, and the Omni guide says provisioned throughput isn't supported there; Google's post puts it on Google Cloud (0). Google's post of 5 November says generally available, and the SDK commit marks the model GA (10). 10 + 5 + 5 + 15 + 0 + 10 = 45.

Google Veo 87

Graded on Vertex AI (Gemini Enterprise Agent Platform), the route the listing names that still serves Veo, since every Veo model on the Gemini API shut down by 22 October 2026. Google Cloud's status dashboard lists Veo on Agent Platform as its own product with a history page (20). That page reads 'No incidents reported' on 4 November 2026, and the dashboard posts incidents for other products, so a clean record (30). The 1 October readings of the AI Studio page and a third-party monitor are dropped (the monitor is a barred copy of a status page). The Veo 3.1 model page publishes 50 regional online prediction requests a minute per base model in us-central1 (15). The Agent Platform error 429 page gives truncated exponential backoff, quota increase requests and traffic smoothing. A Veo request starts a billed generation job and no idempotency key is documented, so backoff guidance without keys, as runway and fal-video read their video job APIs (12). The Gemini online inference SLA, last modified 30 June 2026 and re-read on 4 November, covers only generateContent and streamGenerateContent, not the predictLongRunning call Veo uses (0). veo-3.1-generate-001 and veo-3.1-fast-generate-001 are GA, Lite is preview (10). 20 + 30 + 15 + 12 + 0 + 10 = 87.

Gemini Omni 1.2 Flash 50

Model reading for gemini-omni-1.2-flash on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Keys bound to a service account and restricted to the Gemini API, with no scopes and a token accepted in the URL (15 of 30, the platform's deduction). The pricing page, read on 11 November, lists no free tier for Omni 1.2 Flash, and paid-tier content isn't used to improve Google's products (15 of 20). Retention of generated videos isn't stated in the guide (5 of 15). Request logs described for Generate Content, not confirmed for Interactions video calls (10 of 15). security.txt and a reward programme, no certification naming the API (5 of 20). Outputs carry a SynthID watermark, and uploads of minors and some recognisable people are refused in the EEA, Switzerland and the UK. 15 + 15 + 5 + 10 + 5 = 50.

Google Veo 80

Model reading of the checklist (credential, training, retention, operator visibility, programme), on the Vertex AI route. Vertex AI uses Google Cloud OAuth with IAM roles (30), less 10 because the API reads a token from the URL. Google's OAuth 2.0 web-server guide (last updated 30 October 2026) says to call a Google API with 'either an access_token query parameter or an Authorization HTTP header Bearer value', and the Vertex AI v1 discovery document (revision 20261028, as published in Google's google-api-python-client repository) lists access_token, oauth_token and key as query parameters, the deduction Google APIs took on 17 October and 1 November (20 of 30). Prompts and responses on paid services aren't used to improve products, per the 1 October reading of the terms, not re-read on 4 November (20). Retention for Veo jobs on Vertex AI wasn't read on 4 November. The 1 October reading (videos kept 2 days, abuse-log period not stated, no deletion call) holds the line (5 of 15). Data Access audit logs record reads and writes to model endpoints once enabled, per the Agent Platform page last updated 3 November 2026, as the Gemini Embedding listing credits Cloud Audit Logs on Vertex AI (15). security.txt valid to 2030 with Google's vulnerability reward programme, per the 1 October check (10). ISO/IEC 27001 scope, re-read on 4 November, names Generative AI on Gemini Enterprise Agent Platform, the route graded (10). 20 + 20 + 5 + 15 + 20 = 80.

Gemini Omni 1.2 Flash 54

Read on the lines the Veo listing used for video models. Model reading for gemini-omni-1.2-flash on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Per the Omni guide (written for 1.1 on the same API), the video comes back in the response, inline as base64 or as a Google-hosted file to poll until ACTIVE with delivery uri for outputs over 4 MB (12 of 15). No callback (0 of 10). Resolution, aspect ratio and delivery control output size, and edits run turn by turn through previous_interaction_id without regenerating from scratch (10). No list of past jobs found (0 of 10). Standard Google error statuses on the platform, with FAILED as the only Omni-specific state (12 of 14). No idempotency key, and whether failed generations are billed isn't stated (5 of 20). Only model and input are required, with 720p and 16:9 as defaults, and SDKs in five languages plus the CLI (15). 12 + 0 + 10 + 0 + 12 + 5 + 15 = 54.

Google Veo 64

Per the 1 October check, read from the Veo guide, which uses the same request on both routes. The create call returns a small operation object to poll (15). No callback, and the docs say poll every 10 seconds (0 of 10). Resolution, duration and aspect ratio control output size (10). No list of past jobs (0 of 10). Standard Google error statuses such as INVALID_ARGUMENT and RESOURCE_EXHAUSTED that an agent can branch on (14). No idempotency key, and the 1 October reading found only generated videos billed (10). Only the prompt is required, defaults are 720p, 16:9 and 8 seconds, and official SDKs exist for Python, JavaScript, Go and Java (15). Vertex AI's own API reference for Veo wasn't read on 4 November.

Gemini Omni 1.2 Flash 83

Model reading for gemini-omni-1.2-flash on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Released and generally available on 5 November 2026; the SDKs added it to the Interactions model list on 10 November (30). Deprecations with earliest dates and no stated minimum notice (4 of 12). Churn in Google's video line: every Veo model on the Gemini API shut down by 22 October, and from 3 December 2026 requests to Omni 1.1 Flash are routed to 1.2 Flash and billed at its rates, four weeks after this release (4 of 8). Dated SDK and platform changelogs (15). SDK replies not sampled (5 of 10). Current SDKs in five languages (15). Runtimes stated (10). 30 + 4 + 4 + 15 + 5 + 15 + 10 = 83.

Google Veo 77

Model reading. The google-genai SDK, which runs Veo on Vertex AI, tagged 2.34.0 on 29 October 2026 after weekly tags through October (30). Heavy churn. Veo 2.0 and 3.0 shut down on the Gemini API on 30 June 2026 and all three Veo 3.1 previews on 22 October 2026, with release and shutdown dates published but no notice period stated for previews, and the GA Veo 3.1 models on Vertex AI carry a retirement date of 'November 17, 2026 or later' (10). Dated changelog with entries through 2 November 2026, and a developer forum (12). Current official SDKs (15). SDK repositories on GitHub under googleapis with CI (10). An unreleased python-genai commit of 30 October disables generate_videos for the Gemini API client.

Gemini Omni 1.2 Flash 72

Model reading for gemini-omni-1.2-flash on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Closed service with clear terms, SDKs Apache-2.0 (15). Paid only, so content isn't used to improve products; video retention isn't stated (20 of 30). Deprecations table and a dated routing notice for Omni 1.1 Flash (15 of 20). Data may be processed anywhere Google has facilities on the Gemini API route; no subprocessor list checked (5 of 20). SynthID watermarking is disclosed, and Google names the cases it still handles poorly. 15 + 20 + 15 + 5 = 55.

Google Veo 77

Closed models under Google's terms, which say Google won't claim ownership of generated content. SDKs are Apache 2.0 (15). The terms state the paid and unpaid data use (10). Video retention is stated (2 days on the Gemini API), the abuse-log period isn't (5). The terms, pricing page and Veo guide agree, and we didn't read the DPA (5), per the 1 October check. The deprecations page gives release and shutdown dates for every Gemini API Veo ID and names replacements, and the Agent Platform model page dates each GA model's retirement (20). The Agent Platform model page names us-central1 as the only region and lists data residency, CMEK and VPC-SC controls. We didn't check subprocessors (10).