PRODUCTION SCENARIO
Your intake service submits a JSON schema for structured outputs that sets minimum 0 and maximum 120 on age, minLength 5 on postal_code, and leaves additionalProperties unset on the top-level object. The API rejects the schema.
Which revision makes the schema valid while keeping the guarantees?
Answering here is anonymous. Nothing is saved unless you sign in.
Show answer and explanation
Answer: Drop the numeric and length constraints, set additionalProperties to false, and validate ranges in code
Structured outputs require additionalProperties false on every object and every required field listed, and the grammar supports neither numerical constraints such as minimum and maximum, nor string constraints such as minLength, nor recursive schemas. Value bounds therefore have to be checked after parsing. Beta headers are no longer part of this feature, and strict is a per-tool field rather than a request field.