Preserve provider identity independently of SDK endpoint spelling

When rollout routing explicitly chooses native OpenAI, carry that selection through configuration, client construction, tool policy, and telemetry instead of inferring identity from whether the SDK endpoint is absent. Native SDK calls can use an explicit endpoint; treating every present URL as compatible silently changes request policy and attribution. Conversely, a configured compatible route with an OpenAI-looking URL should retain its selected contract. Reset inherited identity when a factory override changes the effective endpoint. This method proves local identity propagation; provider acceptance and live rollout adoption require separate evidence.

Applies when: native and compatible providers share an SDK but require different request contracts. Keywords: OpenAI Pipecat rollout provider identity endpoint factory tools metrics