v2, ensure you’ve thoroughly tested your system and are aware of any differences in the output.
Please note that v2 will become the default on 1 December 2025.
To ensure a seamless transition, existing customers will have the option to request v1 for an additional grace period.
This allows to adaptions to existing integrations, for example if they are contingent on particular tag handling behaviours exhibited by v1.
As of now, tag handling v2 is only compatible with the quality-optimized model type.
When you set
tag_handling_version to v2, the model_type is implicitly set to quality_optimized.Setting both model_type=latency_optimized and tag_handling_version=v2 in a request will lead to an error.