Ai Image To Video Motion
v1.0.0Get animated motion videos ready to post, without touching a single slider. Upload your still images (JPG, PNG, WEBP, HEIC, up to 200MB), say something like...
Getting Started
Got still images to work with? Send it over and tell me what you need — I'll take care of the AI motion video creation.
Try saying:
- "convert a single product photo or landscape image into a 1080p MP4"
- "animate this image with a slow zoom and subtle motion effects"
- "turning still photos into animated video clips for social media creators"
First-Time Connection
When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").
Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.
- Obtain a free token: Generate a random UUID as client identifier. POST to
https://mega-api-prod.nemovideo.ai/api/auth/anonymous-tokenwith headerX-Client-Idset to that UUID. The responsedata.tokenis your NEMO_TOKEN — 100 free credits, valid 7 days. - Create a session: POST to
https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agentwithAuthorization: Bearer <token>,Content-Type: application/json, and body{"task_name":"project","language":"<detected>"}. Store the returnedsession_idfor all subsequent requests.
Keep setup communication brief. Don't display raw API responses or token values to the user.
AI Image to Video Motion — Animate Images into Motion Videos
Drop your still images in the chat and tell me what you need. I'll handle the AI motion video creation on cloud GPUs — you don't need anything installed locally.
Here's a typical use: you send a a single product photo or landscape image, ask for animate this image with a slow zoom and subtle motion effects, and about 20-45 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.
One thing worth knowing — high-contrast images with clear subjects produce the most visible motion effects.
Matching Input to Actions
User prompts referencing ai image to video motion, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.
| User says... | Action | Skip SSE? |
|---|---|---|
| "export" / "导出" / "download" / "send me the video" | → §3.5 Export | ✅ |
| "credits" / "积分" / "balance" / "余额" | → §3.3 Credits | ✅ |
| "status" / "状态" / "show tracks" | → §3.4 State | ✅ |
| "upload" / "上传" / user sends file | → §3.2 Upload | ✅ |
| Everything else (generate, edit, add BGM…) | → §3.1 SSE | ❌ |
Cloud Render Pipeline Details
Each export job queues on a cloud GPU node that composites video layers, applies platform-spec compression (H.264, up to 1080x1920), and returns a download URL within 30-90 seconds. The session token carries render job IDs, so closing the tab before completion orphans the job.
All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:
- Session —
POST /api/tasks/me/with-session/nemo_agentwith{"task_name":"project","language":"<lang>"}. Gives you asession_id. - Chat (SSE) —
POST /run_ssewithsession_idand your message innew_message.parts[0].text. SetAccept: text/event-stream. Up to 15 min. - Upload —
POST /api/upload-video/nemo_agent/me/<sid>— multipart file or JSON with URLs. - Credits —
GET /api/credits/balance/simple— returnsavailable,frozen,total. - State —
GET /api/state/nemo_agent/me/<sid>/latest— current draft and media info. - Export —
POST /api/render/proxy/lambdawith render ID and draft JSON. PollGET /api/render/proxy/lambda/<id>every 30s forcompletedstatus and download URL.
Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.
Three attribution headers are required on every request and must match this file's frontmatter:
| Header | Value |
|---|---|
X-Skill-Source | ai-image-to-video-motion |
X-Skill-Version | frontmatter version |
X-Skill-Platform | auto-detect: clawhub / cursor / unknown from install path |
Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.
Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.
Example timeline summary:
Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)
Backend Response Translation
The backend assumes a GUI exists. Translate these into API actions:
| Backend says | You do |
|---|---|
| "click [button]" / "点击" | Execute via API |
| "open [panel]" / "打开" | Query session state |
| "drag/drop" / "拖拽" | Send edit via SSE |
| "preview in timeline" | Show track summary |
| "Export button" / "导出" | Execute export workflow |
SSE Event Handling
| Event | Action |
|---|---|
| Text response | Apply GUI translation (§4), present to user |
| Tool call/result | Process internally, don't forward |
heartbeat / empty data: | Keep waiting. Every 2 min: "⏳ Still working..." |
| Stream closes | Process final response |
~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.
Error Handling
| Code | Meaning | Action |
|---|---|---|
| 0 | Success | Continue |
| 1001 | Bad/expired token | Re-auth via anonymous-token (tokens expire after 7 days) |
| 1002 | Session not found | New session §3.0 |
| 2001 | No credits | Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account" |
| 4001 | Unsupported file | Show supported formats |
| 4002 | File too large | Suggest compress/trim |
| 400 | Missing X-Client-Id | Generate Client-Id and retry (see §1) |
| 402 | Free plan export blocked | Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export." |
| 429 | Rate limit (1 token/client/7 days) | Retry in 30s once |
Common Workflows
Quick edit: Upload → "animate this image with a slow zoom and subtle motion effects" → Download MP4. Takes 20-45 seconds for a 30-second clip.
Batch style: Upload multiple files in one session. Process them one by one with different instructions. Each gets its own render.
Iterative: Start with a rough cut, preview the result, then refine. The session keeps your timeline state so you can keep tweaking.
Tips and Tricks
The backend processes faster when you're specific. Instead of "make it look better", try "animate this image with a slow zoom and subtle motion effects" — concrete instructions get better results.
Max file size is 200MB. Stick to JPG, PNG, WEBP, HEIC for the smoothest experience.
Export as MP4 for widest compatibility across social platforms.
