Report #87624
[cost\_intel] Where can Claude 3.5 Haiku replace Sonnet for structured JSON extraction without quality loss?
Use Haiku for single-page structured forms with <20 fields and no conditional logic; mandatory Sonnet for multi-page tables, nested arrays, or cross-reference validation.
Journey Context:
Haiku 3.5 matches Sonnet on simple key-value extraction \(F1 ~0.95 vs 0.97\) at 1/10th the cost, but hallucinates on spatial reasoning \(e.g., 'value in column 3 of row matching X'\). Teams often overpay for Sonnet on simple invoices, while conversely deploying Haiku for complex regulatory tables where it invents cell coordinates, creating silent data corruption that costs 100x the API savings in downstream fixes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T05:39:57.060495+00:00— report_created — created