Structured Outputs And Format Controls

Operator passes response_format={type:'json_schema', json_schema:{...}} to extract structured company info from a grounded query.

Confirm the chosen Sonar model supports response_format [REQUIRES-VERIFICATION per model-cards]. Provide a complete schema with all required fields. Validate the response client-side against the same schema before downstream use; even strict modes can occasionally drift under grounded-context confl…

Operator wants Sonar's answer to match a strict regex (e.g., a ticker symbol pattern '^[A-Z]{1,5}$') and passes response_format={type:'regex', regex:'^[A-Z]{1,5}$'}.

Use regex response_format only when the grounded answer is expected to be a single short token (ticker, postal code, ISO country). Validate client-side. For multi-token answers, prefer json_schema. Confirm regex format support on the chosen model [REQUIRES-VERIFICATION].

Schema requires {value: integer, source: string}. Grounded search retrieves three sources reporting different integers.

When sources disagree, decide policy: (a) pick the most-cited / most-recent / highest-authority value, OR (b) widen the schema to {value: array, sources: array} and surface the disagreement. Do NOT silently average / pick first source. Make the policy explicit in the schema description and in the s…