Skip to main content
ShippedNo vapor

The AI that actually shipped

VerdictOpenAI

Editor's first pass (AI-assisted)

Scored by an AI research pass from the linked sources; a human editor will re-score it. How we score →

Real4.0Documented endpoint with public pricing and a Playground; labelled beta.
Useful4.0Typed answers from text and images suit classification and routing without parsing prose.
Notable4.0The largest lab now sells a decision endpoint, in a category others opened.
Novel3.0It wraps an existing model behind a new endpoint; the interface idea predates it.
Hype gap▼ −0.5 under
Shipped

Readers

Upvotes count the readers who want this seen. Ratings are 1 to 5 scores on the four dimensions; the rating count is the number of readers who rated it. The editor’s score is shown on its own and is the headline figure. Reader ratings join the ranking only once 5 or more readers have rated, and a reader mean from fewer than 5 ratings is too few to count. How ranking works →

OpenAI opens its Decisions API in public beta, built on GPT-6 Luna

A /v1/decisions endpoint returns typed predicate, choice and score answers. Public beta, $0.10 per million input tokens, GA promised in weeks.

OpenAI's Decisions API is a dedicated endpoint, POST /v1/decisions, that evaluates text, images or both and returns typed answers instead of prose. The docs say it is in public beta and expected to reach general availability in the coming weeks. The only supported model is gpt-6-luna.

There are three answer types. A predicate gives the probability that a condition is true. A choice picks one of your values with per-option probabilities and a confidence value. A score gives a probability-weighted average over ordered levels.

The docs price it at $0.10 per million input tokens. There are no output, cache-read or cache-write charges. Images go in as base64 data URLs or public URLs, not file IDs. Zero Data Retention and HIPAA use are supported for eligible customers, and a Playground is available. The docs say it is about 10x faster than the Responses API, without a workload definition.

Press coverage places an earlier limited preview at DevDay on 29 September and dates the public beta to 6 October. The date here rests on one secondary report, since the docs page carries no date.

The pitch is speed and cheap input. The proof is your own labelled examples, which is what OpenAI recommends for setting thresholds.

Sources

Editor's first pass (AI-assisted)

Primary evidence

Comments