Community example: three API-generated product images → a local Hyperframes video

[YamiAnn]

Hi Hyperframes community, I'm YamiAnn from ToAPIs. We built a small product-story example using three original API-generated images, an HTML timeline and local Hyperframes MP4 rendering.

The three gpt-image-2(VIP) low/1K image calls cost $0.0019/image, or $0.0057 total. The resulting locally rendered video is 12 seconds, 1280×720 at 24 fps. That amount is the image API spend only: local rendering does not call a video model and is not a video API price per second.

Source timeline, image prompts, outputs and bilingual guide:
https://github.com/ToAPIs-2025/lower-cost-hyperframes-toapis

We would love feedback on whether this is useful as a community asset-to-timeline example. We can provide test credits for maintainers, help reproduce the image calls and keep a focused configuration/example guide up to date.

For future work, we also support image and video model APIs. If generated video assets fit Hyperframes' import/timeline contracts, we'd be happy to align with the integration maintainer and validate that separately. The example linked above validates images plus local rendering, not a native video-model integration.

YamiAnn · ToAPIs

---

Tested model types, presets and costs

Updated October 16, 2026. These are tested historical presets/prices; this addition does not relabel the original batch below.

Model (API ID)	Type	Tested preset	Unit quote	Confirmed unit charge	Count
gpt-image-2(VIP) (gpt-image-2-vip)	Image	low / 1K / n=1	$0.0019/image	$0.0019	3

Confirmed original image/video example subtotal: $0.0057.

Image API calls and a 12-second local MP4 render validated; local rendering is not a video-model call.

Local rendering makes no video-model call. Dividing image spend by 12 seconds would not be a video API rate.

gpt-image-2(VIP), from $0.0019/image; the tested low/1K preset here is $0.0019/image. Different models, qualities and resolutions do not imply equivalent results.