Developers

Genjutsu API

A documentation-style overview of how a motion transfer API could work. No live integration is claimed here.

API · Motion Transfer · AI Video

What is Genjutsu API?

A programmatic interface for character + reference video → motion transfer → AI video. Useful for apps that need automated short-form generation.

API workflow

Authenticate → submit character + reference → poll or webhook for completion → download output video.

Input

Character image or identity pack, reference video file/URL, optional prompts for restyle, and output constraints.

Output

Rendered MP4/WebM (or job metadata). Exact formats depend on the upstream provider you integrate.

Authentication

Expected pattern: API keys or OAuth scoped to a project. Do not embed secrets in client-side apps.

Pricing / availability

Availability and pricing depend on the underlying video provider. This site does not sell API access today.

Example shape

// Illustrative only — not a real endpoint
POST /v1/motion-transfer
{
  "character": { "image_url": "..." },
  "reference": { "video_url": "..." },
  "options": { "duration_sec": 4 }
}

// Response (async job)
{ "job_id": "mt_...", "status": "queued" }

FAQ

Is there a live Genjutsu API on this site?

Not yet. This page documents the intended workflow shape for developers. No keys, endpoints or fake responses are provided.

What would a Genjutsu API accept?

Typically a character asset (image or identity reference), a motion reference video, and generation options such as duration or output size.

What would it return?

A generated video asset URL or job ID for async rendering, plus status for long-running generations.