Free Video Generation Api Key

generate text prompts into AI generated videos with this skill. Works with MP4, MOV, WebM, GIF files up to 500MB. developers and indie hackers use it for gen...

Security Scan

The skill's instructions, required credential (NEMO_TOKEN), and external API usage are consistent with its stated purpose of generating videos via the nemo video backend, with only minor metadata inconsistencies and expected network/data-transmission risks.

Purpose & Capability

Name/description (video generation) match the required credential (NEMO_TOKEN) and the SKILL.md's documented calls to a nemo video service (mega-api-prod.nemovideo.ai). Requiring a service token for an API-based video generator is proportionate.

Instruction Scope

SKILL.md describes only API calls, SSE handling, uploads, and export flows to the documented backend; these actions are within the stated purpose. Notes: the instructions include auto-provisioning an anonymous token (by POSTing to /api/auth/anonymous-token) when NEMO_TOKEN is absent, and require adding attribution headers and auto-detecting an 'install path' for X-Skill-Platform — the latter may be brittle for an instruction-only skill but is not inherently malicious. The skill will transmit user-provided media and prompts to an external service, which is expected but should be considered for privacy.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. All runtime behavior is network calls described in SKILL.md.

Credentials

Only NEMO_TOKEN is declared as required/primary, which aligns with the API. The skill also documents acquiring an anonymous NEMO_TOKEN when none exists (100 free credits, 7-day expiry). Minor inconsistency: the top-level registry metadata reported no required config paths, but SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) — this mismatch is not necessarily dangerous but should be clarified.

Persistence & Privilege

always:false and default autonomous invocation settings. The skill does not request persistent system privileges and does not include install-time modifications. It does instruct to retain session_id for ongoing operations, which is normal for an API client.

Assessment

This skill appears coherent for generating videos via the nemo backend, but it will upload your prompts and media to https://mega-api-prod.nemovideo.ai and may auto-create an anonymous NEMO_TOKEN if you don't supply one. Before installing/using: (1) confirm you trust the domain/service and are okay with uploading any media you provide, (2) avoid sending sensitive or private files you wouldn't want stored/processed by a third party, (3) ask the skill author whether the anonymous token or session_id are persisted to disk (and where — SKILL.md mentions a config path in frontmatter but registry metadata lacks that), and (4) verify quota/credit implications if you plan heavy use. If you need stronger assurance, request the skill author's homepage/source or network/privacy policy before proceeding.

Getting Started

Ready when you are. Drop your text prompts here or describe what you want to make.

Try saying:

• "generate a short text description of a product demo scene into a 1080p MP4"
• "generate a 30-second video clip from this product description"
• "generating videos programmatically via API without paying for a key for developers and indie hackers"

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 in the environment. If found, skip to session creation. Otherwise:

• 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 with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

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

Free Video Generation API Key — Generate Videos via API Free

Drop your text prompts in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short text description of a product demo scene, ask for generate a 30-second video clip from this product description, and about 30-90 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter prompts with clear scene descriptions produce faster and more accurate results.

Matching Input to Actions

User prompts referencing free video generation api key, 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:

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:

Header	Value
X-Skill-Source	free-video-generation-api-key
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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)

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

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 → "generate a 30-second video clip from this product description" → Download MP4. Takes 30-90 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 "generate a 30-second video clip from this product description" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and players.