# Kling legacy route note — reference2video / multi-image2video

Status: historical / legacy-route note
Captured: 2026-03-30

## Purpose
Record why `reference2video` (`/v1/videos/multi-image2video`) should no longer remain in the current production-facing documentation layer, while preserving provenance and live observations.

## What this route is
- docs-menu name observed in preserved artifacts: `Reference to Video`
- docs path observed in preserved artifacts: `apiReference/model/multiImageToVideo`
- endpoint used in live probing: `POST /v1/videos/multi-image2video`

## Why it was present in the repo
- it exists in the broader Kling dev-doc corpus captured under `samples/kling-api/`
- it remained callable during live testing
- it was initially treated as a potentially relevant non-Omni family because the broader docs corpus mixes multiple model generations and endpoint families together

## Why it was downgraded out of the current production-facing layer
- dashboard/runtime observations suggested a legacy model generation (for example 1.6-class behavior) rather than a clean current-3.0 production route
- current production-facing model policy for this repo is now intentionally narrowed to:
  - `text2video` with `kling-v3`
  - `image2video` with `kling-v3`
  - `omni` with `kling-v3-omni`
- current multi-reference-like production behavior is better explained through Omni `image_list[].image_url` than through `reference2video`
- keeping `reference2video` in the current production-facing docs would blur together:
  - broader historical/platform surface
  - current production-default truth for this repo

## Handling rule
- preserve this route as history/provenance only
- do not present it as a current production-default path
- if future work revisits it, frame that work as legacy-route analysis, not as the default 3.0 production path

## Related interpretation guardrails
- do not use `image2video` + `image_tail` results as a substitute for this endpoint
- do not assume Omni `image_list` is a formally documented migration replacement unless upstream docs explicitly say so
- practical current reading is narrower:
  - Omni `image_list` is the effective current production-facing multi-reference-like route
  - `reference2video` is historical / legacy unless later current-3.0 evidence proves otherwise