Face swap API: quality has no default, unlike avatar videos
Avatar videos default to plus when quality is omitted. Sume's Beta face swap has no default: quality is required and takes standard, plus or max.

On Sume's Beta face swap endpoint, quality is required and there is no default: send standard, plus or max. That differs from avatar videos and avatar video previews, where omitting quality falls back to plus. If you copy an avatar request body over to face swap, add the field.
Where is quality required and where does it default?
The face swap docs list avatar_handle, video_url and quality as required and state "There is no omit default on this endpoint." The avatar video docs say plus is the default when omitted.
| Endpoint | quality field | If omitted |
|---|---|---|
| Face swap (Beta) | Required: standard, plus, max | No default; the request needs it |
| Avatar video | Optional: standard, plus, max | plus |
| Avatar video preview | Optional: standard, plus, max | plus |
What do the three values mean?
For avatar videos the docs describe standard as the fastest Sume execution path, plus as the balanced one and max as the highest quality tier with slower turnaround. The face swap page names the same three values but does not restate what each does, so this post only claims the avatar-video descriptions for avatar videos.
What does the request look like?
Set quality explicitly in the body of POST /v1/models/sume/avatar-face-swap/v1.0/runs.
{
"avatar_handle": "reference_presenter",
"video_url": "https://example.com/source-clip.mp4",
"quality": "standard"
}What happens if I leave it out?
The docs do not print the error text for a missing quality, so read the response body of a test request for the exact code rather than assuming one. Because the endpoint is Beta, check the page again before you depend on this behavior.
Sources
Related posts
More in Developers
- 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.
- frame_images plus input_references in one request: which wins?
When a Sume video request carries both frame_images and input_references, frame_images wins and the job runs as image-to-video. What that means for references.
- Gemini CLI MCP timeout default vs Sume's 55-second jobs_wait
Gemini CLI's MCP timeout defaults to 600,000 ms. Sume's jobs_wait holds at most 55 seconds per call: repeat it on wait_slice_expired, never resubmit.
- Gemini CLI trust: true on a Sume MCP server: what it skips
Gemini CLI's trust setting bypasses every tool confirmation dialog. What that means for Sume's paid tools, and which Sume gates still apply.
Written by Sume