Discuss your project
Architecture IA

Decisions API: check a document type before review

An attachment looks like an invoice without being one. Compare two ways to return a fixed choice and decide what your application still needs to verify before passing the file on.

Decisions API : vérifier le type d’une pièce avant de l’envoyer en revue

Your expense form receives an order confirmation where it expects an invoice. The answer should be one of four choices: invoice, confirmation, other or unreadable. OpenAI introduced Decisions in beta with GPT‑6 Luna on October 6, 2026. General availability followed on October 22, increasing the maximum from 200 to 400 questions per request and adding, among other changes, images in individual question instructions. A typed answer provides a value allowed by the interface. You still need to measure accuracy.

Test with your own data

Label 50 synthetic documents, including blurry ones. Submit them to Decisions and to Responses with structured output, using the same four options. Check how contradictory pages and missing answers are handled. Record 95th-percentile latency, price per 100 documents and order confirmations mislabeled as invoices. Record batch size alongside every measurement.

Making a decision

The application should recognize missing answers, check whether the expected document is present and direct uncertain cases to a reviewer. Our Clef article covers support routing. Here the cost of mislabeling a document and the contract between two interfaces drive the test.

Share this article