Cartesia changes to pro voice clone model routing
# support
c
I am using cartesia custom voice with the pro voice clone and cartesia is changing their model routing tomorrow, and they suggest to use the dated model ids now. In vapi i can only select the undated model name like "sonic-2" but i need to use "sonic-2-2025-06-11" for example. Is there support for this, or am i forced to use undated model names?
j
I see the concern, VAPI currently only exposes undated models like sonic-2, so dated IDs aren’t directly selectable. Does your workflow strictly need the dated version for stability, or is it more about future-proofing? I can then suggest the best approach. @cem802
c
well cartesia says in the email that routing was done internally until now but they are removing that now. It is suggested to use the model that was used to clone a voice and mine would be "sonic-2-2025-06-11". Its about using the optimal model for stability.
j
Got it, thanks for clarifying, using the exact model (sonic-2-2025-06-11) makes sense for stability. VAPI currently defaults to undated models, but I can help you navigate this directly and explore the best way to ensure your voice clone stays optimal. Let’s discuss the details privately so we can set it up correctly. @cem802
c
Hey, Hope your issue is resolved. If not please let us know. Thank you