Getting Started

Share your static images and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "convert my static images"
• "export 1080p MP4"
• "turn these images into a smooth"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for

NEMO_TOKEN

• Generate a UUID as client identifier
• POST

  https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token

  with

  X-Client-Id

  header
• Extract

  data.token

  from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST

https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent

{"task_name":"project"}

session_id

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

AI Image to Video — Convert Images Into Video Clips

This tool takes your static images and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have three product photos in JPG format and want to turn these images into a smooth animated video with transitions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: high-contrast images with clear subjects animate more smoothly.

Matching Input to Actions

User prompts referencing ai image to video best, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

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

1. Session —

   POST /api/tasks/me/with-session/nemo_agent

   with

   {"task_name":"project","language":"<lang>"}

   . Gives you a

   session_id

   .
2. Chat (SSE) —

   POST /run_sse

   with

   session_id

   and your message in

   new_message.parts[0].text

   . Set

   Accept: text/event-stream

   . Up to 15 min.
3. Upload —

   POST /api/upload-video/nemo_agent/me/<sid>

   — multipart file or JSON with URLs.
4. Credits —

   GET /api/credits/balance/simple

   — returns

   available

   ,

   frozen

   ,

   total

   .
5. State —

   GET /api/state/nemo_agent/me/<sid>/latest

   — current draft and media info.
6. Export —

   POST /api/render/proxy/lambda

   with render ID and draft JSON. Poll

   GET /api/render/proxy/lambda/<id>

   every 30s for

   completed

   status 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:

X-Skill-Source

ai-image-to-video-best

X-Skill-Version

version

X-Skill-Platform

clawhub

cursor

unknown

All requests must include:

Authorization: Bearer <NEMO_TOKEN>

X-Skill-Source

X-Skill-Version

X-Skill-Platform

Draft JSON uses short keys:

t

tt

sg

d

m

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)

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the export workflow

SSE Event Handling

heartbeat

data:

~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 Codes

• 0

  — success, continue normally

• 1001

  — token expired or invalid; re-acquire via

  /api/auth/anonymous-token

• 1002

  — session not found; create a new one

• 2001

  — out of credits; anonymous users get a registration link with

  ?bind=<id>

  , registered users top up

• 4001

  — unsupported file type; show accepted formats

• 4002

  — file too large; suggest compressing or trimming

• 400

  — missing

  X-Client-Id

  ; generate one and retry

• 402

  — free plan export blocked; not a credit issue, subscription tier

• 429

  — rate limited; wait 30s and retry once

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these images into a smooth animated video with transitions" — 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.

Common Workflows

Quick edit: Upload → "turn these images into a smooth animated video with transitions" → Download MP4. Takes 30-60 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.