Guides
Sume guides: the API, Formats, agents, models, media tools and pricing, each answer dated and sourced.
Submitting 20 avatar videos at once: what each Sume plan accepts
Sume accepts as many paid jobs as concurrency plus queue allows: 6 on Free, 24 on Pro, 48 on Startup, 120 on Scale. Past that a submit returns 429 queue_full.
Facebook Feed video ad 4:5 at 1440x1800: render it with Timeline
Meta's Facebook Feed video spec lists 4:5 at 1440 x 1800. No Sume video model lists 4:5, but a Timeline 1.0 render can output 1440x1800. Steps and limits.
Instagram Feed video ad 9:16 at 1080x1920: size and 1% tolerance
Meta lists 9:16 at 1080 x 1920 for Instagram Feed video ads with a 1% tolerance. Sume 9:16 settings and a Timeline output that fit, with the arithmetic.
Facebook Feed video ad file type: MP4, MOV or GIF from Sume?
Meta lists MP4, MOV or GIF for Facebook Feed video ads. Sume Timeline, video-filter and video-trim each return an MP4, so MP4 is the format to plan around.
Facebook Feed video captions: burn them onto a clip with no speech
Meta marks captions optional but recommended for Facebook Feed video ads. Sume's caption job fails on a silent clip unless you pass your own cues.
Shopify product video limit: 1 GB, 10 minutes, and Sume clip lengths
Shopify.dev lists 1 GB and 10 minutes as the product video maximum. Sume clips run 2 to 30 seconds per request; Timeline can join up to 1800 seconds.
Shopify product video at 3840x2160: which Sume model lists 4K?
Shopify.dev caps product video at 3840x2160 (UHD/4K). Sume lists a 4K tier on gemini-omni-flash-1.1 for 3 to 10 seconds in 16:9 or 9:16. Request and checks.
Shopify's 1,000 videos per store per week: plan a Sume batch
Shopify.dev says apps can create up to 1,000 videos per store each week. Count one job per video, one Idempotency-Key per SKU, and watch Sume's queue.
Shopify image max 4472 x 4472 px: what Sume's image API outputs
Shopify.dev caps product images at 20 MB and 4472 x 4472 px. gpt-image-2.5 on Sume stops at a 3840 edge and 8,294,400 pixels, so it sits under the pixel cap.
Shopify product video formats MP4, MOV, WEBM: what Sume returns
Shopify.dev lists MP4, MOV and WEBM for product videos. Sume Timeline, video filter and video trim return an MP4, which is one of the three formats listed.
Google Merchant Center image size: 500x500 minimum, 1500x1500 advised
Google lists at least 500 x 500 pixels for product images and recommends 1500x1500 or above. Sume's gpt-image-2.5 can output 1536x1536, which meets the advice.
Google Merchant Center image rules: no watermark, price or CTA overlay
Google's image page bars promotional elements or content that covers the product. How to ask Sume's image API for a clean product image, and what to check.
Google Merchant apparel images worn by people: reference-guided images
Google asks for apparel product images worn by people. gpt-image-2.5 on Sume takes up to 16 reference images, so a garment photo can guide the image.
Google Merchant Center 16 MB and 64 megapixel image limits vs Sume
Google lists no image over 64 megapixels and no file over 16 MB. Sume's gpt-image-2.5 caps output at 8,294,400 pixels; file size is not published.
Google Merchant Center image formats: which Sume output_format fits
Google lists JPEG, WebP, PNG, GIF, BMP and TIFF for product images. Sume's Image API lists png, jpeg, webp and svg; svg is not on Google's list.
Pull product stills from a video with the video-frames API
Video frames returns jpeg or png stills from a Sume-hosted clip at set seconds. Google lists 500 x 500 minimum, so extract from the clip before captions.
Turn product photos into a silent video with Timeline static holds
Timeline 1.0 treats a still as a static hold, so product photos become a silent video with fades. Shopify lists MP4 up to 10 minutes; here is the request.
Cut one product video into feed cutdowns with the video-trim API
Video trim cuts a [start, end) range from a Sume-hosted clip into a new MP4 at $0.02 per job. Meta's Facebook Feed page lists 1 second to 241 minutes of length.
Paper edit by API: build a rough cut from transcript lines
Premiere 26.5 added Paper Edit. To do the same by API, transcribe with sentence segments, pick the lines you keep, then render those ranges as a Timeline.
Search footage for a spoken phrase with an API: words with timing
DaVinci Resolve 21 lists IntelliSearch. To find a spoken phrase in a clip by API, transcribe with video inspect and search words[] in your own code.
Remove filler words from a video by API: cut at word timestamps
Descript's API lists Remove Filler Words as an Underlord edit. the Sume docs list no such op; here is how to cut um and uh yourself from words[] and a Timeline.
Reframe a video around the speaker by API: what a crop can do
Descript's Center Active Speaker (Beta) follows whoever talks. Sume's video filter crop is one fixed rectangle per clip, so cut per speaker and crop each part.
Get the rendered MP4 back from a video editing API job
Descript's API lists no rendered file download without publishing. In Sume, a finished timeline_render job result carries video_url; here is the poll flow.
MCP tools for editing video: the hosted Sume list, trim to timeline
Descript and Runway both ship MCP servers. The hosted Sume MCP exposes video_trim, video_filter, audio_detach, video_frames_create and the timeline tools.
Join voiceover clips inside one timeline render with audio.parts
Timeline 1.0 takes up to 20 gapless audio.parts slices with source_in and duration. Skip the timeline-audio job when the join is only for one render.
Timeline render warnings: padded or looped short sources explained
A Timeline 1.0 slot longer than its source renders with a soft warning, not a failure, and /plan cannot predict it. Read warnings[] and probe clips first.
Timeline 1.0 limits: 200 slots, 1800 s, 20 audio parts, 8 fades
The numbers that cap one Timeline 1.0 render: 1 to 200 video slots, 1 to 1800 s of audio, 20 audio parts, 12-slot single strategy and 8 chained fades.
Extract audio from a long video: the 900 s output cap and range
Audio detach takes sources up to 1800 s but outputs at most 900 s. For a longer track pass range and detach in two calls. Errors included.
video-filter order of operations: ops first, then filtergraph
In Sume video-filter, ops[] (dim, crop; max 8) run before the filtergraph, which has its own 2048-character and 32-filter caps. Order matters for a crop.
Trim an H.265 or AV1 clip by API: which codec comes out?
DaVinci Resolve 21 lists H.265, MV-HEVC and AV1. Sume's exact trim re-encodes to libx264 yuv420p; keyframe trim copies the stream. Input support is not listed.
Keep the source's channels and sample rate when extracting audio
Adobe lists Match Source audio channels and sample rate in Premiere 26.5. Sume audio-detach keeps both by default: channels source, sample_rate omitted, wav.
Editing upload limits: Descript's GB tiers vs Sume's seconds caps
Descript lists per-file size caps by plan (1, 10, 20, 50 GB). Sume's media routes cap by clip duration instead: 300 s or 1800 s in, up to 900 s out.
Rough cut from a script by API: one scene per Timeline slot
Descript Quick Design splits a script into moments with changing visuals. With Sume you map each scene to a Timeline video slot over a voiceover spine yourself.
Trim and conform a clip to 1080x1920 at 30 fps in one call
video-trim takes an optional output {width, height, fps} that conforms on the way out, exact precision only. Width and height 256-2160, fps 24, 25, 30 or 60.
GPT Image 2.5 1080x1350: why the size fails and what to send
1080x1350 breaks GPT Image 2.5's multiple-of-16 size rule. 1080 is not a multiple of 16. 1088x1360 (exact 4:5) meets the listed rules. Per OpenAI and Sume docs.
GPT Image 2.5 mask edit: does the mask need an alpha channel?
OpenAI's API says the mask must contain an alpha channel. Sume's docs list a public HTTPS mask_url for GPT Image 2.5 edits but state no mask format rule.
GPT Image 2.5 moderation low: can you send it through Sume?
OpenAI lists a moderation parameter (auto or low) for GPT Image 2.5. Sume's request table does not list it, so check the catalog before sending it.
GPT Image 2.5 cached input price: does Sume pass it on?
OpenAI lists cached input at $1.25 text and $2 image per million tokens for Sunburst. Sume's docs give estimates and reserved cost, not a cache discount.
FLUX image URL expires after 10 minutes: what Sume returns
Black Forest Labs says generated FLUX image URLs expire after 10 minutes. Sume returns Sume-hosted signed URLs; here is how to fetch and keep the file.
Image 1.0 input_urls, n and format: deprecated names to replace
Sume's Image 1.0 still accepts input_urls, n and format, but prefers image_urls, num_images and output_format. What each maps to and their limits.
How many reference images? 10 on Image 1.0, 16 on GPT Image 2.5
Image 1.0 image_urls takes 1 to 10 public HTTPS URLs; ChatGPT Image 2.5 takes up to 16 references. Text-only models reject references.
gpt-image-2 or openai/gpt-image-2? Model ids on Sume's Image API
Sume accepts bare Image Router ids such as gpt-image-2 and nano-banana-2 as aliases for openai/gpt-image-2 style ids. The catalog lists org/slug ids.
Image 1.0: text, reference or masked edit - which fields to send
Image 1.0 uses prompt only for text-to-image, prompt plus image_urls for edits or references, and adds mask_image_url for masked edits. Fields and URL rules.
Token bucket vs fixed window: what a reset header means
Anthropic says its limits replenish continuously; Sume's docs call ratelimit-reset the seconds until the window resets. How to pace a client for each.
Gemini rate limits: per project, not per API key. And Sume?
Google says Gemini rate limits apply per project, not per API key, so a second key adds nothing. What Sume's docs say about plan limits and how to read them.
Gemini tiers unlock by spend and days. Sume limits follow the plan
Gemini upgrades a project after spend and elapsed days. Sume sets request and concurrency limits by plan, and a prepaid top-up does not raise concurrency.
Create vs read rate limits: Managed Agents 300/1,200, Sume plans
Anthropic's Managed Agents limit creates and reads separately. Sume splits its per-minute budget the same way by plan, so polling cannot starve submits.
AI Act Article 50 in force: what to log per generated file
Article 50 applies from 2 August 2026. Keep a per-file record of job id, request id and artifact URL from Sume, and know what the docs leave unsaid on marking.