/messages is protocol-path evidence.Do not rotate a valid key before proving which stream implementation built the request.Route the construction decision.
Reuse the catalog provider and delegate its stream implementation.
Build the supported protocol explicitly, replacing catalog dispatch.
Reject the route because no protocol owner exists.
Build an independently named custom provider.
Prove the final path.
Requires api: openai-completions for an intentional custom route.
Different request and response contract; do not infer it from the URL.
May come from an explicit protocol or a reused catalog provider.
Keep Sessions, defaults, credentials, logs, and rollback unambiguous. Record the sanitized final path in a fresh Session.
Backward-compatible hardening.
Catalog reuse must remain available for native authentication and compatibility behavior. Authoring surfaces should warn when a catalog id combines an omitted protocol with a changed endpoint, and tests must assert the final wire path—not only the model list.
Keep the complete recovery matrix.
The canonical guide includes safe YAML, supported protocols, request evidence, credential boundaries, acceptance gates, and rollback.
Read the complete guide