Midjourney Video

Treat Midjourney Video as a human-operated creative service, not a developer API. Prepare inputs, motion direction, settings, budget, and acceptance criteria; then hand the approved plan to the subscribed account owner for manual execution on midjourney.com or in Discord.

Keep the interface boundary absolute

As of 2026-07-10, Midjourney's official Community Guidelines say it does not provide an API except for rare explicitly granted exceptions and prohibits automated tools, third-party scripts, and automated interaction. The current Terms also prohibit automated access and one account may be used by only one person.

Therefore:

• Do not write or run browser automation, Discord self-bots, reverse-engineered HTTP calls, cookie/token replay, scraping, queued submission scripts, or unofficial “Midjourney API” clients.
• Do not ask for account credentials, session cookies, Discord tokens, or remote control of the user's session.
• Do not call a third-party gateway an official Midjourney API. Do not send content to one without separate user approval and a terms/privacy review.
• Do not promise unattended backend integration, webhooks, deterministic job submission, programmatic seeds, or an SLA.
• Route requirements for supported programmatic generation to a provider with a documented public API. Use this skill only for planning and a manual operator handoff unless the customer can show an explicit written Midjourney automation exception.

Never perform the manual UI steps yourself. A human operator must inspect the account state, approve the visible GPU-time impact, submit the job, choose candidates, extend, and download.

Treat that manual execution as a revision-bound authorization, not delegated autonomy. Freeze the exact handoff text, input hashes, settings, prompt, submission count, and Fast-minute cap before approval. Approval covers only that revision and those listed submissions. Any operator edit, changed account state, extra variation or extension, visibility mismatch, or undocumented UI behavior voids the approval and requires a new handoff.