Ai Video Generator Free Kapwing

Turn a 200-word blog post or script into 1080p ready-to-share videos just by typing what you need. Whether it's generating videos from text or clips without...

Security Scan

The skill's runtime instructions mostly match a NemoVideo API integration, but the package name/description falsely implies Kapwing and there are a few metadata/instruction inconsistencies that warrant caution.

Purpose & Capability

The skill is named and marketed as 'Kapwing', but every API endpoint in SKILL.md points to mega-api-prod.nemovideo.ai (NemoVideo). Rebranding or impersonation risk: a user expecting an official Kapwing integration would be misled. Also the SKILL.md frontmatter declares a configPath (~/.config/nemovideo/) but the registry metadata reported no required config paths—an internal inconsistency.

Instruction Scope

Instructions direct the agent to obtain/use a NEMO_TOKEN (or request an anonymous token), create sessions, POST SSE messages, upload local files (multipart -F "files=@/path"), poll render endpoints, and include custom attribution headers. Uploading local files and polling state are expected for a video service, but the doc also suggests detecting an install path (~/.clawhub/ or ~/.cursor/skills/) to set X-Skill-Platform which implies filesystem checks not declared elsewhere. The skill further instructs keeping technical details out of chat (internalizing API calls) — reasonable for UX but reduces transparency.

Install Mechanism

Instruction-only skill with no install spec and no code files. Nothing is written to disk by an installer in the package itself.

Credentials

Only one credential (NEMO_TOKEN) is required which is proportionate for the documented NemoVideo API. The skill can also obtain an anonymous token if none is provided. However, the mismatch between the skill name (Kapwing) and the required NEMO_TOKEN invites extra scrutiny: the token grants access to an external video-rendering service, so users should confirm they intend to grant that service access.

Persistence & Privilege

always:false and no install hooks are present. The skill will run at invocation and can act autonomously (default), but it does not request permanent 'always' inclusion or make changes to other skills' configs.

What to consider before installing

This skill appears to call NemoVideo APIs (mega-api-prod.nemovideo.ai) even though its name/description advertise 'Kapwing' — that mismatch is the primary red flag. Before installing: 1) Confirm you actually want your agent to talk to NemoVideo (not Kapwing). 2) Be careful uploading private files — the skill will send files to the remote service and may generate anonymous tokens for 7 days if you don't provide a NEMO_TOKEN. 3) Prefer supplying your own NEMO_TOKEN if you trust the service; otherwise decline to share credentials. 4) Ask the publisher for source/homepage and clarification on why the skill name references Kapwing. 5) If you want to avoid any local filesystem checks, verify how your agent implements the skill (does it inspect install paths?). These inconsistencies look like sloppy or misleading packaging rather than clearly malicious behavior, but verify provenance and privacy policies before use.

Getting Started

Send me your text or clips and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "generate a 200-word blog post or script into a 1080p MP4"
• "turn this script into a short video with visuals and captions"
• "generating videos from text or clips without manual editing for content creators and students"

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.

AI Video Generator Free Kapwing — Generate Videos from Text Free

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

Here's a typical use: you send a a 200-word blog post or script, ask for turn this script into a short video with visuals and captions, 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 scripts under 60 seconds produce faster and cleaner results.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-video-generator-free-kapwing, 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).

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

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.

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this script into a short video with visuals and captions" — 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 social platforms.

Common Workflows

Quick edit: Upload → "turn this script into a short video with visuals and captions" → 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.