Production is a system, not a prompt
A single public manual for MYEQ Studio, the Production API and MCP — with the same vocabulary in all eight supported languages.
Use MYEQ Studio
Learn the production method: define, plan, generate, verify, correct and approve.
Build with MYEQ
Integrate the same production authority through the HTTP API or MCP.
Workspace
Team, roles, access, credits, projects and activity.
Skills
Your methodology, visual language, rules and delivery standards.
Project
Objective, format, audience, brief and references.
Script
Narrative, structure, scenes, dialogue and rhythm.
Storyboard
Shots, camera, duration, characters, location and audio.
Entities + references
Characters, products, wardrobe, locations, voices and images.
Production
Image, I2V, A2V, V2V, voice, music and SFX.
QA
Identity, continuity, composition, audio and stability.
Repair
New Take, Retake, Inpaint, new audio or new references.
Editor
Assembly, cuts, layers, audio, timing and versions.
Approval
Generated is not certified: the team records final approval.
Start here
MYEQ is a production operating system. Reliable work comes from defining context and standards before paid generation, then verifying and repairing only what failed.
The core rule
The user owns creative intent. MYEQ owns operational competence. The platform should make the correct professional workflow the easiest workflow.
Two audiences, one product
Use MYEQ Studio if you are producing interactively. Use the API or MCP if you are automating the same production authority. Do not invent different project, billing or approval semantics for each interface.
24, 30 and 60 FPS in Studio, API and MCP
Use the same committed scene snapshot and exact admission across all three interfaces. Requested FPS is preserved; there is no automatic fallback to 24 FPS. Availability depends on the approved worker and the exact scene.
START/END canvases: 704×1280, 1280×704 or 960×960. I2V accepts generated audio or no audio; A2V requires authorized source audio and preserves its selected offset. Ingredients and V2V do not gain high FPS support from this table. Seeds are integers from 0 to 2147483647. I2V and A2V support END without START at 24, 30 and 60 FPS only when the deployed service explicitly admits it. END guides the final frame; the beginning is generated from the prompt. Leave start empty and keep the image in end. This does not promise identical pixels or reverse the video. A2V always needs authorized source audio and at least one START or END image; audio alone is not admitted.
| FPS | Admitted class | Physical limits |
|---|---|---|
| 24 | Default; selected modality must pass its own admission | Duration, audio and references depend on the selected native class |
| 30 | Approved I2V / A2V only | 720p · 2–10 whole seconds · 9:16 / 16:9 / 1:1 · I2V/A2V: START and/or END; A2V also requires source audio |
| 60 | Approved I2V / A2V only | 720p · 2–10 whole seconds · 9:16 / 16:9 / 1:1 · I2V/A2V: START and/or END; A2V also requires source audio |
Save, preflight the quote, then confirm one scene
Create or read the authorized project, commit the scene with PATCH expectedVersion, then send the same snapshot and targetSceneId to /api/v1/production/snapshots/preflight-scene. Inspect data.ready, issues and estimatedCredits; this creates no job or credit reservation. Generate through /api/v1/production/snapshots/generate-scene with confirm=true and a stable Idempotency-Key. Poll the returned jobId. MCP uses myeq.video.preflight_scene and myeq.video.generate_scene with the same snapshot; paid submission never retries automatically. Scene settings override project defaults; preserve matching frozen sceneContracts.
Legacy /video/start, /video/create, /video/create-job and /video/preflight are retired: default/24 returns 410; 30/60 requires snapshot migration with 422. 25/48/50 are unsupported. Preflight failure never changes cadence or charges credits. A successful check does not reserve availability or wallet balance.