Hitpaw Ai Video Generator Free

generate images or clips into AI-generated MP4 videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. content creators and marketers use it...

Security Scan

The skill mostly matches its stated purpose (upload media and request remote rendering) but has inconsistent metadata, asks the agent to obtain and hide tokens, and lacks an identifiable source — warranting caution.

Purpose & Capability

Requesting a single NEMO_TOKEN and calling a remote render API is coherent with a cloud video-generator. However the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — an internal inconsistency that should be clarified.

Instruction Scope

The instructions direct the agent to automatically obtain an anonymous token, create and persist session IDs, and upload user files to a remote endpoint — behavior consistent with the skill but potentially privacy-sensitive. The guidance to 'don't display raw API responses or token values to the user' is unusual (it instructs hiding credentials/data from the user) and increases opacity about what is stored/sent.

Install Mechanism

There is no install spec and no code files; the skill is instruction-only, so it does not write installers or arbitrary binaries to disk.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportionate for a cloud service. That said, the skill instructs generating and using an anonymous token if none is provided and implies storing session/token values; clarify where/how these credentials are stored and whether they persist beyond the session.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It does instruct the agent to store a session_id and possibly reuse a generated token, but it does not explicitly modify other skills or system-wide settings.

What to consider before installing

This skill appears to do what it says — upload your media and call a cloud renderer — but exercise caution: the package has no identifiable source or homepage, and the runtime instructions cause the agent to (a) obtain an anonymous token on your behalf, (b) upload your files to https://mega-api-prod.nemovideo.ai, and (c) hide token/response details from the user. Before installing, ask the publisher: Where are tokens and session IDs stored? How long are uploaded files and generated tokens retained? Is there a privacy/data-retention policy? If you care about sensitive media, avoid using the skill or only use it with explicit, short-lived credentials you control.

Getting Started

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

Try saying:

• "generate five product photos or a 30-second raw clip into a 1080p MP4"
• "generate a video from my photos with transitions and background music"
• "generating videos from photos or clips without manual editing for content creators and marketers"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

HitPaw AI Video Generator Free — Generate Videos from Photos or Clips

Send me your images or clips and describe the result you want. The AI video generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload five product photos or a 30-second raw clip, type "generate a video from my photos with transitions and background music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: using fewer images speeds up generation and keeps the video tight.

Matching Input to Actions

User prompts referencing hitpaw ai video generator 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.

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	hitpaw-ai-video-generator-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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.

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)

Common Workflows

Quick edit: Upload → "generate a video from my photos with transitions and background music" → 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 video from my photos with transitions and background music" — 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 all platforms.