Free Online Video Generator Ai

Turn a short product description and three product photos into 1080p AI-generated videos just by typing what you need. Whether it's generating videos from te...

Security Scan

The skill's requested token and API usage align with a cloud video-generation use, but instructions to auto-create/store tokens, hide raw API responses, and read/write a config path without explicit user consent are concerning and deserve caution.

Purpose & Capability

The name/description claim cloud video generation from text/images, and the only required credential is NEMO_TOKEN which is exactly what a cloud backend would need. The declared config path (~/.config/nemovideo/) is plausible for storing session/token state, but it's not strictly necessary for basic API usage and therefore is somewhat unexpected.

Instruction Scope

SKILL.md instructs the agent to automatically obtain an anonymous token and create sessions, upload user files (images/video) to a remote API, and poll render endpoints — these are expected for a cloud render service. However, it also instructs 'Don't display raw API responses or token values to the user', which reduces transparency and could hide sensitive details or exfiltration. It also instructs deriving headers from the agent's install path (reading local environment) and storing session_id/token for future requests. The skill will transmit user files to an external service (mega-api-prod.nemovideo.ai); users should be aware that their media will leave their device.

Install Mechanism

Instruction-only skill with no install spec and no code files. This is the lowest install risk — nothing is downloaded or installed by the skill itself.

Credentials

Only NEMO_TOKEN is requested as an environment variable, which matches the described API usage. Oddly, the instructions will auto-generate and persist an anonymous NEMO_TOKEN when none is provided; requiring the env var but also creating one automatically is inconsistent but not necessarily malicious. Declared config path may be used to persist tokens/session IDs.

Persistence & Privilege

The skill will persist a token/session_id (it suggests storing state under ~/.config/nemovideo/) and auto-connect when first opened. While not marked always: true, automatic credential creation and storage enable ongoing access to the remote service until tokens expire or are revoked. Combined with the instruction to hide raw API responses, this persistence raises privacy and transparency concerns.

What to consider before installing

This skill appears to do what its name says (send your text/images to a cloud renderer and return an MP4), but it will: 1) automatically request an anonymous token from mega-api-prod.nemovideo.ai if NEMO_TOKEN is not present, 2) upload your media files to that remote service, and 3) store the token/session state under ~/.config/nemovideo/ by default. The instruction to 'not display raw API responses or token values' reduces transparency — you won't see the raw token or backend replies. Before installing, consider: - Do you trust mega-api-prod.nemovideo.ai with your images and any metadata? Avoid uploading sensitive media. - If you want control, set NEMO_TOKEN yourself (so the skill cannot auto-create it) or block the skill from auto-connecting. - Inspect or restrict where persistent session data is written (the config path) and delete it when you stop using the skill. - If unsure about the service, ask for an explicit privacy/terms link or validate the domain externally. Proceed only if you accept that your media and generated tokens will be transmitted and stored by this third-party backend.

Getting Started

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

Try saying:

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

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.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Free Online Video Generator AI — Generate Videos from Text or Images

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

Say you have a short product description and three product photos and want to generate a 30-second promotional video from my text and images — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter text prompts with clear instructions produce more accurate results.

Matching Input to Actions

User prompts referencing free online video generator ai, 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 requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-online-video-generator-ai, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise 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

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.

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)

Common Workflows

Quick edit: Upload → "generate a 30-second promotional video from my text and images" → 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 promotional video from my text and images" — 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.