What changed in the API.

Production-quality moment discovery in saved scanners

Video find_moments scanner runs now use the same production moment-selection behavior as ChatClipThat.

• Added optional analysis_start_seconds and analysis_end_seconds on single video find_moments runs.
• Omitting both fields analyzes the full upload within account limits.
• Completed observations include a Moment ID that can be explicitly submitted to /v1/renders.
• Other scanner types retain their focused question-and-answer behavior, and scanner runs never render automatically.

Audio-only saved scanner runs

All six saved scanner methods now accept completed private audio uploads with timestamped JSON results.

• Added media_kind on uploads and runs plus source_kind on runs.
• Added typed audio observations with optional speaker labels and timestamped excerpts.
• Generated speech excerpts are not certified verbatim transcripts.
• Kept monitor false explicit only after full-audio review; unanswerable remains a completed zero-observation result.
• Kept audio scanner output JSON-only with no render or public audio artifact.

Durable scanner batches

The public contract for /v1/scanner-batches is stable, while deployment availability remains gated until the durable batch service is enabled.

• Accepts up to 100 explicit scanner/upload pairs with unique client IDs and one required request idempotency key.
• Lists and pages durable batch/item state, including each item’s pinned scanner version and eventual run and analysis IDs.
• Cancellation stops queued items from starting while already-spawned work drains.
• Uses fair scheduling while reserving capacity for ordinary platform work.
• Bills every item as its own scanner run; upload reuse does not combine charges or processing.

Saved visual scanners and typed observations

Reusable, versioned visual questions now run against completed private uploads. Each run snapshots its scanner version and emits boolean, string, number, or object observations with explicit semantics, source metadata, relevance, and grounded evidence timestamps.

• Added monitor, summarizer, classifier, scorer, find-moments, and extractor answer contracts.
• Made monitor false an explicit full-video observation while keeping unanswerable as zero observations.
• Added cross-run observation queries and run provenance.
• Kept scanner execution JSON-only with no render or public-frame side effect.

Dedicated developer application

The public documentation and authenticated developer console now have a dedicated application surface designed for api.chatclipthat.com. Accounts, credits, analysis, and rendering continue to use the same ChatClipThat identity and backend.

• Public home, guides, recipes, quickstart, and API documentation are indexable.
• Console, authentication, machine routes, and account data are excluded from indexing.
• Legacy main-app developer paths remain compatible during migration.

Private uploads, scanner batches, and signed webhooks

Completed account-owned video and audio uploads are production inputs for saved scanner runs. Batch orchestration and signed terminal-event delivery are available through the API, with status polling retained as a reconciliation backstop. Trusted direct HTTPS video URLs remain available for separate one-off analyses.