> Got video clips to work with? Send it over and tell me what you need — I'll take care of the free HD video creation.
Try saying:
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.
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.https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer , Content-Type: application/json, and body {"task_name":"project","language":""} . 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.
Drop your video clips in the chat and tell me what you need. I'll handle the free HD video creation on cloud GPUs — you don't need anything installed locally.
Here's a typical use: you send a a 60-second raw video clip, ask for make a free HD video with transitions and music, 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 clips under 2 minutes render fastest at full 1080p.
User prompts referencing maker free hd, 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 | ❌ |
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":". 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/ | POST | Upload a file (multipart) or URL. |
/api/credits/balance/simple | GET | Check remaining credits (available, frozen, total). |
/api/state/nemo_agent/me/ | GET | Fetch current timeline state (draft, video_infos, generated_media). |
/api/render/proxy/lambda | POST | Start export. Body: {"id":"render_. Poll status every 30s. |
Accepted file types: 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 | maker-free-hd |
X-Skill-Version | frontmatter version |
X-Skill-Platform | auto-detect: clawhub / cursor / unknown from install path |
All requests must include: Authorization: Bearer , X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.
0 — success, continue normally1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token1002 — session not found; create a new one2001 — out of credits; anonymous users get a registration link with ?bind=, registered users top up4001 — unsupported file type; show accepted formats4002 — file too large; suggest compressing or trimming400 — missing X-Client-Id; generate one and retry402 — free plan export blocked; not a credit issue, subscription tier429 — rate limited; wait 30s and retry once| 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.
The backend responds as if there's a visual interface. Map its instructions to API calls:
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)
Quick edit: Upload → "make a free HD video with transitions and 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.
The backend processes faster when you're specific. Instead of "make it look better", try "make a free HD video with transitions and music" — 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.
共 1 个版本