Report #53984
[cost\_intel] When does Claude 3 Haiku fail on structured JSON extraction vs Sonnet
Use Haiku only for flat schemas \(<3 nested levels\); Sonnet required for nested objects, arrays within objects, or conditional field validation due to Haiku's instruction-following degradation on complex schemas
Journey Context:
Teams default to Haiku for extraction to save costs \(10x cheaper at $0.25/1M vs $3/1M input\), but Haiku hallucinates required fields or returns malformed JSON when schemas have nested objects or conditional logic. The failure mode is silent: valid JSON but wrong structure or dropped fields. Sonnet maintains schema adherence up to 4-5 levels of nesting. Cost analysis shows a failed Haiku extraction requiring retry costs more than using Sonnet once, and the latency of two Haiku calls exceeds one Sonnet call.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:06:36.289533+00:00— report_created — created