Getting Started

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

Try saying:

• "compress my video files"
• "export 1080p MP4"
• "compress this video to under 8MB"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If

NEMO_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

{"task_name":"project","language":"en"}

session_id

Tell the user you're ready. Keep the technical details out of the chat.

Video Compressor for Discord — Compress Videos for Discord Sharing

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

Here's a typical use: you send a a 120MB gameplay clip recorded on OBS, ask for compress this video to under 8MB so I can send it in Discord, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — targeting under 8MB works for free Discord accounts; 25MB works for Nitro users.

Matching Input to Actions

User prompts referencing video compressor discord, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

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

/api/tasks/me/with-session/nemo_agent

{"task_name":"project","language":"<lang>"}

session_id

/run_sse

app_name

session_id

new_message

Accept: text/event-stream

/api/upload-video/nemo_agent/me/<sid>

/api/credits/balance/simple

available

frozen

total

/api/state/nemo_agent/me/<sid>/latest

draft

video_infos

generated_media

/api/render/proxy/lambda

{"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source

  :

  video-compressor-discord

• X-Skill-Version

  : from frontmatter

  version

• X-Skill-Platform

  : detect from install path (

  ~/.clawhub/

  →

  clawhub

  ,

  ~/.cursor/skills/

  →

  cursor

  , else

  unknown

  )

Include

Authorization: Bearer <NEMO_TOKEN>

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:

About 30% of edit operations close the stream without any text. When that happens, poll

/api/state

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 field mapping:

t

tt

sg

d

m

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 → "compress this video to under 8MB so I can send it in Discord" → Download MP4. Takes 20-40 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "compress this video to under 8MB so I can send it in Discord" — concrete instructions get better results.

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

H.264 codec gives the best balance of quality and size for Discord sharing.