Automation and public API

Experimental

The public API and published automation skills can change. Keep a tested version of your workflow, inspect current schemas, and start in a non-critical project with a minimal render.

Superluminal publishes experimental automation guidance in the sulu-skills repository. It covers API, render, storage, production, and Market skills. For Blender-native submission, it recommends Blender MCP plus the Superluminal add-on.

Choose the right path

Blender add-on

The best path when an artist submits a scene. It integrates dependency tracing, add-on packing, upload modes, version choice, the progress terminal, project jobs, and output download.

Experimental API

For automated systems where you own the full lifecycle: authentication, schema validation, project and organization resolution, file preparation, retries, monitoring, budget controls, and output handling.

Safety for render submission

Creating a render job costs money, and a retry of the same create request can create a second job. An automated workflow must:

1. Generate a client-side operation ID and save it before the request.
2. Record the organization, project, input, frame range, settings, and expected maximum spend.
3. Treat a timeout as an unknown result. Search for the job and reconcile before any retry.
4. Require explicit confirmation for each new billable submission.
5. Cap concurrency and monitor the live organization balance.
6. Log response identifiers. Never log tokens or signed URLs.
7. Verify one representative output before scaling up the range.

Authentication hygiene

• Store API credentials in a secret manager or ignored local credential store.
• Never put a token in source, MDX, a screenshot, a command transcript, or a support message.
• Scope credentials and organizations as narrowly as the current API supports.
• If a credential was possibly exposed, rotate it.
• Redact credential-bearing URLs and request headers from observability.

Version and schema discipline

Read the current repository instructions and live schemas before you implement. Validate both success and error responses. Fail closed on unknown destructive or billable fields. Add contract tests for the exact API version your workflow expects.

• sulu-skills: Read the current experimental workflows and safety notes at the source.
• Blender submission: Use the integrated production path when a scene starts in Blender.
• Product availability: Check what is shipped, experimental, or still a preview.