Sora 2 API Alternatives for Developers: One Key, Many Video Models

OpenAI shut down the Sora 2 Videos API on 24 September 2026, so code that called it now fails. A practical replacement is one API that reaches several video models: on the VdoBloom API you can call Veo 3.1, Seedance 2.5, Seedance 2, MiniMax H3, Vidu Q3 and Runway Gen-4.5 with one key, one job format and one credit balance, with no subscription needed. The same models are available to AI assistants through our MCP server.

Quick facts

• Sora 2 API status: shut down 24 September 2026, about six months after OpenAI gave notice in March. VdoBloom does not offer Sora.
• VdoBloom API: REST at https://vdobloom.com/api/v1, bearer key, POST /videos/generations, job polling or webhooks.
• MCP server: https://vdobloom.com/mcp for Claude, ChatGPT and other MCP clients.
• Prices: the same credits as the web app. Veo 3.1 Fast is 25 credits per 8-second clip; Seedance 2 Mini is 17 credits for 5 seconds at 720p.
• Billing: one-time credit packs that never expire; a failed generation is refunded automatically.

Read the VdoBloom API docs

What Sora 2 was good at, and what you need to replace

Sora 2 was popular with developers because it made realistic clips with synced sound from a single API call. Apps used it for social video, ad drafts and story tools. When the API closed, teams lost three things at once: the model, the job workflow around it, and their billing setup.

So a good replacement needs more than a model with similar quality. It needs a stable way to submit jobs, check status, get the file, and handle failures and retries. For a broader, non-developer look at what to use instead, read our Sora 2 alternatives post.

Why one multi-model API makes sense now

• Models retire. Sora showed that a single-model dependency can disappear. With several models behind one API, a switch is a change to one field.
• Different jobs need different models. Cheap drafts, long takes and short polished shots each have a best fit.
• One bill. One credit balance covers every model, and prices match the app.

The 6 best Sora 2 API alternatives on VdoBloom

1. Our pick: Veo 3.1 Fast and Quality on VdoBloom, closest for short clips with sound

Model ids veo3_fast and veo3_quality. Each call makes one 8-second clip with sound, text or image start, 16:9 or 9:16. 25 or 100 credits. See Veo 3.1 Fast.

Test it in the browser before you write code: Try this prompt on Veo 3.1 Fast.

2. Seedance 2.5: long takes up to 30 seconds

Model id bytedance/seedance-2-5. 4 to 30 seconds at 480p, 720p or 1080p, text or image start, audio included. 126 credits for 5 seconds at 720p. See Seedance 2.5.

Test it in the browser before you write code: Try this prompt on Seedance 2.5.

3. Seedance 2, Fast and Mini: one family, three price points

bytedance/seedance-2 runs 4 to 15 seconds up to 4K (82 credits for 5 seconds at 720p). bytedance/seedance-2-fast costs 50 and bytedance/seedance-2-mini 17 at the same length. Use Mini for previews in your app and the full model for finals.

Test it in the browser before you write code: Try this prompt on Seedance 2 Mini.

4. MiniMax H3: cinematic 2K at a low price

Model ids minimax-h3/text-to-video and minimax-h3/image-to-video. 4 to 15 seconds at 768P or 2K, with sound. 20 credits for 5 seconds at 768P. See MiniMax H3.

Test it in the browser before you write code: Try this prompt on MiniMax H3.

5. Vidu Q3: 16-second takes

Model id vidu-q3 (and vidu-q3-turbo). 5, 8 or 16 seconds at 720p or 1080p, picture and sound together. 40 credits for 5 seconds at 720p.

Test it in the browser before you write code: Try this prompt on Vidu Q3.

6. Runway Gen-4.5: demanding prompts

Model id runway-gen45. 5, 8 or 10 seconds at 720p, text or image start. 48, 77 or 96 credits.

Test it in the browser before you write code: Try this prompt on Runway Gen-4.5.

Comparison table

GET /models?type=video returns the full, current list with prices for every length and resolution.

Which model should be your default? For most apps that used Sora 2 for short social clips, Veo 3.1 Fast is the simplest swap: one fixed 8-second clip with sound, at a flat price. If your users want longer clips, Seedance 2.5 reaches 30 seconds. For high volume and low cost, Seedance 2 Mini and MiniMax H3 keep each request small. Many teams use two: a cheap model for previews and a stronger one for the final render.

How to switch from Sora 2 to the VdoBloom API

1. Create a VdoBloom account and buy a one-time credit pack. New accounts get 10 credits on sign-up.
2. In Settings, open the Developer tab, accept the API terms and create a key. It starts with vdb_ and is shown once.
3. Call GET /models?type=video to see models, lengths, resolutions and prices.
4. Send POST /videos/generations with model, prompt, duration, resolution and aspect_ratio. Add image_url for image-to-video. The call returns a job at once.
5. Add an Idempotency-Key header so a retried request does not charge twice.
6. Poll GET /jobs/{id} every 20 to 60 seconds, or set a webhook on the key. Videos take one to ten minutes.
7. Download the video_url as soon as the job completes. Result links are temporary, so store the file yourself.

Rate limits are 120 requests or 20 generations per minute per account. Prompts follow the same content rules as the app, and a blocked prompt is not charged. Full details are on the developer docs.

Create an API key

Migration tips from a Sora 2 integration

• Abstract the model id. Keep the model name in config, not in code. With several models behind one endpoint, swapping is a config change.
• Map your settings. Sora requests had their own size and length fields. On VdoBloom you send duration, resolution and aspect_ratio, and each model accepts its own set. Read them from GET /models instead of hard-coding them.
• Use a cheap model in tests. Point your staging environment at bytedance/seedance-2-mini (8 credits for 5 seconds at 480p) and keep the expensive model for production.
• Plan for async. Treat every video call as a job. Store the job id, then poll or wait for the webhook.
• Store results yourself. Result links expire, so copy each finished file to your own storage.
• Handle 402. When the balance is below the request price, the API returns insufficient_credits. Show a clear message to your user or top up before retrying.

Using the models from an AI assistant (MCP)

If your workflow runs inside Claude, ChatGPT or another MCP client, point it at https://vdobloom.com/mcp. In Claude or ChatGPT you add it as a custom connector and sign in, with no key to paste. Command-line clients can send a vdb_ key as a bearer header. The tools include list_models, generate_video, get_status and create_upload for files on your device.

Try a replacement model in Text to Video

FAQ

Is the Sora 2 API still available?

No. OpenAI shut down the Sora 2 Videos API on 24 September 2026. As of November 2026 there is no replacement video model in its API.

Does VdoBloom offer Sora 2?

No. VdoBloom offers other video models, including Veo 3.1, Seedance and MiniMax H3, through the same API.

Are API prices different from the app?

No. The API uses the same credit prices as the web app, and every job shows its credit_cost.

What happens if a generation fails?

The credits are refunded automatically.

Do I need a monthly plan to use the API?

No. You can use one-time credit packs, which never expire.

Can I use Kling 4.0 or Wan 3.0 through the API?

Not yet. They are in the web app. Check GET /models for the current API list.