Report #56054
[cost\_intel] Claude Haiku produces invalid nested JSON on complex extraction while Sonnet succeeds
Use Haiku for flat key-value extraction \(single-level fields\) but Sonnet for nested schemas with conditional logic. Haiku misses 15-20% of nested fields in tables and hallucinates nulls on conditional schemas.
Journey Context:
Teams assume OCR quality determines extraction success, but the real differentiator is handling conditional schemas. Haiku parses invoices flatly fine, but fails when extracting line-items arrays or conditional metadata. Sonnet maintains schema integrity across nesting. Cost difference is 8x \(Haiku $0.80/1M vs Sonnet $6/1M tokens\), but retry rates on nested tasks make Haiku actually more expensive when accounting for validation failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:34:43.518351+00:00— report_created — created