feral cape
The /api/alpha/videos/models endpoint's pricing SKU system is not really consistent enough to be able to be used programatically. Like sometimes with_audio and without_audio are different, sometimes they're the same, and Seedance uses an entirely different system involving tokens.
Maybe a system where the keys are in format "[mode].[resolution].[audio]" would be a good idea.
For example,
"text_to_video_duration_seconds_480p": "0.04",
"text_to_video_duration_seconds_720p": "0.08",
"image_to_video_duration_seconds_720p": "0.10",
"text_to_video_duration_seconds_1080p": "0.12",
"image_to_video_duration_seconds_1080p": "0.15"
would be
"t2v.480p.*": "0.04",
"t2v.720p.*": "0.08",
"i2v.720p.*": "0.10",
"t2v.1080p.*": "0.12",
"i2v.1080p.*": "0.15"
and
"duration_seconds": "0.40",
"duration_seconds_with_audio": "0.4",
"duration_seconds_with_audio_4k": "0.6",
"duration_seconds_without_audio": "0.2",
"duration_seconds_without_audio_4k": "0.4"
would be
"*.4k.audio": "0.6",
"*.4k.no_audio": "0.4",
"*.1080p.audio": "0.4",
"*.1080p.no_audio": "0.2",
"*.720p.audio": "0.4",
"*.720p.no_audio": "0.2"
(4k could either be 2160p ? )
and for seedance's weird token-based thing it would pre-calculate the costs so the user doesn't have to.
deft sorrel