Video To Text Online Free

convert video files into text transcripts with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. students, journalists, content creators use it f...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video→transcript service: it needs a single service token, uploads user videos to a remote API, and has no install-time code — nothing indicates covert behavior, but it will send your videos to an external provider and read a couple of local paths for attribution.

Purpose & Capability

The skill is a cloud-backed video transcription/export tool and requests a single NEMO_TOKEN credential and network access to mega-api-prod.nemovideo.ai, which matches the described purpose. One small inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) and platform-detection by install path for attribution, while the registry metadata summary noted no required config paths — this is likely benign but worth noting.

Instruction Scope

The runtime instructions stick to uploading videos, creating sessions, streaming SSE chat, polling for render status, and exporting downloads. They also instruct the agent to read this file's YAML frontmatter and to detect install path patterns (e.g., ~/.clawhub, ~/.cursor/skills/) for X-Skill-Platform attribution. Reading the skill's own frontmatter is expected; probing a couple of standard install paths is minor but does broaden filesystem access beyond pure network I/O. The skill correctly avoids exposing tokens in user-visible output and describes re-auth flows.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only, so nothing is downloaded or written to disk by an installer. This is the lowest-risk install pattern.

Credentials

Only one credential is declared (NEMO_TOKEN) as the primary credential. The instructions also implement an anonymous-token flow if no token is present (POST to the service to obtain a short-lived token). Requiring a single service token is proportionate for a cloud transcription/export service.

Persistence & Privilege

The skill is not always-enabled and makes no requests to modify other skills or system-wide settings. It operates on-demand and uses a session token for operations; no elevated persistence privileges are requested.

Assessment

This skill uploads user video files to an external API (mega-api-prod.nemovideo.ai) to produce transcripts and rendered MP4s — that is the intended behavior. Before installing, consider: (1) Do you trust this third-party service with the videos you will upload? Avoid uploading sensitive or regulated content unless you confirm their privacy/security policies. (2) The skill will use a NEMO_TOKEN if provided, or obtain an anonymous short-lived token automatically; if you prefer explicit control, provide your own token instead of letting the skill request one. (3) The skill may check a couple of common local install paths for attribution metadata (non-sensitive), which is minor filesystem access. If any of these behaviors are unacceptable, do not install; otherwise the skill appears coherent for its stated purpose.

Getting Started

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

Try saying:

• "convert my video files"
• "export 1080p MP4"
• "transcribe this video to text and"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Video to Text Online Free — Convert Video Speech to Text

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

Say you have a 10-minute interview recording and want to transcribe this video to text and export the transcript — the backend processes it in about 30-90 seconds and hands you a 1080p MP4.

Tip: shorter clips under 5 minutes transcribe faster and with higher accuracy.

Matching Input to Actions

User prompts referencing video to text online 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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-to-text-online-free
• 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> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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

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.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "transcribe this video to text and export the transcript" — concrete instructions get better results.

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

Upload MP4 for the most reliable transcription results.

Common Workflows

Quick edit: Upload → "transcribe this video to text and export the transcript" → 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.