One prompt.
A video in return.

Describe it. We handle the steps.

Only prompt is required. Kando prepares the script, builds the scene, and renders the video automatically. No session setup or follow-up messages needed.

// Run on your server with your Kando service credentials.
const base = process.env.KANDO_URL;
const headers = {
  Authorization: `Bearer ${process.env.KANDO_API_KEY}`,
  'Content-Type': 'application/json',
};

const response = await fetch(`${base}/v1/videos`, {
  method: 'POST', headers,
  body: JSON.stringify({
    prompt: 'An 8-second video of two strangers at a café. A slow push-in.',
  }),
});
if (!response.ok) throw new Error(await response.text());
let video = await response.json();
console.log(video.id); // Save this ID to resume polling later.

const deadline = Date.now() + 30 * 60_000;
while (video.status === 'queued' || video.status === 'in_progress') {
  if (Date.now() > deadline) {
    throw new Error('Still generating; resume with GET ' + video.status_url);
  }
  await new Promise(resolve => setTimeout(resolve, 5000));
  const status = await fetch(`${base}${video.status_url}`, { headers });
  if (!status.ok) throw new Error(await status.text());
  video = await status.json();
}
if (video.status !== 'completed') {
  throw new Error(video.error?.message || video.status);
}

// Public CDN URLs do not need your service credentials.
const url = new URL(video.video_url, base);
const mp4 = await fetch(url, {
  headers: url.origin === new URL(base).origin ? headers : {},
});
if (!mp4.ok) throw new Error(await mp4.text());
const { writeFile } = await import('node:fs/promises');
await writeFile('video.mp4', Buffer.from(await mp4.arrayBuffer()));

A video when it’s ready.

A successful text response is not enough: the job completes only when the full rendered MP4 has been saved. The following is an illustrative completed response; IDs and file metadata come from your request.

{
  "id": "<video-id>",
  "object": "video",
  "prompt": "An 8-second café encounter. A slow push-in.",
  "status": "completed",
  "created_at": "<ISO timestamp>",
  "status_url": "/v1/videos/<video-id>",
  "video_url": "https://cdn.vframe.cc/kando/videos/<video-id>/<sha256>.mp4",
  "output": {
    "path": "export/review.mp4",
    "sha256": "<file hash>",
    "size": 1234567,
    "mime": "video/mp4"
  },
  "error": null
}

Four endpoints. One workflow.

Call your gateway or standalone agent with Authorization: Bearer YOUR_API_KEY. URLs in responses are relative to that service and require authentication. Invalid prompts return 400; unknown video IDs return 404.

Use your Kando workspace.

These examples use your own running Kando service. Public self-serve API keys and billing are not available yet.

1. Start Kando

   In the repository, run pnpm dev for the local gateway and store, and pnpm web for the website.

2. Connect your application

   Set KANDO_URL and KANDO_API_KEY on your application server. Keep service credentials out of browser code.

3. Open the video studio

   The website reads the same connection from the root .env. Hosted shared workspaces also require KANDO_WEB_ACCESS_KEY. Everyone with that workspace key can access its projects. Manage invitation codes and recorded model costs at /internal; invited visitors only access projects created with their code.

Advanced project history, files, and model controls remain available through the existing session API. A video ID also identifies its underlying project.