Higgsfield Genjutsu motion transfer, 17 s at 480p: $6.7575 on Sume
Sume's higgsfield-genjutsu appears only when its provider is configured. When listed, 17 s at 480p is about $6.7575 and 720p $14.4713; check your catalog first.

Sume's higgsfield-genjutsu model does motion transfer: one source video plus one to eight reference images, at 480p or 720p, for 4 to 30 seconds. It is in the Sume catalog only when its provider is configured, and the public catalog that I read on 2026-10-08 does not list it, so check GET /v1/videos/models before you plan around it. If your account does list it, 17 seconds at 480p works out to about $6.7575.
Where the figure comes from
The repository's price table for Genjutsu motion transfer holds a provider estimate of $0.318 per second at 480p and $0.681 per second at 720p, taken from an authenticated estimate on 2026-09-18. With Sume's 1.25 margin that is $0.3975 and $0.85125 per second. The Sume docs do not publish these numbers, and they apply only when the model is enabled, so treat them as a planning estimate and confirm with the quote your account returns.
| Resolution | Per second | 17-second source | Arithmetic |
|---|---|---|---|
| 480p | $0.3975 | $6.7575 | 17 x $0.3975 |
| 720p | $0.85125 | $14.4712 | 17 x $0.85125 |
Check that you have it
The script below asks for the video model list and prints whether the id is present. It stops with a message if the key is missing.
import json, os, urllib.request
key = os.environ["SUME_API_KEY"]
req = urllib.request.Request(
"https://api.sume.com/v1/videos/models",
headers={"Authorization": f"Bearer {key}"})
text = urllib.request.urlopen(req).read().decode()
print("higgsfield-genjutsu listed:", "higgsfield-genjutsu" in text)
print("h3-max-recast listed:", "h3-max-recast" in text)
print(len(json.loads(text).get("data", [])), "models returned")If it is not listed
Use Kling 3.0 Motion Control (one still plus one driver, $0.1575 per second, always in the catalog) or H3 Max Recast (swap people in a clip, $0.375 per second). Genjutsu also takes video references but not audio, and the output length is the source length, so a 17-second source gives a 17-second result.
How to treat the estimate
The 480p and 720p numbers come from an estimate that was taken on 2026-09-18 and written into Sume's price table. Providers change prices, and Sume's own docs do not list a Genjutsu price, so I would not quote $6.7575 to a client. I would quote the amount that your account's quote shows at submit time. The arithmetic is shown only so that you can see the scale: 17 seconds is 17 x $0.3975 = $6.7575 at 480p and 17 x $0.85125 = $14.47125 at 720p.
Genjutsu preserves the source length, so the declared duration must be the inspected length of the source video, 4 to 30 seconds. A 3-second source is below the minimum, and a 31-second source is above the maximum; either is refused before any reservation.
Because the catalog may not list it, build your pipeline so that it falls back to Kling 3.0 Motion Control when the model is absent.
Sources
Related posts
More in Models
- 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.
- GLM-5.3-FlashX costs $0.37 in on Z.ai; Sume lists Flash, not FlashX
Z.ai's pricing page lists Flash, FlashX and GLM-5.3, with no Fast row. Sume's registry has a GLM 5.3 Flash row only.
- 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