What are structured AI outputs?

Structure means downstream code can rely on the shape

A structured output constrains a response to a defined shape — a fixed set of fields, specific types, an enum of allowed values — rather than a paragraph of prose. The point is not style; it is that a program reading the response can pull out a value at a known path instead of parsing sentences and guessing at meaning.

There are two different ways to ask for it

The first is prompt-based: instructions tell the model to respond only in JSON matching a described shape. This works with essentially any model and needs no special API support, but it is a request the model can still ignore, get partly wrong, or wrap in explanatory text you did not ask for. The second is provider-enforced: some providers offer a mode, often called structured outputs or JSON mode, where generation itself is constrained so that only tokens consistent with the schema can be produced at each step. This is a stronger mechanism than an instruction, not just a stricter-sounding one — and it is a distinct feature from tool calling (see how tool calling works), which shapes the arguments to a named function rather than the model’s own answer.

A prompt instruction is a request, not a guarantee

When structure comes only from prompt wording, the model can still produce output that does not match — an extra field, a missing one, prose before the JSON, a value of the wrong type. Any system relying on prompt-only structure needs a real plan for what happens when parsing fails, not an assumption that it never will.

Provider-enforced structure is a different kind of guarantee

Where a provider constrains generation directly against a schema, the output is far more reliably well-formed, because malformed tokens are excluded from being generated in the first place rather than merely discouraged. Exactly which providers and models support this, and how strictly, varies and changes over time — treat prompt-based structure and provider-enforced structure as different reliability tiers, not interchangeable ways to get the same result.

A valid shape is not the same as a correct answer

Even with the strongest enforcement, the schema only constrains form, not meaning. A summary field can be syntactically valid JSON and still contain three rambling sentences instead of one, or a confidently wrong number in a field labeled as a count. A vague or overly permissive schema tends to produce technically valid output that is still unreliable to use.

Parsing successfully is not the same as being safe to trust

Whether structure came from a prompt or from provider enforcement, successfully parsing a response only confirms the shape was followed — it says nothing about whether field values are accurate, in range, or sensible. Treating a parsed object as verified data, rather than as a claim to check, is where structured-output systems most often go wrong in production.

Questions people ask

Is a structured output the same thing as a tool call?

No. Tool calling proposes a named function and its arguments for your application to potentially execute; a structured output shapes the model’s own answer into a defined format. The two mechanisms can be used independently or together.

Does asking a model for JSON in the prompt guarantee valid JSON back?

No. It is a request the model can still get wrong — extra text, a missing field, an incorrect type. Systems that rely only on prompt wording need a defined fallback for when parsing fails, not an assumption that it always succeeds.

If a provider enforces a schema, is the result guaranteed correct?

It is guaranteed to be well-formed according to the schema — the right fields, the right types. It is not guaranteed that the values inside those fields are accurate or sensible; enforcement constrains shape, not truth.

Do I still need to validate a structured response before using it?

Yes. Successfully parsing a response confirms the shape matched, not that the content is correct. Range checks, type checks, and sanity checks on the values remain necessary regardless of how the structure was produced.