Structured output

Structured output turns model text into schema-validated application data.

Explore structured output

Page	Learn how to
Schema design	Define narrow, portable Zod contracts.
Parsed completion	Return validated data from one model call.
Agent output	End a tool-using or contextual run with a schema-shaped result.
Extractors	Pull typed fields from existing content.
Validation errors	Handle malformed JSON and schema failures safely.
Choose a primitive	Match the runtime pattern to the workflow.

The trust boundary

Model response → JSON parsing → schema validation → trusted application data

The provider may use the schema to guide generation, but product code should trust only locally validated data.

Structured output surfaces

Anvia uses Zod schemas across direct parsed completions, agent final output, extractors, tool contracts, and pipeline input.

Use a regular completion or agent response when the caller only needs prose. A schema is useful when another part of the application will read fields, branch on values, or persist the result.