Free Text To Video Api

Turn a 50-word product description paragraph into 1080p AI-generated videos just by typing what you need. Whether it's generating videos automatically from w...

Security Scan

The skill is mostly coherent with a text→video API but has a few inconsistencies and privacy/surprise behaviors (automatic anonymous token creation, metadata claiming a config path) you should understand before installing.

Purpose & Capability

The skill's name/description match the runtime instructions: it talks to a remote Nemo video API and needs a NEMO_TOKEN. However the SKILL.md frontmatter advertises a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — a minor mismatch that should be clarified.

Instruction Scope

Instructions are focused on interacting with the external mega-api-prod.nemovideo.ai endpoints (session creation, SSE chat, upload, export). They require reading the skill's frontmatter and detecting the install path to set attribution headers; this is reasonable for attribution but does read local install path information. The skill will automatically obtain an anonymous token via the API if NEMO_TOKEN is not present, which means it can start sending user content to the remote service without the user supplying credentials explicitly.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk; nothing is downloaded or written by an installation script.

Credentials

Only a single env var (NEMO_TOKEN) is declared, which is proportionate. Concern: the skill will auto-create/refresh an anonymous NEMO_TOKEN by calling the provider endpoint if none exists (tokens last 7 days, 100 free credits). This automatic credential acquisition and use may be surprising and results in user data being sent to the provider without an explicit credential from the user. Also the frontmatter's configPaths claim implies the skill may read or expect local config at ~/.config/nemovideo/.

Persistence & Privilege

always is false and there is no install-time persistence or cross-skill configuration. The skill can be invoked autonomously (default), which is expected behavior for skills.

What to consider before installing

This skill appears to do what it says (call a cloud video generation API) but it will contact an external service and can automatically obtain and use an anonymous token if you don't provide NEMO_TOKEN. Before installing: (1) be aware any text or uploaded files may be transmitted to https://mega-api-prod.nemovideo.ai and processed there; (2) if you don't want automatic token generation, provide a controlled NEMO_TOKEN or avoid installing; (3) confirm you’re comfortable with the service's privacy/terms and any billing or credit model; (4) ask the owner to clarify the mismatched configPath claim (~/.config/nemovideo/) in the SKILL.md frontmatter. If you need stronger guarantees, test with non-sensitive data and a disposable token first.

Getting Started

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

Try saying:

• "convert my text prompts"
• "export 1080p MP4"
• "convert this product description into a"

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 Text to Video API — Convert Text Into Generated Videos

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 50-word product description paragraph, ask for convert this product description into a 30-second promotional video, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter, clearer text prompts produce more accurate and focused video output.

Matching Input to Actions

User prompts referencing free text to video api, 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.

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

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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 → "convert this product description into a 30-second promotional video" → 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 "convert this product description into a 30-second promotional video" — concrete instructions get better results.

Max file size is 500MB. Stick to TXT, DOCX, JSON, CSV for the smoothest experience.

Export as MP4 for widest compatibility across platforms and players.