The quick read
- For an illustrative reporting process, divide total batch cost by the number of reports that meet the acceptance criteria.
- Assess quality, delay and cost together.
Look beyond a model call
The price of a response is only one part of a workflow. Retrieval, document extraction, external services, storage and human correction may all contribute. Failed attempts cost resources even when they produce no usable result.
Measure accepted output
For an illustrative reporting process, divide total batch cost by the number of reports that meet the acceptance criteria. Record how many need another model call or substantial editing. A cheap first draft may become expensive if someone must check and rewrite most of it.
Compare the whole system
Assess quality, delay and cost together. A larger model might need fewer retries, while a smaller model may be sufficient for a tightly defined step. Use current provider pricing and document assumptions about volume and input length. Separate fixed setup effort from recurring operating cost. Revisit the estimate after the pilot rather than projecting from one convenient example. A good cost model makes it clear what useful work was delivered and what conditions would change the calculation.
Sources & notes
AI-assisted editorial content checked against the linked sources.
developers.openai.com — official reference
Sources reviewed for the September 2026 launch edition.