Report #77419
[cost\_intel] When does Claude 3 Haiku match Sonnet 3.5 for JSON extraction at 12x lower cost?
Use Haiku 3 for extraction tasks where output schema is constrained \(enums, regex patterns, short strings\) and input context <20k tokens. Switch to Sonnet 3.5 if schema contains free-text descriptions >100 tokens or requires multi-hop reasoning across context.
Journey Context:
Sonnet 3.5 is overkill for simple field mapping \(invoice dates, amounts\). Haiku achieves >98% F1 on structured schemas but hallucinates on open-ended generation \(e.g., 'summarize and extract'\). Quality degradation signature: Haiku produces invalid enum values or truncates long text fields; Sonnet maintains coherence. Cost math: Haiku input $0.25/1M vs Sonnet $3/1M; on 10M tokens/month, $2,750 savings with <2% accuracy loss for structured tasks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T12:32:37.632885+00:00— report_created — created