OpenAI’s Decision API Leaves Beta With Voice Integration


TL;DR

  • General Release: OpenAI’s Decisions API is generally available, giving developers probabilities, choices and scores through its GPT-6 Luna model.
  • Voice Apps: Integration with OpenAI’s GPT-Live voice service sends conversation transcripts directly for decisions, removing an application round trip.
  • Input Costs: New prompt caching charges to store shared material and discounts the input price when that material is reused.

OpenAI has moved its Decisions API, which gives software probabilities, choices or scores instead of written replies, into general availability on October 22. For applications making repeated small judgments, OpenAI claims about tenfold faster answers than its text-generating Responses API. Andrew Hsu, chief technology officer at AI language-tutoring company Speak, told TechCrunch that its trial cut the interval between actions from 1.4 seconds to 0.13 seconds.

Developers already had access through an all-developer public beta on October 6. The general release adds prompt caching and native voice integration, while doubling the maximum number of questions in one request from 200 to 400.

Small Judgments Instead of Written Replies

Decisions API runs on GPT-6 Luna, the model also available through OpenAI’s Responses API. Nikunj Handa, OpenAI’s API product lead, told TechCrunch that TypeSafe’s rival Jev decision model showed his team uses for its own version. His team reconfigured Luna for faster, cheaper inference rather than training a new model.

The Decisions API evaluates text, images or structured JSON data and returns a probability, one of the developer’s supplied choices, or a score against ordered criteria. Responses can generate a custom data object, a written explanation or a request to use a tool with specified arguments.

 

As OpenAI demonstrates with a product-photo example, an application can ask whether the image contains a crack, tear or dent. The Decisions API then returns an estimated probability of damage, and the application uses a chosen cutoff to flag the photo for review. Developers can set thresholds using labeled examples and the relative costs of false alarms and missed cases.

One request can ask independent questions about the same photo, such as whether it is damaged and which product category it belongs to. A later question that depends on the first answer still needs another request. The application performs any action selected by the answers.