Production API overview
The HTTP API exposes the same provider-neutral production authority used by MYEQ Studio.
The public documentation is shareable, but API and MCP capability availability is governed by the live product manifest and account access. Foundation or experimental operations are not stability promises.
One lifecycle
Context → Plan → Preflight → Execute → Inspect → Decide → Repair → Certify → Deliver is the long-lived semantic model. Not every stage is currently stable; read the live product manifest before assuming availability.
Plan before spending
Planning compiles creative intent into an inspectable proposal. It should not dispatch paid generation. Preflight then verifies access, references, capabilities and budget.
curl -X POST https://myeq.pro/api/v1/production/plans \
-H "Authorization: Bearer $MYEQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"projectId": "project-123",
"script": "Create a 60-second vertical trailer",
"vertical": "ai_film",
"sourceLanguage": "en",
"responseLanguage": "es",
"dialogueLanguage": "es",
"visualPromptLanguage": "en"
}'Execution is durable
Paid execution returns durable authority owned by MYEQ. A client disconnect must not cancel or duplicate accepted work. Read job status instead of depending on the caller process staying alive.
Public contracts are provider-neutral
Clients choose production intent and MYEQ capabilities, not private deployment runtimes or retired provider names. Implementation details stay behind adapters.