Report #55672
[cost\_intel] Claude 3 Haiku vs Sonnet quality cliff for structured JSON extraction tasks
Deploy Haiku for flat schemas \(<5 fields\) with clean inputs; mandatory upgrade to Sonnet for nested schemas >2 levels or adversarial inputs with noise
Journey Context:
Teams default to Sonnet for all extraction due to fear of format errors, but Haiku matches Sonnet within 3% accuracy on simple key-value extraction while costing 5x less. The cliff appears at nesting depth: Haiku's parser fails cascades on nested objects with >3 levels. Adversarial inputs \(OCR noise, mixed formats\) also trigger Haiku's safety refusals at 4x the rate of Sonnet. Test on your schema complexity first before over-provisioning.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T23:56:25.447544+00:00— report_created — created