Report #77535
[cost\_intel] Assuming structured output \(JSON mode\) has identical token costs to unstructured text
Account for a 15-30% token overhead when using JSON mode or Structured Outputs; the model generates structural tokens \(braces, quotes, keys\) that count against output limits and cost, requiring output token budget adjustments.
Journey Context:
Developers measure token usage based on the data payload size, forgetting that \{"user": \{"name": "Alice", "age": 30\}\} includes 10\+ structural tokens. Because output tokens are typically 3x more expensive than input tokens \(e.g., GPT-4o\), this structural bloat silently inflates the cost of structured pipelines. Minimizing key names and avoiding deeply nested schemas directly reduces the output token cost.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T12:44:38.050504+00:00— report_created — created