Getting Started

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

Try saying:

• "add a 3-minute YouTube tutorial video into a 1080p MP4"
• "add captions in English and Spanish with auto-sync"
• "adding subtitles to YouTube and social media videos for YouTubers and content 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.

How Video Subtitle Maker Works Here

This does AI subtitle generation for clip files. Everything runs server-side.

A quick walkthrough: upload a 3-minute YouTube tutorial video → ask for add captions in English and Spanish with auto-sync → wait roughly 30-60 seconds → download your MP4 at 1080p. The backend handles rendering, encoding, all of it.

Fair warning — shorter clips under 5 minutes generate subtitles significantly faster.

Request Routing

Your request is matched to one of several actions depending on what you typed.

The Processing Pipeline

Requests go to a cloud backend for GPU-accelerated rendering. A typical video subtitle maker job finishes in under a minute for short clips.

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

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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.

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)

Error Handling

Quick Start Guide

First time? Just upload a video files and describe what you need. I'll run it through NemoVideo's backend and hand you back a 1080p MP4.

Processing takes about 30-60 seconds depending on video length. You start with 100 free credits — most edits cost 1-3.

FAQ

How long does processing take? Depends on length — a 30-second clip finishes in 30-60 seconds, a 10-minute video might need 3-5 minutes.

What formats work? MP4, MOV, AVI, WebM on input. Output is always MP4.

Is there a file size limit? Yeah, 500MB. Compress or trim if you're over.

Do I need an account? Nope. You get 100 free credits on first use, no signup.