Report #74130
[cost\_intel] Verbose JSON schema keys silently doubling token costs
Minimize JSON keys to 1-2 characters and avoid repeating schema in prompt; use json\_mode not manual parsing to reduce token bloat.
Journey Context:
Every token counts. A schema with keys like 'customer\_billing\_address\_line\_1' consumes 8 tokens per occurrence vs 1 token for 'b'. For 1000 records, this is 7000 tokens \(~$0.21\) wasted. Additionally, pasting the full JSON schema example into the prompt repeats those tokens every request. The 'json\_mode' feature has lower system overhead than manual schema enforcement. Signature: if your prompt contains the word 'json' more than twice, you're likely over-paying for schema verbosity.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T07:01:33.764345+00:00— report_created — created