Model Studio documents decision-model-preview for classification and scoring through the System One protocol. The documentation does not establish how it compares with Jev.
Alibaba Cloud Model Studio now lists decision-model-preview for tasks where software needs a decision rather than a written answer: choose a category, rate urgency or estimate the probability of yes. The model lifecycle list dates its release to September 24; Yicai reported the API's opening that day. The model page was updated on September 28; that is a documentation date, not evidence of another model release.
In an API example, one request carries a customer ticket and three questions: which team should handle it, whether to alert on-call staff, and how severe the issue is. The response gives choices or scores with probabilities instead of generating free-form text. The example's 52.9 ms latency is a sample response value, not an independent speed test.
Alibaba calls the calling format the TypeSafe System One protocol and includes an example using typesafe-sdk. TypeSafe introduced Jev on September 15 for a similar class of structured decisions. A shared request format helps explain how to call the services. The documentation does not show that the underlying models or their answer quality are the same.
Using decision-model-preview requires an Alibaba Cloud API key. The docs list endpoints in Singapore and Beijing, a context limit of 65,536 tokens and a recommendation of no more than 16 questions per request because latency grows as questions are added. The model page currently lists limited-time free access in those regions, but no lasting price from which to compare its cost with Jev.
A Reddit post by u/pneuny drew attention to the documentation. The author called the model a hurried Jev competitor. That is their interpretation: Alibaba's published material does not say how long development took, and we found no public head-to-head test of the two models. A team choosing a service for ticket routing would need to run the same tickets through both APIs; the 52.9 ms in Alibaba's example is not such a comparison.