Getting Started

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

Try saying:

• "generate a short description of a Jesus sermon scene or Bible verse image into a 1080p MP4"
• "create a video of Jesus delivering the Sermon on the Mount with narration"
• "generating AI videos of Jesus for religious or educational content for pastors, ministry creators, religious educators"

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

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.

Jesus AI Video Generator Free — Generate Jesus-themed videos free

Drop your text prompts or images in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short description of a Jesus sermon scene or Bible verse image, ask for create a video of Jesus delivering the Sermon on the Mount with narration, 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 scene descriptions produce more focused and accurate AI video results.

Matching Input to Actions

User prompts referencing jesus ai video generator free, 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.

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

X-Skill-Source

jesus-ai-video-generator-free

X-Skill-Version

version

X-Skill-Platform

clawhub

cursor

unknown

Every API call needs

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 JSON uses short keys:

t

tt

sg

d

m

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a video of Jesus delivering the Sermon on the Mount with narration" — concrete instructions get better results.

Max file size is 200MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across church presentation software and social media.

Common Workflows

Quick edit: Upload → "create a video of Jesus delivering the Sermon on the Mount with narration" → 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.