Route Operation
Authoritative client-vs-server routing decision for a media op (doc 09 §2.2). The browser calls this with its probed capabilities to confirm the fast path before running WebCodecs; a headless caller (no client_caps) always routes to the server. Entitlements come from the caller’s plan (HEVC/E-AC-3/AC-4 gating).
Body
A media op + the caller's client capabilities. The server returns the AUTHORITATIVE plan (the client mirrors the same logic but the server's verdict wins).
The browser's probed WebCodecs/WebGPU capabilities (advisory; None ⇒ headless).
Response
Successful Response
The response is of type Response Route Operation Api V1 Assets Route Post · object.