Gemini Omni 1.2 Flash vs Higgsfield API

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.

Higgsfield API 80

Hosted reading. status.higgsfield.ai now shows Models API, Webhooks and Developer Console components with 90-day uptime bars (20). Its incident and maintenance feed is empty and its history pages redirect to the front page, so the page has never posted an incident, which this run reads at 20, not as a clean record (20 of 30). Concurrency limits are published with numbers, 2 for a new account and 10, 20 and 40 at $25, $100 and $1,000 of funds added in 28 days, and the queue limit is a stated multiple of concurrency (15). Since late October, requests over the concurrency limit are queued, and a full queue answers 429 with Retry-After, a retryable flag and account_queue_full. The docs give backoff with jitter, a retry table and idempotency keys for submissions (15). The API terms say self-serve customers get no uptime commitment and the docs offer SLAs only in an enterprise agreement, with none published (0). No beta or preview label on the API (10). 20 + 20 + 15 + 15 + 0 + 10 = 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.

Higgsfield API 81

Submissions return a small JSON handle, results are URLs, and webhooks replace polling (20 of 25). Resolution, duration and aspect ratio set output size per model. No endpoint to list requests was found in the docs (10 of 20). The error page says which statuses to retry, and the limit now arrives as a 429 with Retry-After, code, retryable and retry_after_seconds, and expired or disabled keys as 403 with a code. Other errors are message strings the docs warn against parsing (16 of 20). Idempotency-Key on every generation endpoint, with a 422 on a reused key with different parameters, plus cancel for queued requests (20). Few required parameters, sensible defaults, and official Python and TypeScript SDKs (15). 20 + 10 + 16 + 20 + 15 = 81.

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.

Higgsfield API 65

The docs sitemap shows pages changed on 24 October 2026, when the queueing, retention, key and webhook signing pages were rewritten (30). In the 90 days from 4 August, the TypeScript SDK has four tags, 0.2.3 to 0.2.6 (17 and 18 September 2026), counted half as SDK tags, and no changelog exists. The 8 October date for higgsfield-client 0.2.0 came from PyPI's JSON path, which pypi.org's robots.txt disallows, and is struck (10 of 20). No public changelog. Support is by Discord and email, and the SDK repositories' open issues couldn't be read (6 of 15 for a closed service). Official Python and TypeScript SDKs are current (15). The TypeScript repository has a publish workflow and moved to Node 22 on 22 October, with critical dependency fixes merged on 29 October and not yet released. The Python one has tests but no CI workflow (4 of 10). 30 + 10 + 6 + 15 + 4 = 65.

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.

Higgsfield API 64

Closed service with API terms dated 2 September 2026 that are specific on licence, resale and outputs. SDKs are MIT and Apache-2.0 (15). The API terms state training on inputs and outputs by default with a workspace opt-out, request records kept while the account is active, media kept at least seven days and zero retention only by enterprise addendum, and the privacy policy of 31 October 2026 agrees on training. The docs now let a request set its own retention down to one hour and delete a finished request, but the docs' opt-out page says it covers outputs only, against the terms' inputs and outputs. The DPA the terms incorporate was not found (20 of 30). The status page carries a dated notice that platform.higgsfield.ai stops serving the API by 31 October 2026, the terms promise efforts to announce model removals, and legacy endpoints are labelled, but there is no changelog (10 of 20). Partner models are named by vendor in the catalogue. The subprocessor list is said to sit in the trust centre, which was unread, and no data locations were found (5 of 20). 15 + 20 + 10 + 5 = 50.