fal video models vs Gemini Omni 1.2 Flash

fal video models 77

Graded as a hosted service on the queue API. Instatus page at status.fal.ai with components for Model API, Serverless API, Official Models and the dashboards, and monthly uptime figures (20). The notice history, re-read on 1 November 2026, has two notices in the 90 days from 3 August, a 30-minute major outage of synchronous calls to fal.run on 4 September (the queue wasn't named, so partial) and 18 minutes of degraded performance on 29 September, and none in October (20). Concurrency is published, 2 for a new account rising to 40 self-serve with paid invoices over four weeks, and queued requests are never rejected (15). A 429 carries type concurrent_requests_limit and X-Fal-needs-retry: 1, the docs give backoff of 1, 2, 4 and 8 seconds, the queue retries 503, 504 and connection errors up to 10 times, and backup domains are documented. There is no idempotency key, and one page says concurrency requeues have no maximum while another says 10 (12). The enterprise page mentions SLA guarantees but no SLA document is published (0). The queue API is generally available (10).

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.

fal video models 81

Graded on the queue API, with the hosted MCP server noted. Results are small JSON with a file URL, and a model's llms.txt is 6 to 8 KB loaded on demand. The MCP server has 11 tools with schema and pricing lookups (20). The catalogue API takes category, limit and a cursor, queue status reports position, webhooks replace polling, and most models take duration and resolution, though names and types differ (18). Errors carry a machine-readable error_type, the same value in X-Fal-Error-Type, and guidance on which to retry (18). No idempotency key. Server-side retries, X-Fal-No-Retry, a cancel endpoint and no charge for 5xx failures reduce the cost of a failed call, but a repeated submit is a second billable job, and the MCP docs don't mention readOnlyHint or destructiveHint (10). Few required parameters, and official Python and JavaScript clients plus Swift, Kotlin and Dart (15).

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.

fal video models 73

Keys take one of seven permission presets (API, SERVERLESS, DEPLOY, COMPUTE, BILLING, READONLY, FULL) or a custom permission list, can be limited to named models and can expire after 1 hour to 1 year, since 9 October 2026. Legacy ADMIN and API keys still work. The MCP relay uses OAuth with browser sign-in, and its scopes aren't documented (30). A READONLY preset grants no write access, and model limits narrow a key further. The MCP docs state that the server has no server-side approval gate before a paid generation (15). Returns generated media and fal's own catalogue text (10). Request payloads are kept 30 days in the dashboard history, and usage and analytics APIs report per-request spend (10). https://fal.ai/.well-known/security.txt returned 404 on 1 November 2026 and no disclosure policy or bug bounty was found. The enterprise page claims SOC 2 certification, the DPA of 31 July 2026 has a data security exhibit, and the trust centre at trust.fal.ai renders only in a browser, so the report and its scope were unread, per the 8 October check (8).

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.

fal video models 89

An OpenAPI 3.1 document for the queue API and one for the platform APIs, and a per-endpoint OpenAPI 3.1 document from the catalogue API with expand=openapi-3.0, read for fal-ai/kling-video/v3/pro/text-to-video on 1 November 2026 (25). The 8 October reading of per-endpoint documents on fal.ai's ?endpoint_id= path is struck, because fal.ai's robots.txt disallows that query. A docs llms.txt, Markdown twins of docs pages and an llms.txt per model with schema, defaults and price (10). Model pages state what each model does but rarely when not to use it, and the Seedance 2.5 catalogue text says up to 720p while its schema lists 1080p (12). Inputs are typed with enums, ranges and defaults, but duration is a string enum on Kling, a string with a unit on Veo 3.1 and an integer on Wan 3.0, and Kling's rule that one of prompt or multi_prompt is needed sits in prose with a required example of {} (13). Examples in cURL, Python and JavaScript on every model, a model error reference with typed errors such as content_policy_violation and video_duration_too_long, and a request error reference with 13 types (14). Versioned endpoint IDs and a dated public changelog (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.

fal video models 64

Closed platform with published terms (8 September 2026) and API Services supplemental terms. The clients are MIT and the catalogue marks each model's license_type. The terms warrant nothing about rights in output, and a clause bars scripts that integrate with the services without written authorisation, which sits oddly with an API product (13). Data handling is documented and mostly agrees. Request payloads are kept 30 days with an opt-out header and a delete API, the API Services terms say client content isn't used to train or develop fal's products except on models marked Pending Enterprise Ready, and the privacy policy of 22 July 2026 deletes account data 30 days after closure. The terms still let fal use usage data to develop AI models, and content sent to a third-party model goes to that third party (22). Model pages now carry dated deprecation notices, Veo 3.1 and its sub-endpoints on 17 November 2026, Luma Ray 2 on 25 October with a named replacement, and the key docs say presets can be refined. But 31 of 152 text-to-video endpoints are marked deprecated in the catalogue, most without a date, and there is no written policy or changelog entry (12). The DPA names a subprocessor list at trust.fal.ai/subprocessors with 15 days' notice of changes, but that page renders only in a browser, and the privacy policy says processing is in the United States and other countries (10).

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.