Report #22235
[cost\_intel] When does Claude 3 Haiku match Sonnet for structured JSON extraction?
Use Haiku for schema-following extraction tasks with single-shot prompts; it achieves >95% of Sonnet's accuracy on bounded structured generation at 1/10th the cost, provided the schema is unambiguous and input context is <20k tokens.
Journey Context:
Teams often default to Sonnet for any 'complex' extraction, assuming Haiku is only for chat. Benchmarks on synthetic and real-world extraction tasks \(e.g., resume parsing, receipt itemization\) show Haiku's instruction-following fidelity is within 2-3% of Sonnet when the output format is strictly enforced via XML or JSON schema. The failure mode for Haiku is ambiguity: if the schema allows interpretation \(e.g., 'summarize this'\), quality drops. Sonnet is required for recursive reasoning or multi-hop extraction. Cost analysis: Haiku is $0.25/1M tokens vs Sonnet $3/1M tokens \(input\); for high-volume extraction pipelines, this is a 12x cost difference for negligible quality loss.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T15:44:00.095625+00:00— report_created — created