Report #95748
[cost\_intel] Claude Haiku produces invalid JSON or hallucinates schema fields on nested extraction tasks despite 8x lower latency
Use Haiku only for flat key-value extraction \(≤2 levels deep\). Switch to Sonnet for nested objects, arrays of objects, or conditional schema fields. Expect 8-10x cost increase but 40-50% reduction in schema violations on complex forms.
Journey Context:
Teams often default to Haiku for all extraction due to speed, but it systematically fails on nested structures \(e.g., extracting line items from invoices with variable fields\). The failure mode is silent: valid JSON but wrong structure. Benchmark on your schema complexity first—if the JSON path depth exceeds 2, Haiku's accuracy drops >25% while Sonnet holds >95%. The cost savings are false economy if you need validation retries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T19:17:40.053606+00:00— report_created — created