seedance-2.0-fast optimizes iteration speed for storyboards and ad variants. seedance-2.0 targets higher-quality renders when Fast output is not sufficient.
Short-drama and marketing teams often pipeline Fast previews into standard final renders. Both ids bill through the same LumeAPI wallet.
Full task API examples live on /docs/models/seedance-2.0 and /docs/models/seedance-2.0-fast.
Integration checklist for Seedance
Use seedance-2.0-fast for creative iteration and seedance-2.0 for finals—document that workflow for content teams so bills match expectations.
Persist task ids until outputs are downloaded or expired. Retry failed tasks with capped attempts to avoid runaway wallet debits.
Content teams should tag each render with seedance-2.0-fast vs seedance-2.0 in metadata so monthly Usage reviews map spend to workflow stage.
Self-serve path: register to first API call
LumeAPI is designed for developers who want to integrate without scheduling demos. Create an account, confirm your email, and open Console to generate an API key. Fund your USD wallet with USDT on supported chains when you are ready for billable traffic—there is no mandatory minimum beyond what your tests require.
Point your OpenAI-compatible client at https://api.lumeapi.site/v1, set Authorization to Bearer your key, and pass a catalog model id in the model field. Run a short curl or SDK script from /docs to verify latency, streaming, and error handling before you attach the key to production services.
Use Usage logs to reconcile per-call cost with finance forecasts. When a model tier is too expensive or quality is insufficient, change model id—not your entire integration. For cross-provider price tables and Research deep dives, follow internal links on this page rather than duplicating migration math here.
Documentation, catalog, and support
Every catalog model has a detail page under /models with official reference pricing, LumeAPI pricing, and links to /docs/models/{id} for parameters and curl examples. Start there when this commercial page points you to a model id you have not called before.
The /docs index lists gateway authentication, Chat Completions, image endpoints, and async video patterns. llms.txt bundles the same information for agent tooling—useful when you want a single URL to paste into Cursor or an internal bot.
Research articles explain why bills grow and how to compare providers; commercial pages like this one explain what LumeAPI offers and how to start. Follow internal links instead of searching for duplicate migration content across pages.
If billing, chain deposits, or integration behavior is unclear, use /contact for support channels. Include your model id, approximate request time, and whether the issue is authentication, balance, or model parameters—that speeds up resolution.
Why LumeAPI
Mainstream models only
GPT, Claude, and Gemini catalog ids with published per-token or per-media rates — not obscure small models marketed as discounts.
Transparent pricing
Official reference vs LumeAPI columns on every commercial page. Your request model id matches Usage logs and billing.
OpenAI-compatible gateway
One base URL for Chat Completions, image generations, and async video. Swap key, base URL, and model id — keep your SDK.
Self-serve wallet
Top up with USDT, create keys in Console, and track per-call cost in Usage — no sales calls required.
Get started in three steps
Create an API key — register and open Console.
Set the LumeAPI base URL — https://api.lumeapi.site/v1
Choose a supported model id — from the table above or model catalog.
Migrate in minutes
Three values change: API key, base URL, model id. Everything else stays the same.
Before (direct Seedance provider)
python
# Direct Seedance provider SDK
After (LumeAPI)
python
# Seedance async task — full example at /docs/models/seedance-2.0
# Gateway base: https://api.lumeapi.site/v1