Skip to content
DEVELOPERS / COMING SOON

Your pipeline.
More possibilities.

We’re shaping how Cleom could fit into studio tools. Start with the creative workflow, then help us understand the integration you need.

●   THE APP IS AVAILABLE TODAY

Submit briefs and review deliveries through the Cleom workspace. Public API access, developer credentials, SDKs and an installable MCP server are coming soon. The examples below illustrate a direction; they are not executable API documentation.

ONE CREATIVE WORKFLOW. DIFFERENT STARTING POINTS.

Work that starts
with the right brief.

Explore the tools in the app and the kind of information an integration might carry.

01 / A FOCUSED VIDEO

One scene. A clear direction.

Describe a scene and choose its duration, quality and aspect ratio. Attach relevant references in the app.

Explore Create in the app ↗
CONCEPT ONLY / NOT A LIVE API
{
  "workflow": "create",
  "brief": "A cinematic reveal of our game's forest world",
  "duration_seconds": 15,
  "quality": "1080p",
  "aspect_ratio": "9:16"
}
Illustrative request shape · No endpoint or SDK required
THE WORKFLOW WE START FROM

Context in.
Reviewable work out.

  1. 01

    Brief & references

    Capture the creative direction and the game details that matter.

  2. 02

    Production request

    Keep the selected settings and inputs together in the queue.

  3. 03

    Team production

    The Cleom team prepares the work and uploads the delivery.

  4. 04

    Library & review

    Preview the result, download the file and plan the next iteration.

LET’S START WITH YOUR USE CASE

What should
connect to what?

A useful integration starts with a real production need.

Tell us which tool starts the request, what references and settings it should send, who approves the result and where the delivery belongs. We’ll discuss feasibility and scope with your team.

No integration availability or release date is promised by these examples.