Veo 3.1 Fast API on MaxAPI
Veo 3.1 Fast is one of the public models available through MaxAPI.
Common use cases
- Generate short marketing or product videos from a text prompt or storyboard
- Animate a static product photo into a 4-15 second video (image-to-video mode)
- Produce first-and-last-frame interpolations from two reference frames
- Compose multi-reference videos that draw on several image, video, or audio inputs
Endpoints
Video generation is asynchronous. POST the request, then poll the task URL until status is succeeded, failed, or canceled.
- POST /v1/videos/generations
- GET /v1/videos/generations/{task_id}
Dimensions and sizing
Supports resolutions 720p, 1080p, 4k and durations 4–15 seconds. Pass ratio (16:9 / 9:16 / 1:1 / 3:4 / 4:3 / 21:9), duration (seconds), mode (text_to_video / image_to_video / first_last_frame / multi_ref), and resolution.
Available routes
Pass route_mode in the request body (or X-MaxAPI-Route-Mode on the Gemini-native endpoint) to select. If you don't pass one, MaxAPI follows the API key's configured order.
- mix — blended route that may switch between providers for cost and stability; typically the lowest per-image price for beta variants.
Pricing
Pricing is per route mode. Failed requests are not charged. 1 credit = 1 USD.
- mix: $0.1269 per generation
Quick example
curl -X POST "https://api.maxapi.dev/v1/videos/generations" \
-H "Authorization: Bearer $MAXAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "veo-3.1-fast",
"prompt": "a calm ocean wave at sunrise, slow camera pan",
"ratio": "16:9",
"duration": 5,
"mode": "text_to_video",
"resolution": "720p"
}'
FAQ
Is Veo 3.1 Fast on MaxAPI OpenAI-compatible?
Yes. Send requests to POST /v1/videos/generations with an Authorization: Bearer header. The response format mirrors the existing MaxAPI image/video conventions.
How do I switch between route_mode options?
Pass "route_mode": "official" / "official-cheap" / "mix" in the JSON body, or set X-MaxAPI-Route-Mode on the Gemini-native endpoint. Defaults to the API key's configured order.
How is billing handled?
Failed requests don't charge credits. Per-image, per-call, and per-generation pricing is billed on completion; token-priced routes settle from upstream usage. 1 credit = 1 USD.
Where does the returned URL live?
Output assets are stored on MaxAPI's CDN (cdn.maxapi.dev) with a 7-day TTL. Pass "asset_delivery": "mirror" to receive URLs on the configured alias domain instead.
Full API reference