LeonardoAI Motion 2.0 Image-to-Video API: Endpoint & Pricing
LeonardoAI Motion 2.0 Image-to-Video exposes video generation video generation through LLM.API so motion experiments share the same billing and auth as other models.
What is LeonardoAI Motion 2.0 Image-to-Video?
LeonardoAI Motion 2.0 Image-to-Video targets motion content rather than chat. Video generation model by Muapi. On LLM.API it sits alongside other media models under a single developer account.
Can you self-host LeonardoAI Motion 2.0 Image-to-Video?
No. We found no public weights for LeonardoAI Motion 2.0 Image-to-Video on Hugging Face, so there is nothing to download, quantize or serve on your own GPUs: no VRAM budget, no vLLM or GGUF build to plan for. The only way to run it is over an API.
Skip the deploy — use LLM.API as your endpoint
No GPUs, no quantization trade-offs. Same model, OpenAI-compatible, with custom volume discounts on request.
Providers
LLM.API routes LeonardoAI Motion 2.0 Image-to-Video to the providers below, with discounted effective rates versus list price.
List price by provider
InputOutputProvider list prices; the LLM.API discount applies on top.
| Provider | Pricing | Context | Capabilities |
|---|---|---|---|
| muapi | in —; out $0.0001 per second of video | — | — |
Prices and availability from the LLMAPI catalogue, updated nightly. Last updated 11 Oct 2026.
Try this model
Test LeonardoAI Motion 2.0 Image-to-Video right here — free to start.
Suggestions for your first prompt
Code snippet
Call LeonardoAI Motion 2.0 Image-to-Video through the OpenAI-compatible API — Video generation via LLM.API (see docs for media endpoints).
Switching from OpenAI? Change 2 lines.
- base_url="https://api.openai.com/v1"
- api_key="YOUR_OPENAI_KEY"
+ base_url="https://api.llmapi.ai/v1"
+ api_key="YOUR_LLMAPI_KEY"Everything else stays the same — SDK, message format, tools, streaming. Set model to leonardoai-motion-2.0 and the call runs unchanged.
curl https://api.llmapi.ai/v1/chat/completions \
-H "Authorization: Bearer $LLMAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "leonardoai-motion-2.0",
"messages": [
{"role": "user", "content": "Give me three crisp launch checklist items."}
]
}'from openai import OpenAI
client = OpenAI(
api_key="YOUR_LLMAPI_KEY",
base_url="https://api.llmapi.ai/v1",
)
resp = client.chat.completions.create(
model="leonardoai-motion-2.0",
messages=[
{"role": "system", "content": "You are a precise product assistant."},
{"role": "user", "content": "Give me three crisp launch checklist items."},
],
)
print(resp.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({
apiKey: process.env.LLMAPI_KEY,
baseURL: "https://api.llmapi.ai/v1",
});
const resp = await client.chat.completions.create({
model: "leonardoai-motion-2.0",
messages: [
{ role: "user", content: "Give me three crisp launch checklist items." },
],
});
console.log(resp.choices[0].message.content);stream = client.chat.completions.create(
model="leonardoai-motion-2.0",
messages=[{"role": "user", "content": "Write a haiku about latency."}],
stream=True,
)
for chunk in stream:
delta = chunk.choices[0].delta.content
if delta:
print(delta, end="", flush=True){
"model": "leonardoai-motion-2.0",
"messages": [
{"role": "system", "content": "You are a precise product assistant."},
{"role": "user", "content": "Give me three crisp launch checklist items."}
]
}ENDPOINTS
Supported endpoints & features
Base URL https://api.llmapi.ai/v1 · model ID leonardoai-motion-2.0 · OpenAI-compatible.
POST /v1/chat/completionsChat Completions — supported
| Feature | Status | How to set it |
|---|---|---|
| Function calling (tools) | Not supported | tools, tool_choice |
| Parallel tool calls | Not supported | parallel_tool_calls |
| JSON mode | Not supported | response_format: {"type": "json_object"} |
| Structured outputs | Not supported | response_format: {"type": "json_schema", …} |
| Streaming | Not supported | stream: true |
| Vision (image input) | Not supported | image_url content parts |
| Web search | Not supported | web_search |
ERRORS
Errors & fallback routing
| Code | What it means | What to do |
|---|---|---|
401 | Missing or invalid API key. | Send Authorization: Bearer YOUR_LLMAPI_KEY and check the key is active. |
429 | Rate limited, or the upstream provider is throttling the request. | Back off and retry with jitter; the gateway also retries the request on another provider where one is available. |
5xx | Upstream provider error or timeout. | Retry; fallback routing sends the retry to the next healthy provider for this model. |
When a provider fails or throttles, the request is routed to the next provider serving this model — the ones listed in the providers table above.
LeonardoAI Motion 2.0 Image-to-Video in production
What the model is good at.
Product visualization
Helps visualize products and environments before shoot or 3D work. Relevant for `leonardoai-motion-2.0` workloads on LLM.API.
Resolution options
Supports multiple output resolutions depending on provider pricing tiers. Grounded in the model's video role rather than generic chat claims.
Iterative creatives
Enables prompt-based A/B exploration of motion concepts. Reflects video generation positioning for this endpoint.
Storyboard acceleration
Turns written beats into moving drafts for rapid review.
Cinematic prompting
Responds to camera, lighting, and mood language in creative briefs. Reflects video generation positioning for this endpoint.
What you get when you call LeonardoAI Motion 2.0 Image-to-Video through LLM.API.
Unified AI Routing
Production: Reach LeonardoAI Motion 2.0 Image-to-Video and sibling models through one OpenAI-compatible endpoint.
One endpoint, every model.Cost Control
Practical: Compare provider price points and keep spend visible as you scale LeonardoAI Motion 2.0 Image-to-Video.
More performance, less spend.Reliability Layer
Practical: Retry and route across configured providers when a single upstream blips.
Never go dark on users.Observability
Production: Trace prompts, tokens, and errors for LeonardoAI Motion 2.0 Image-to-Video alongside the rest of your stack.
See every token, everywhere.Drop-in SDKs
Practical: Keep using familiar OpenAI client patterns with base URL https://api.llmapi.ai/v1.
Think tasks, not models.Model Breadth
Swap LeonardoAI Motion 2.0 Image-to-Video for chat, media, or embedding alternatives without rewriting auth.
Scale from 1 to millions.
When to Use — When NOT to Use
Use it if...
- You can tolerate longer generation times than chat (LeonardoAI Motion 2.0 Image-to-Video)
- You need resolution-tiered pricing for motion content (LeonardoAI Motion 2.0 Image-to-Video)
- You are building short-form generative video features (LeonardoAI Motion 2.0 Image-to-Video)
Avoid if...
- You need broadcast-length films or guaranteed cinema-grade continuity
- You require sub-second interactive generation
- You only need still images or chat text
COMMUNITY
What creators say about AI video models
Summarised from publicly published developer and community reviews of this model family. Opinions are the sources’, not LLM.API’s, and may not be specific to LeonardoAI Motion 2.0 Image-to-Video.
- Creator reviews of the latest Kling releases praise multi-shot consistency, native audio and genuine 4K output.
- Comparisons with Sora and Runway focus on prompt adherence and motion stability rather than raw resolution.
- The common workflow advice: generate many short takes cheaply, then upscale or extend the ones that land.
SOURCES
COMMUNITY
What developers say about LeonardoAI Motion 2.0 Image-to-Video
— No public developer feedback about this model yet.
Frequently Asked Questions
How do I call LeonardoAI Motion 2.0 Image-to-Video via API?
Send OpenAI-compatible requests to https://api.llmapi.ai/v1 with model "leonardoai-motion-2.0" and your LLM.API key. See the code snippet on this page.
What modalities does LeonardoAI Motion 2.0 Image-to-Video support?
LeonardoAI Motion 2.0 Image-to-Video accepts text, image and produces video according to its architecture metadata on LLM.API.
Which providers serve LeonardoAI Motion 2.0 Image-to-Video?
LLM.API currently lists: muapi. Availability can vary by region and account.
What are limitations of LeonardoAI Motion 2.0 Image-to-Video?
Like other API models, LeonardoAI Motion 2.0 Image-to-Video can be wrong, incomplete, or uneven on edge cases. Validate outputs for high-stakes use. Media/OCR/STT models additionally depend on input quality.
What is the context length for LeonardoAI Motion 2.0 Image-to-Video?
Reported context for LeonardoAI Motion 2.0 Image-to-Video is See provider specs. Always verify the active provider row if multiple providers are listed.
Does LeonardoAI Motion 2.0 Image-to-Video support streaming?
Streaming depends on the active provider; check the providers table on this page for flags.
When should I choose LeonardoAI Motion 2.0 Image-to-Video?
You can tolerate longer generation times than chat — especially when you specifically need LeonardoAI Motion 2.0 Image-to-Video.
Where is the canonical page for LeonardoAI Motion 2.0 Image-to-Video?
https://llmapi.ai/models/leonardoai-motion-2-0/
COMPARE
Competitive Models
Kling V2.1 Pro Image-to-Video
Output$0.08 / secondList price per second of video.
— in / $0.08 out per second of video, context varies — the closest current alternative to LeonardoAI Motion 2.0 Image-to-Video.
Vidu Q1 Reference Image-to-Video
Output$0.08 / secondList price per second of video.
— in / $0.08 out per second of video, context varies — the closest current alternative to LeonardoAI Motion 2.0 Image-to-Video.
Veo 3 Fast Text-to-Video
Output$0.075 / secondList price per second of video.
— in / $0.075 out per second of video, context varies — the closest current alternative to LeonardoAI Motion 2.0 Image-to-Video.
Get one key to every model
Swap your API key. Keep your code.