Back to feed
News Story
InfoQ
1 sources

OpenAI Launches Decisions API, Potentially Threatening Jev

OpenAI unveiled its Decisions API at DevDay, built on the GPT-6 Luna model, which can quickly select from preset answers and return confidence scores with a latency of just 150 milliseconds. The API closely overlaps with the core capabilities of startup Jev, which launched on September 15 and is reportedly discussing a valuation exceeding $10 billion. This move could pose a significant competitive threat to Jev, sparking community discussion.

SynthePulse Insight · AI deep readingMembers

15 Days and $10 Billion: Did OpenAI's Decisions API Really Kill Jev?

Version 1 · 1 source

OpenAI unveiled the Decisions API at DevDay, using the smallest and cheapest GPT-6 Luna to choose among preset options and return a confidence score, a product form that overlaps heavily with Jev, which launched only 15 days earlier. But Jev's pricing, calibration method and true accuracy have not been disclosed, and whether its moat holds depends on the hardest variable to verify: just how accurate the probabilities it returns really are.

  • OpenAI announced the Decisions API at DevDay, built on the currently smallest and cheapest GPT-6 Luna, able to choose among a set of preset answers and return a confidence score.
  • OpenAI cites a latency of 150 milliseconds, while using GPT-6 Luna directly for the same kind of task takes 1.6 seconds.
  • The Decisions API is currently available only as a limited preview, with pricing, the maximum number of candidate answers and custom tuning capabilities all undisclosed.
Open section navigationA Head-On Collision Just 15 Days Apart

A Head-On Collision Just 15 Days Apart

On September 15, TypeSafe AI officially launched Jev. Just 15 days later, OpenAI announced the new Decisions API at DevDay. It is built on OpenAI's currently smallest and cheapest GPT-6 Luna, can choose among a set of preset answers, and returns a corresponding confidence score.

Developers only need to provide the API with a question, candidate answers and context. The model does not generate a passage of text like ChatGPT; instead it returns a decision that can be handed directly to a program: which category the content should be sorted into, which model a request should be routed to, what action an Agent should take next. This overlaps almost entirely with the capability that has drawn the most attention to Jev over the past half month.

A few hours after the news broke, a post with a blunt title appeared in Reddit's AI_Agents section: "Jev Is Dead." The poster wrote that with OpenAI rolling out the Decisions API, it would probably be very difficult for Jev to keep surviving, and that its only remaining advantages were being "extremely fast and extremely cheap." A commenter added another judgment: "Jev never had any moat at all."

This OpenAI Launch Feels Somewhat Rushed

In the DevDay keynote, Sam Altman spent only a few sentences introducing the Decisions API: it lets the model respond in a fraction of a second, and it works by giving the Luna model a set of preset options and pushing response speed to the extreme by making the model focus on that single choice.

This passage contains two key pieces of information. First, the Decisions API narrows open-ended generation into "choosing from explicit options," which is highly consistent in design philosophy with Jev's Choice primitive. Second, it chose Luna as the underlying model — the smallest and cheapest in OpenAI's current model lineup. Using the smallest, lowest-cost model to handle decision tasks rather than calling a larger model shows that this capability is clearly aimed at the scenario of a high-frequency, low-cost foundational component that can be embedded into Agent workflows at scale.

But this new API is currently available only as a limited preview, and pricing, the number of candidate answers supported per request, and whether developers can tune it with their own data are all undisclosed. An OpenAI spokesperson told foreign media that the company plans to release more information "at full launch." It can therefore be judged that OpenAI most likely rushed this launch in order to get the news out before DevDay.

From a product positioning standpoint, this kind of capability fills the gap between ordinary chat models and traditional classifiers. In the past, if developers wanted a model to choose among several answers, they usually called an ordinary chat model and constrained the output with prompts, or read token probabilities; another route was to train a dedicated small classifier, which is fast and cheap but requires labeled data, and often needs retraining whenever the labels change. The Decisions API sits between the two: developers can supply new questions and labels through prompts just as with a large language model, while getting structured results and confidence scores similar to a classifier.

Free for now

Read the full analysis

5 more sections of analysis, plus the full takeaway

Loading

Credibility boundary

This article is based on a report by InfoQ (article_id 19545), which is itself a second-hand account; the figures concerning Jev's pricing, speed, cost and valuation all come from TypeSafe's own claims or Financial Times reporting and have not been verified by third parties; the Reddit user's internal test is an individual account lacking a first-party source. OpenAI's latency figure and Altman's remarks are vendor statements. The judgments in the text about the moat and the training pipeline are the original author's inferences, and this article has labeled them accordingly.

Primary report

InfoQ

Primary source