Image and video examples
Use the same Facade host and Prism API key as chat completions. The examples below assume:GET /v1/models or the console model catalog to choose a public model ID for your org. The sample IDs below show the expected request shapes; replace them with the IDs published in your catalog.
Image generation
POST /v1/images/generations accepts OpenAI-style image generation bodies. Facade authenticates the customer key, checks catalog visibility and credits, then routes the request through the configured image runtime.
Text-to-video
Create video jobs withPOST /v1/video/generations. Video is asynchronous: store the returned job ID, then poll GET /v1/video/generations/{jobId}.
Image-to-video
Send a hosted image URL with the video request.prompt may describe the motion; media-only requests are accepted by video runtimes that support image or reference inputs.
HappyHorse 1.1 text-to-video
HappyHorse 1.1 is the latest Alibaba video model with cinematic lighting, stable camera movements, and native audio generation. Usehappyhorse-1.1-t2v for text-to-video.
HappyHorse reference-to-video
HappyHorse-compatible request shapes supportimageUrls for multi-reference video generation and audio controls such as generateAudio and refAudioUrl.
Video edit
For video edit models, sendrefVideoUrl. A prompt is useful for edit intent, but the media input is the required anchor.
Poll a video job
Operational notes
- Video and image model IDs must appear in
GET /v1/modelsfor the calling key. - Media inputs are URL-only today. Prism does not accept a file upload in these request bodies. Host the input on an HTTPS URL that the selected runtime can fetch, and avoid long-lived public access where a short-lived URL is possible.
- If the selected model is draft, not visible, not configured for the requested modality, or missing provider credentials, the Facade returns a catalog or runtime configuration error.