Gemini Omni 1.2 Flash vs PixVerse API

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.

PixVerse API 42

Model reading. The changelog's latest entry is the One-click VibeMV API on 24 September 2026, per the 1 October check, not re-read on 10 November (PixVerse's Terms of Service bar robots on its websites). That is 47 days before 10 November 2026, within 90 (20, was 30, cause time). PixVerse's official CLI released v1.4.6 to v1.4.16 from 24 September to 29 October 2026, but it runs on the web app's subscription credits and app models, not the Platform API, so it doesn't count. Legacy models from V3.5 to V5.6 stay callable, and no removals were found (10). Dated changelog and support through the platform (12). No official SDK. The stdio MCP package's last version is 0.2.2, committed on 21 October 2025, with a v2.0.0 README commit on 22 October 2025 and nothing since (0). Nothing current to assess for package health (0). 20 + 10 + 12 + 0 + 0 = 42.

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.

PixVerse API 46

Closed models under platform terms (updated 4 September 2026, re-read on 5 November) with MOTIVAI PRIVATE LIMITED, with AIVORA PTE. LTD. named as an affiliate and as the operator in the general Terms of Service (29 October 2026). The platform terms give API users the rights in generated video and allow commercial use (15). The terms don't address training on inputs or outputs and give no retention period, only that data may be deleted when service ends. We didn't read the privacy policy against them (5). No deprecation policy, but legacy models are labelled, per the 1 October check (5). No subprocessor list or data locations found (0). 15 + 5 + 5 + 0 = 25.

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.

PixVerse API 28

Model reading of the checklist (credential, training, retention, operator visibility, programme). One API key in an API-KEY header (20). The platform terms (still dated 4 September 2026 on 5 November) don't say whether inputs or outputs train models (0). No retention period or deletion call found (0). A usage deduction query API since 18 August 2026 shows what each job cost, no audit log (8). No security.txt, bug bounty or certification found (0). The docs and security.txt per the 30 September check, not re-read on 10 November. 20 + 0 + 0 + 8 + 0 = 28.

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.

PixVerse API 70

Small JSON responses with a video id, plus webhooks so an agent needn't poll (25). Duration, quality and aspect ratio set output size. No task list endpoint found (10). Numeric status and error codes are documented but cryptic (12). Every submit needs a fresh UUID in Ai-trace-id, and reusing one returns the earlier job instead of creating a new one. That works as an idempotency key, though an agent that reuses an id by mistake gets the old video back (20). Required trace header, no official SDK. A CLI and an MCP server exist (3). Per the 30 September and 1 October checks, not re-read on 10 November (PixVerse's Terms of Service bar robots and page-scrapes on its websites). 25 + 10 + 12 + 20 + 3 = 70.

Gemini Omni 1.2 Flash 30

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. No machine payment protocol (0). The pricing page lists $1.50 per million input tokens, $12 per million video output tokens and effective rates of $0.023 a second at 360p, about $0.07 at 720p, $0.104 at 1080p and $0.209 at 4K, without a login (20). No free tier (0). A Google account and AI Studio key, or a Cloud project, come first (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

PixVerse API 15

No x402, MPP or L402 (0). Credits per second are public for every model, and the docs peg $1 at five 5 second V6 720p clips, but plan prices sit on a billing page that needs JavaScript, so the dollar price of a credit isn't stated outright (10). A Free API plan with 3 concurrent jobs is listed, but the docs don't say whether it includes credits (0). A person signs up on the platform (0). Per the 30 September and 1 October checks, not re-read on 10 November (PixVerse's Terms of Service bar robots and page-scrapes on its websites). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Gemini Omni 1.2 Flash 69

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. Called through the Interactions API, which the platform's Discovery document doesn't type; the SDK's generated Interactions types list the model (10 of 25). llms.txt with Markdown twins (10). The Omni guide, read on 11 November, covers Omni 1.1 Flash on the same API and lists what isn't supported (system instructions, temperature, negative prompts, audio references, YouTube sources) and the regional limits; it doesn't name 1.2 (16 of 20). Aspect ratio (16:9 or 9:16), resolution (360p, 720p, 1080p, 4k) and delivery are enumerated; length is set in the prompt, not a field (10 of 15). REST and SDK examples; a failed generation sets the file state to FAILED, and other error codes aren't documented beyond the platform's page (8 of 15). Dated SDK and platform changelogs (15). 10 + 10 + 16 + 10 + 8 + 15 = 69.

PixVerse API 58

No OpenAPI file published (0). llms.txt on the platform docs (10). Each endpoint page says what the operation does, and the model tables say which models support it. Older model tables still sit beside current ones (12). Typed parameters with fixed values for model, quality, duration and aspect ratio (11). Examples on each endpoint. Results use numeric status codes (1 done, 5 generating, 7 moderation failure, 8 failed) that an agent has to look up (10). A dated changelog that adds models and endpoints every few weeks (15). Per the 30 September and 1 October checks, not re-read on 10 November (PixVerse's Terms of Service bar robots and page-scrapes on its websites). 0 + 10 + 12 + 11 + 10 + 15 = 58.