Veo 3.1 via the Tokenator API
About Veo 3.1
Google's state-of-the-art video generation model, built for maximum visual fidelity in final production cuts. Veo 3.1 generates high-quality 1080p video from text or image prompts with native synchronized audio — including dialogue, ambient effects, and background sound. Supports scene extension (up to 20 chained clips for 140+ second narratives), frames-to-video transitions between two images, vertical video for Shorts, and 4K upscaling.
Specification
| Full name | Veo 3.1 |
| API ID | veo-3.1 |
| Model vendor | Gemini |
| Type | Video generation |
| Clip duration | 4, 6, 8 seconds |
| Resolution | 720p, 1080p, 4k |
| Aspect ratio | 16:9, 9:16 |
| Audio | yes |
| Reference | accepted — you may attach an image, but the model works without one |
| First frame | accepted only together with the last frame |
| Last frame | accepted only together with the first frame |
| Billing | 720p — 1×, 1080p — 1.5×, 4k — 2× |
| Defaults | 4 seconds, 720p, 16:9 |
| Generation time | up to 15 min |
| Badge | NEW |
| Supported API formats | /v1/videos/generations |
| Upstream providers | 1 |
| Current status | available |
| Data updated | 2026-11-04 |
Upstream providers
| Provider | Multiplier |
|---|---|
| FastCluster | 9× |
A request goes to the first available provider by priority; if it fails, Tokenator switches to the next one.
Example request
curl https://api.tokenator.top/v1/videos/generations \ -H "Authorization: Bearer sk-your-tokenator-key" \ -H "Content-Type: application/json" \ -d '{ "model": "veo-3.1", "prompt": "a neon city in the rain, slow camera fly-through", "duration": 4, "resolution": "720p" }'
Compatible tools
The model can be used in any tool that accepts a custom base URL: Claude Code, Codex CLI, OpenCode, Cursor, Cline, Kilo Code, Cherry Studio, DeepSeek Harness, Hermes, Pi, OpenClaw.
See also
FAQ about Veo 3.1
What is the API ID of Veo 3.1?
veo-3.1 — put this into the model field of your request.
How do I request a video?
POST to /v1/videos/generations with model and prompt. The same key and the same base URL as for text models — only the path changes. The answer comes back when the clip is ready, with a link to the mp4 in data[0].url. The full request description, the parameters and curl, Python and Node.js examples are in the video generation documentation.
Which parameters does Veo 3.1 accept?
prompt — the scene description, duration — 4, 6, 8 seconds, resolution — 720p, 1080p, 4k, aspect_ratio — 16:9, 9:16, generate_audio for sound, frame_images to animate an existing frame. Values outside this list are refused with a clear error, and anything you leave out is filled from the model's defaults.
What does one clip cost?
Video is not billed in tokens but in generations from a video bundle: 720p — 1×, 1080p — 1.5×, 4k — 2×. A longer clip costs proportionally more than a short one. The remaining generations are shown in your account and in the key dashboard.
How long does it take?
A render takes from tens of seconds to a few minutes. The connection is held with a keep-alive, and if the model answers with an async job the proxy waits for it and hands back the finished clip — you do not need to poll anything yourself.
What if a render fails?
The claimed generations are refunded automatically — a failed render costs nothing. If it keeps failing, try another aspect ratio or a shorter clip: not every combination is supported by every provider.
Can I try it without writing code?
Yes: the Studio tab in your key dashboard has an Images / Video switch where duration, resolution and aspect ratio are picked with buttons. Video bundles are on sale in your account.