Beat API

Choose the API level that matches your need. For complete outputs, use the workflow endpoints: supply source audio and visual references to the music video API, or product images with an offer brief and creative direction to the ecommerce video API, and receive a traceable asynchronous task producing a hosted finished video. For lower-level control, call the video or image APIs directly against a chosen model. For live experiences, the realtime API handles WebRTC and camera input with transformation applied as the stream runs. Tasks are asynchronous by design, which is the correct pattern for generation that takes minutes rather than milliseconds.

• •Workflow Endpoints, Not Just Models - Complete music video and ecommerce video processes rather than a single generation call
• •Traceable Async Tasks - Long-running generation modelled properly as asynchronous work with traceability
• •Hosted Output - Generated video hosted rather than handed back as a file for you to store
• •Direct Model Access - MiniMax H3, Seedance 2.5, Veo 3.1 and Kling 3.0 available individually
• •Image API - Nano Banana, GPT Image 2 and Seedream 5.0 Pro alongside video
• •Realtime WebRTC Transformation - Live camera transformation, a materially harder problem than batch generation
• •Effect API - Style, dance, commerce and transformation effects as named endpoints
• •Published API Documentation - Developer docs available for all five families

For engineering teams building video generation into a product, particularly anyone who has discovered that turning a model call into a finished music video or product video involves substantially more orchestration than expected. The ecommerce video workflow suits platforms generating product video for many sellers. The realtime WebRTC API serves live streaming and camera-based applications, which is a much smaller and more specialised audience. This is developer infrastructure with usage-based pricing, so it is not intended for individual creators wanting an interface.