Skip to main content

The Livepeer AI Gateway exposes nine batch pipelines and one LLM pipeline through HTTP POST endpoints. Each pipeline accepts a JSON request body keyed by model_id and pipeline-specific fields, and returns a JSON response with the result. Real-time video AI (live-video-to-video) runs through the trickle protocol and is covered separately in the real-time AI overview. For warm models, VRAM requirements, and architecture support per pipeline, see model support. For SDK wrappers, see AI SDKs.

Shared conventions

Base URL: Any Livepeer Gateway endpoint. The community Gateway at https://dream-gateway.livepeer.cloud accepts unauthenticated requests for development. Authentication: Bearer token when the Gateway requires it. The community Gateway does not require a token. Request format: POST /<pipeline-endpoint> with Content-Type: application/json. model_id field: Every pipeline accepts a model_id field specifying the Hugging Face model ID (or Ollama model ID for LLM). Omitting model_id uses the pipeline’s default warm model. Error responses: 400 for malformed requests, 422 for validation errors (invalid model_id, missing required fields), 500 for inference failures. Error bodies include a detail field with the failure reason. Cold model latency: If no Orchestrator has the requested model warm in GPU memory, the first request triggers a model load (30 seconds to 5 minutes depending on model size). Subsequent requests to the same model on the same Orchestrator are immediate.

Pipeline reference

Generate images from text prompts using diffusion models (SDXL, SD 1.5, Flux).
Response: JSON object with images array. Each image is a { url, seed } object.
Transform images using style transfer, enhancement, or img2img diffusion.
Response: JSON with images array, same format as text-to-image.
image-to-image uses multipart/form-data, not application/json. The image is uploaded as a file field.
Animate a still image into a short video clip using Stable Video Diffusion.
Response: JSON with frames array containing frame URLs, or a video URL.
SVD outputs 14-25 frames at 576x1024 resolution. Text prompts are not used; the image is the sole conditioning input.
Generate captions or descriptions for images using BLIP or vision-language models.
Response: JSON with text field containing the generated caption.
Transcribe audio to text with per-chunk timestamps using Whisper.
Response: JSON with text (full transcript) and chunks array (per-segment timestamps and text).
Generate natural speech from text using Parler-TTS.
Response: JSON with audio object containing a URL to the generated audio file.
Requires a pipeline-specific AI Runner container. Not all Orchestrators have this pipeline active.
Upscale low-resolution images using the SD x4-Upscaler (4x super-resolution).
Response: JSON with images array, same format as text-to-image.
Promptable visual segmentation for images using SAM 2 (Meta AI).
Response: JSON with masks, scores, and logits arrays.
OpenAI-compatible chat completions using Ollama-based runner.
Response: OpenAI-compatible chat completion object with choices[0].message.content.
The LLM pipeline is in beta. The request format follows the OpenAI /v1/chat/completions shape. Supported models include Meta-Llama-3.1-8B-Instruct (warm, 8 GB VRAM), Mistral-7B-Instruct-v0.3, Gemma-2-9b-it, and Qwen2.5-7B-Instruct.

Operational notes

Multipart vs JSON. Pipelines that accept file uploads (image-to-image, image-to-video, image-to-text, audio-to-text, upscale, segment-anything-2) use multipart/form-data. Pipelines that accept only text input (text-to-image, text-to-speech, LLM) use application/json. Gateway selection. The community Gateway routes to whichever Orchestrator in the Active Set has the requested model warm. For production, operate a self-hosted Gateway with -maxPricePerUnit to control costs, or use a Gateway provider with an API key. safety_check filter. Enabled by default on image-generating pipelines. Set to false to disable. The filter runs on the Orchestrator side; disabling it does not affect content moderation policies that the Gateway operator may enforce. The AI quickstart walks through the first inference call end-to-end with error handling.
Last modified on May 31, 2026