What changed in the API.

Saved scanners and typed observations

Reusable, versioned scanner definitions now sit above one-off video analyses. Each run snapshots its scanner version and emits typed observations with explicit semantics, source metadata, relevance, and timestamped evidence.

• Added scanner types for monitors, summaries, classification, scoring, timestamped moments, and extraction.
• Added cross-run observation queries and run provenance.
• Kept relevance separate from calibrated confidence.
• Kept finished-video rendering as an optional downstream operation.

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.

Uploads and signed webhooks

Console surfaces and contracts are prepared for private uploads and completion webhooks. These capabilities may be unavailable until storage and delivery infrastructure is enabled for an account; the console reports that state explicitly. Trusted direct HTTPS source URLs and run polling remain the baseline integration.