Introduction

Welcome to the KinoCloud developer documentation. KinoCloud lets you submit render and simulation jobs, manage credits, and drive everything from scripts, CI pipelines, or AI agents over a single versioned HTTP API.

Start here

Getting started — create an API key and make your first authenticated request in ~15 minutes.
Authentication & API keys — keys vs sessions, environments, scopes, and rotation.
Submitting jobs — the estimate → upload → submit → poll lifecycle for render and simulation jobs.
MCP for AI agents — connect Claude Desktop or a remote agent over the Model Context Protocol.
Errors & rate limits — the error envelope, code catalogue, and rate-limit headers.
Versioning & deprecation — the change policy you can build a long-lived integration against.

Interactive API reference

The API reference is generated directly from the same Zod schemas that validate live requests, so it can never silently drift from the running API. It includes every endpoint, request/response schema, and an interactive "Try it" panel.

The machine-readable contract is published at /api/v1/openapi.json (and the standard discovery alias /.well-known/openapi.json) — point your SDK generator or Postman at either.

Introduction

Start here

Getting started — create an API key and make your first authenticated request in ~15 minutes.
Authentication & API keys — keys vs sessions, environments, scopes, and rotation.
Submitting jobs — the estimate → upload → submit → poll lifecycle for render and simulation jobs.
MCP for AI agents — connect Claude Desktop or a remote agent over the Model Context Protocol.
Errors & rate limits — the error envelope, code catalogue, and rate-limit headers.
Versioning & deprecation — the change policy you can build a long-lived integration against.

Interactive API reference

The machine-readable contract is published at /api/v1/openapi.json (and the standard discovery alias /.well-known/openapi.json) — point your SDK generator or Postman at either.