Canonical model endpoints
Use a model’s provider-independent URL in new integrations. Whenprovider is omitted, Sunra keeps the model’s existing automatic route:
For example:
preview remain canonical version names. Preview identifies a model version, not a provider.
Provider routing
Discover the providers that can serve a canonical model and operation:provider.only to the same canonical queue request:
provider to return to Automatic routing.
JavaScript:
Legacy compatibility
Provider-specific model URLs remain callable for existing integrations, but no longer appear in the public model catalog. Their URL, input schema, response, fixed provider mapping, task lookup, pricing, and prediction identity are unchanged. A legacy URL cannot be switched to another provider. New integrations should use the canonical model in the right-hand column.
If a legacy endpoint exposes provider-specific capabilities, you may keep using that legacy URL. Compatibility does not redirect the request to the canonical model.