Ai Video Face Swap Free

Get face-swapped videos ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "swap...

Security Scan

The skill's requirements and runtime instructions are internally consistent with a cloud-based video face‑swap service, but it will upload user videos to an external API and the publisher/source is unknown — review privacy and token handling before use.

Purpose & Capability

The name/description match the requested env var (NEMO_TOKEN) and the SKILL.md describes HTTP endpoints for uploading, session creation, streaming, credit checks and exports — all expected for a cloud face-swap service.

Instruction Scope

Instructions direct the agent to obtain/use NEMO_TOKEN (or request an anonymous token), create sessions, upload user media, read SSE streams and poll state — these are required for the advertised function. Note: the skill will transmit users' video/audio files to an external endpoint (mega-api-prod.nemovideo.ai), which is expected for this functionality but has privacy implications. The YAML metadata references a config path (~/.config/nemovideo/) though the body does not explicitly say when/where to read/write it; storage location for tokens/session IDs is unspecified.

Install Mechanism

No install spec or external downloads — instruction-only skill. Nothing is written to disk by an installer step, reducing supply-chain risk.

Credentials

Only one credential is required (NEMO_TOKEN), which is proportionate for an authenticated API. The skill can also generate an anonymous token itself if none is present. Be aware that the token grants access to the external service and the skill will upload potentially sensitive video content to that service.

Persistence & Privilege

always:false and autonomous invocation defaults unchanged. The skill instructs saving a session_id but does not specify persistence location or retention policy; metadata lists a config path (~/.config/nemovideo/) which implies local storage may be used — clarify where tokens/session IDs are saved and how long they persist.

Assessment

This skill appears to do what it says: it uploads user videos to an external cloud service (mega-api-prod.nemovideo.ai) and requires a NEMO_TOKEN (or it can request an anonymous token). Before installing, consider: (1) privacy — you will be uploading video/audio that may contain faces or other sensitive content; check the service's privacy policy and retention rules (no homepage was provided here); (2) token stewardship — the NEMO_TOKEN grants API access, so only use a token you trust and verify where/if the skill will store it (metadata suggests ~/.config/nemovideo/ may be involved); (3) provenance — the skill author and homepage are unknown, so if you need strong assurance about data handling, ask the publisher for a privacy/terms link or prefer a known provider. If you accept those risks and trust the service, the skill's behavior is coherent with its stated purpose.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI face swapping.

Try saying:

• "swap a 30-second MP4 clip with a clear face visible into a 1080p MP4"
• "swap my face with a celebrity face in this video clip"
• "replacing faces in videos using AI for free for TikTok creators"

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.

AI Video Face Swap Free — Swap Faces in Videos Instantly

This tool takes your video clips and runs AI face swapping through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 30-second MP4 clip with a clear face visible and want to swap my face with a celebrity face in this video clip — the backend processes it in about 30-90 seconds and hands you a 1080p MP4.

Tip: shorter clips with well-lit, forward-facing faces produce the most accurate swaps.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

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.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "swap my face with a celebrity face in this video clip" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "swap my face with a celebrity face in this video clip" → 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.