Free Video Generation Ai Online

Turn a short text description like 'a sunset over mountains with calm music' into 1080p AI generated videos just by typing what you need. Whether it's genera...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-generation agent: it needs a NEMO_TOKEN (or can obtain an anonymous token), makes API calls to a remote render service, and may read its own frontmatter and user upload files — nothing appears intentionally deceptive, but there are small inconsistencies and expected privacy considerations to review.

Purpose & Capability

The skill's name/description (text→video generation) aligns with required artifacts: a single NEMO_TOKEN credential and API calls to a remote video-rendering service. Minor inconsistency: the registry metadata listed no required config paths, but the SKILL.md frontmatter declares a configPaths entry (~/.config/nemovideo/). This difference is likely a metadata mismatch but should be reconciled.

Instruction Scope

SKILL.md instructs the agent to use NEMO_TOKEN (or obtain an anonymous token via POST to the vendor API), create sessions, post SSE messages, upload user files (multipart), poll render endpoints, and read the skill's YAML frontmatter to populate attribution headers. These actions are within the stated purpose (rendering videos) but do require filesystem access for uploads and reading the skill file; the agent is also instructed to detect install path to set X-Skill-Platform — this filesystem probing is peripheral to core functionality and worth noting.

Install Mechanism

There is no install spec and no code files — instruction-only skill. This is low-risk from an installation perspective because nothing is downloaded or written to disk by an installer.

Credentials

Only one credential is declared (NEMO_TOKEN) and it is appropriate for a cloud API service. The SKILL.md's fallback behavior (obtain an anonymous token) is coherent. No unrelated secrets or broad credential access are requested.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide persistence. It does instruct reading its own metadata and detecting install location to set an attribution header, which is limited in scope and not an elevation of privilege.

Assessment

This skill appears to do what it says: it will call an external API (mega-api-prod.nemovideo.ai) to generate videos. Before installing, consider: 1) only provide a NEMO_TOKEN if you trust the service — the token grants the skill authorization to act on your behalf; 2) the skill may upload files you provide (video/image/audio) and will read its own skill file and detect install path to add attribution headers; 3) if you don't provide NEMO_TOKEN, the skill will request an anonymous token that grants temporary credits — that involves contacting the vendor endpoint; 4) there is a small metadata mismatch about config paths between registry and SKILL.md that should be clarified. If you have privacy or network policy concerns, avoid supplying a permanent token and review network access to the external domain.

Getting Started

Share your text prompts or images and I'll get started on AI video generation. Or just tell me what you're thinking.

Try saying:

• "generate my text prompts or images"
• "export 1080p MP4"
• "generate a 30-second video from my"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Free Video Generation AI Online — Generate Videos from Text Free

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

Say you have a short text description like 'a sunset over mountains with calm music' and want to generate a 30-second video from my product description with background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter, more specific prompts produce more accurate and usable video results.

Matching Input to Actions

User prompts referencing free video generation ai online, 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.

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: free-video-generation-ai-online
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Common Workflows

Quick edit: Upload → "generate a 30-second video from my product description with background music" → Download MP4. Takes 1-2 minutes 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 "generate a 30-second video from my product description with background music" — concrete instructions get better results.

Max file size is 200MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across social platforms and devices.