Report #94110
[cost\_intel] Claude 3.5 Sonnet overkill for flat JSON extraction bleeding 10x cost
Use Claude 3.5 Haiku for single-level schema extraction \(flat key-value pairs\) at $0.80 per 1M output tokens vs Sonnet's $8.00—10x savings with <2% quality degradation on entity extraction. Force Sonnet only when schema requires conditional nesting or cross-field validation rules.
Journey Context:
Teams default to Sonnet for all structured outputs assuming JSON fidelity requires frontier capability. Haiku 3.5 matches Sonnet within 2% accuracy on flat extractions \(names, dates, amounts\) but fails catastrophically on nested logic: when extraction requires 'if field X exists then validate field Y format,' Haiku hallucinates structure or outputs invalid JSON 15-20% of the time versus Sonnet's <2%. The cost differential is exactly 10x \($0.80 vs $8.00 per 1M output tokens\), so production pipelines must branch: attempt Haiku, validate JSON schema strictly, fallback to Sonnet on parse failure. Common error: assuming Haiku's speed advantage \(2x faster\) justifies universal use—it collapses on conditional schemas.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T16:33:05.242636+00:00— report_created — created