Video Ai Generator Free Credits

Turn a 30-second product clip or five brand images into 1080p AI generated videos just by typing what you need. Whether it's generating polished videos from...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-generation integration: it asks for one service token (NEMO_TOKEN), uploads media, and calls the listed API endpoints; nothing requested appears unrelated to its stated purpose.

Purpose & Capability

Name/description, required env var (NEMO_TOKEN), and the SKILL.md's API endpoints all align: the skill uploads media, starts sessions, streams SSEs, checks credits, and exports MP4s. There are no unrelated credentials or binaries requested.

Instruction Scope

Instructions are focused on interacting with the nemovideo API (anonymous-token flow, session creation, SSE, upload, export, credit queries). A minor out-of-band behavior: it instructs reading the skill's YAML frontmatter at runtime and detecting an install path string to set X-Skill-Platform — this requires accessing the skill file path but is plausible for attribution. The SKILL.md also says to 'save session_id' (state persistence) but does not mandate reading unrelated files or environment variables.

Install Mechanism

No install spec and no code files — instruction-only skill. This is the lowest-risk install mechanism; nothing is downloaded or written by an installer.

Credentials

Only one credential is required (NEMO_TOKEN / primaryEnv) which is appropriate for a cloud API client. Metadata lists a config path (~/.config/nemovideo/) which fits storing token/session state; no unrelated secrets are requested.

Persistence & Privilege

always:false and model invocation allowed (defaults). The skill indicates it will obtain/keep a session_id and may use ~/.config/nemovideo/ for state; this is reasonable for session persistence but users should be aware tokens/session identifiers may be stored by the agent if implemented that way.

Assessment

This skill behaves like a normal cloud-video integration: it needs a NEMO_TOKEN (or will obtain an anonymous temporary token) and will upload whatever media you provide to the nemovideo API domain. Before enabling: (1) confirm you trust https://mega-api-prod.nemovideo.ai and its privacy policy, (2) avoid uploading sensitive content until you’re comfortable with the service, (3) prefer using an ephemeral or limited token rather than a long-lived account token, and (4) be aware the agent may persist session state (session_id / tokens) under ~/.config/nemovideo/ or similar if implemented. If you want higher assurance, test with non-sensitive sample files and monitor network calls or inspect where/if the agent stores tokens.

Getting Started

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

Try saying:

• "generate my video clips or images"
• "export 1080p MP4"
• "generate a short promotional video with"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video AI Generator Free Credits — Generate AI Videos, Export MP4

This tool takes your video clips 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 30-second product clip or five brand images and want to generate a short promotional video with music and transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: using shorter source clips under 60 seconds speeds up generation and uses fewer credits.

Matching Input to Actions

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

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

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

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

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.

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.

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

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)

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

Common Workflows

Quick edit: Upload → "generate a short promotional video with music and transitions" → 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 short promotional video with music and transitions" — concrete instructions get better results.

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

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