Gemini Omni Flash 1.1 on Sume: spec sheet and billing in one page
Everything that ships for gemini-omni-flash-1.1 on Sume: 3 to 10 seconds, four resolutions, two ratios, always-on audio, reference limits, edit mode, billing.
gemini-omni-flash-1.1 on Sume makes 3 to 10 second clips at 360p, 720p, 1080p or 4K in 16:9 or 9:16, with synced audio always on, from $0.1125 to $3.75 a clip. One catalog id, and Sume routes the request by its shape.
Spec
| Item | Value |
|---|---|
| Model id | gemini-omni-flash-1.1 |
| Duration | 3-10 s, whole seconds |
| Resolution | 360p, 720p, 1080p, 4K |
| Aspect ratio | 16:9, 9:16 |
| Audio | Native, always on; generate_audio:false is rejected; no audio input |
| Text-to-video | prompt |
| Image-to-video | image_url, optional end_image_url (Video Router); frame_images on /v1/videos |
| Reference-to-video | up to 10 reference images, up to 3 reference videos of at most 3 s each |
| Edit mode | video_url; resolution optional, default 720p; no aspect_ratio or duration |
Billing
Sume bills provider list times 1.25 per output second, reserved at submit. Rates: 360p $0.0375/s, 720p $0.125/s, 1080p $0.1875/s, 4K $0.375/s. Google's pricing page lists the model's video output at $17.50 per 1M tokens, about $0.10 per second at 720p, with no free tier (read 2026-10-08); the Sume 720p rate is that times 1.25.
A shortfall returns 402 insufficient_credits. usage.cost on the finished job is the billable amount.
Request and flow
Submit, poll polling_url, download unsigned_urls[0], or set a callback_url (HTTPS) for a signed webhook.
curl -X POST https://api.sume.com/v1/videos \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"gemini-omni-flash-1.1","prompt":"A lighthouse beam sweeps over waves, gulls and wind","duration":6,"resolution":"1080p","aspect_ratio":"16:9"}'Sources
Related posts
More in Models
- Gemini Omni rate limit: Google lists none, Sume lists them
Google's rate-limit page has no Omni or Veo row. It lists per-project RPM, TPM and RPD plus spend caps. Sume publishes per-key limits and concurrency by plan.
- GLM-5.3 reasoning cannot be turned off: cap the Sume run instead
Z.ai says GLM-5.3 always reasons, with low, high and max levels. What that means for run time and for a spend cap on a Sume agent run.
- GLM 5.3 Fast or Flash: which one does Sume list?
Sume's agent model list has GLM 5.3 Flash, not GLM 5.3 Fast. What Z.ai's GLM-5.3 page says and what the API's model field accepts.
- Does Google keep Omni and Veo prompts for 55 days?
Google's Gemini API page says prompts, context and outputs are kept 55 days for abuse checks. Veo files last 2 days. How that differs from a Sume request.
Written by Sume