AI Signal

Decisions API: your app needs a route, not a paragraph

OpenAI made Decisions API generally available on October 22. It returns typed judgments over shared evidence; your app still controls actions and uncertainty.

· 1:05

Watch on YouTube ↗View on X ↗Watch on TikTok ↗Share episode ↗Machine-readable catalog ↗

Transcript

The original narration, preserved as published. Relative dates refer to the episode’s coverage window.

Why pay a chatbot to write a paragraph when your app just needs a decision? OpenAI made its Decisions API generally available on October twenty-second. Currently, GPT six Luna is its only model.

It checks a condition and estimates its probability, picks from your allowed choices, or rates an input against ordered levels, such as issue severity. Need a written explanation or custom object? Use Responses with Structured Outputs.

Take a damaged-delivery ticket. Supply the customer's complaint, order details and an item photo. Ask whether the product has visible damage and which team should handle it. The answers go straight into your code.

The release accepts structured JSON directly and different images for individual questions. Shared input can receive cache discounts. Each request now supports up to four hundred independent questions, twice the public beta limit.

Your software still performs any action. A probability is an estimate, not a guarantee. Our recommendation: send uncertain cases to a person instead of automatically granting a refund. Watch routing mistakes and review workload on your real tickets.