API referenceScenes

Authoring context for up to 10 scenes

One merged context per scene: GET /scenes/{id}/authoring-context plus the rulers, cues and heard words of GET /scenes/{id}/context.

Per-scene results in input order. Free.

Authorization

bearerAuth

AuthorizationBearer <token>

Typecut API key. Generate one in app.typecut.ai → Settings → API keys. Send as Authorization: Bearer tc_live_….

In: header

application/json

TypeScript Definitions

Use the request body type in TypeScript.

scene_ids*array<string>

Items1 <= items <= 10

detail?string

Value in"compact" | "full"

curl -X POST "https://example.com/scenes/contexts" \  -H "Content-Type: application/json" \  -d '{    "scene_ids": [      "string"    ]  }'

{
  "data": {}
}

{
  "error": {
    "type": "string",
    "code": "string",
    "message": "string"
  }
}

{
  "error": {
    "type": "string",
    "code": "string",
    "message": "string"
  }
}

Lift an imported HTML slice into a standalone scene POST

import_html tier 3. An LLM pass writes the slice's window of the original file as a standalone composition on local time.

Land up to 10 authored compositions POST

PUT /scenes/{id}/composition for each scene — the same gates, mount, hosting and write — with every verdict inline.