Text-to-video, image-to-video and reference-to-video all take the same request body on the same key — 53 models, every published tier on one card, so a batch can be priced before it renders.
Twelve prompts, one render each from every video model on this catalog. Watch the output before you commit the batch — the model that follows the instruction is not always the one with the best spec sheet.
A fixed camera on a single traffic light against a plain grey sky. The light starts red, changes to green, and then changes to amber, in that exact order, each colour holding for a clearly visible moment. No other objects, no camera movement, no cuts.
Text-, image- and reference-to-video clips — anime sequels, promo videos and explainer content.
Character consistencyPer-second pricing1080p / 4K output| Model | Price · GPTProto | vs Official | vs OpenRouter | Context | Modality | Stability | Action |
|---|---|---|---|---|---|---|---|
 Seedance 2.5 (Build 260628)Bytedance | $0.45per 5s clip | — | — | — | → | Try | |
| Seedance 2.0 (Build 260128)Bytedance | $0.30per 5s clip | — | — | — | → | Try | |
| Seedance 2.0 Fast (Build 260128)Bytedance | $0.18per 5s clip | — | — | — | → | Try | |
| Seedance 2.0 Mini (Build 260615)Bytedance | $0.095per 5s clip | — | — | — | → | Try | |
| Seedance 1.5 Pro (Build 251215)Bytedance | $0.041per 5s clip | −15% | −19% | — | → | Try | |
 Minimax H3MiniMax | $0.22per 5s clip | −30% | −34% | — | → | Try | |
 Wan 3.0NewQwen | $0.090per 5s clip | −10% | −15% | — | → | Try |
Choose a workflow and usage level to see an example monthly cost on GPTProto, alongside the same usage at comparable provider rates.
Video and agent workloads burn credits faster — the recommendation adjusts automatically as you switch scenario or usage level.
Point one client at one host and the request body stops changing when the model does. The only string that moves is the model id.
The whole migration is one field — same endpoint, same auth header, same polling route.
A render pipeline does not stop when one scene looks good — it stops when a channel degrades at clip 140. Here is what keeps the queue moving.
Major models run on redundant upstream channels. If one degrades mid-batch the work moves to a backup instead of dying with it — no code change, no job left sitting at pending.
Major models are served through redundant upstream channels, so a single provider outage does not take the whole batch down with it.
Browse modelsContinuous monitoring with automatic traffic shifting, so a degrading channel is routed around before it becomes a queue that quietly stops moving.
Enter how many clips you render a month and we price them at the tier you are actually buying — not at a headline number.
Real posts from real, public accounts — nothing here is invented.
For a team already juggling DeepSeek, Kimi, Qwen, or other providers, a shared routing layer can be reasonable if it removes duplicated work and the fallback behavior is tested. GPTProto is one implementation of this approach.
I've been testing GPTProto recently, and it's honestly made my creative workflow much simpler. Instead of paying for multiple subscriptions, I can access several leading AI models from one place.
I turned this single prompt into a cinematic fantasy video using GPTProto. "Continuous 15-second cinematic shot, 4K resolution, hyper-realistic dark fantasy photorealism…"
I challenged myself to create a cinematic AI cooking short in just 15 seconds. I used GPTProto to bring the entire workflow together, from image generation to video, all in one place.
Made with Seedance 2.0 + GPT Image 2 on GPTProto. A Pixar-style commercial with the perfect glow.
What worked for me was pointing the cloud connections at GPTProto so the frontend only sees one endpoint and I just change the model name to swap. I am not rebuilding a connection from scratch every time.
I route the calls through GPTProto so a fallback is a config switch instead of a weekend rewrite when a model disappears. It turns "my default model just got export controlled" from an incident into a config change.
I used to switch between different AI tools just to compare results. Now I just use GPTProto. GPT-5, Claude, Gemini, Kimi, and more — all in one workspace.
I route the calls through GPTProto so the model id and latency land in one place regardless of which provider is behind it. The win is having the log schema consistent across providers.
I created this 15-second cinematic product video with GPTProto using Seedance 2.0, and I was really impressed by how smooth the workflow was.
GPTProto routes the character prompt and shot list to a top model on one API key: 20 minutes … voices it and burns in captions from the same key: 20 minutes.
Text, images, and voice are configured separately. You can keep OpenRouter for text and use GPTProto for visuals.
The call layer underneath the router is GPTProto, so swapping a model does not require provisioning a new provider integration. Changing models becomes cheap enough that the question stops being "should we change."
You only pay for what you render. Top up once, then spend the balance on any of the 53 video models at the discounted rate — top-ups of $20+ earn bonus credits.
Enough for a first pass of short clips — enough to put a real invoice next to the spreadsheet. Top up $20+ anytime to unlock bonus credits.
The usual first top-up: render a week of real clips, keep the old provider as a fallback, and compare both invoices before you commit.
For pipelines already rendering daily. Bonus credits spend at these same discounted rates, so the bonus deepens the discount instead of sitting off to the side.
Short answers, no sales talk. Every one of these is something a team wiring video generation into a pipeline has actually asked.
Both, and the model decides. Vidu Q3 Turbo bills strictly per second at every resolution, three tiers in total. Kling v3.0 Std publishes a separate per-run price for each length from 3 to 15 seconds — 26 of them. Nothing on the catalog is billed in “video points” and nothing is rounded up to the nearest minute.
It is one published cell, not a flat rate. Vidu Q2 Pro Fast at 540p for 10 seconds costs $0.096, which is $0.0096 a second, and that is the cheapest second we sell. The same model at 1080p for 1 second costs $0.064 — six times the per-second price for a tenth of the clip. That is why the card publishes the tier, not a headline number.
Both, and they answer different questions. The catalog’s fixed price is the cheapest single run the model sells. $0.0096 is that same run divided by its length. If you buy many short clips, the run price is what bills; if you buy long clips, the per-second figure is what compounds. The model page prints every tier so you can pick the axis that matches your batch.
No. All 53 video models take the same POST /api/v3/videos body, the same bearer token and the same polling route. Changing models is one string in the model field.
First and last frames go in frame_images as {"type":"image_url","image_url":{"url":"…"},"frame_type":"first_frame"}. Reference images, audio or video go in input_references, which keeps the same image_url carrier field whichever medium it holds. Both need URLs the provider can reach — a local path will not work. Not every model accepts both, and the model page says which.
Yes — that is what the rate card and the calculator are for. Pick the model, the resolution and the length and you get the published price for that exact configuration. Combinations a model does not sell are not offered, so you never get a number you cannot actually buy.
Major models run on redundant upstream channels with automatic failover and monitoring around the clock, so a channel that degrades is routed around instead of leaving a job stuck at pending. We publish what the mechanism does, not an availability percentage — there is no uptime guarantee attached to this page.
Any time. There is no subscription and no minimum: it is a top-up balance, bonus credits spend at the same discounted rates as the rest of your balance, and moving back to a direct provider is the same one-line change you made to move here.
Field-level API docs, the live video catalog, and the model page that prints every tier behind the prices above.
Create images and videos online, or bring text, image, and video models into your app with one API key. Explore discounted rates on selected models.
